User talk:Lou Montana

addBackpackGlobal

Reverted back because of two issues from your note that I thought were misleading. The backpack is null only momentarily while your note might have been interpreted as backpack on remote machine was null period. The example provided takes care of removing backpack if unit has one, because checking for null backpack while unit has a backpack will break the code and no mags would be added. If unit has backpack it would work, if unit doesn't have backpack it would still work. removebackpackglobal doesn't report on remote machine immediately hence waiting. I personally don't see the need to edit what I posted, but if you feel strongly it needs to be, please discuss. killzone_kid (talk) 14:35, 6 February 2019 (CET)

Hello, a provided example should go straight to the point and the description should not display any personal view ("This is inconvenient, but it is what it is."). The whole "check if there is a backpack" is mission-creator related, not of wiki concern. I agree though, the "momentarily" aspect was not clear in my note and should remain. Please join the Official Arma Discord to discuss further. - Lou Montana (talk) 14:43, 6 February 2019 (CET)

Tweaked a little, better? killzone_kid (talk) 14:50, 6 February 2019 (CET)

Should do the job, but why not (something like) this? Shorter and clearer.

⚠

The added backpack is created on the machine where unit is local. If the unit is remote an immediate backpackContainer command usage will return objNull.
The workaround is to wait for the backpack information's network synchronisation (See Example 2)

- Lou Montana (talk) 14:57, 6 February 2019 (CET)

backpackContainer is not the only command you can return backpack though killzone_kid (talk) 15:22, 6 February 2019 (CET)

« an immediate get-backpack command » then - Lou Montana (talk) 23:25, 6 February 2019 (CET)