The way I imagine it might work:
a) Place an ammo box and edit its content through the normal Zeus editor for it.
b) Select the module out of the list and click on the box with it.
c) Enter a name for the "loadout" in the dialog, that pops up, to save it.
d) Place the module again, on free terrain, and select one of your previously saved loadouts (dropdown menu would be nice but entering the name again would also work)
Notes:
1.) Putting any work into this only really makes sense, if saved loadouts are persistent between missions (as they are in VAS).
2.) Where you save the loadouts is entirely up to you. If clientside makes the most sense, do it. With naming conventions even among programmers being what they are, noone really wants to go looking for their loadouts in a giant list of badly named somethings. If someone really, really wants to copy loadouts from someone else, person1 can place their crates, then let person2 into Zeus' seat to save them through the module.
The way I imagine it might work: a) Place an ammo box and edit its content through the normal Zeus editor for it. b) Select the module out of the list and click on the box with it. c) Enter a name for the "loadout" in the dialog, that pops up, to save it. d) Place the module again, on free terrain, and select one of your previously saved loadouts (dropdown menu would be nice but entering the name again would also work)
Notes: 1.) Putting any work into this only really makes sense, if saved loadouts are persistent between missions (as they are in VAS).
2.) Where you save the loadouts is entirely up to you. If clientside makes the most sense, do it. With naming conventions even among programmers being what they are, noone really wants to go looking for their loadouts in a giant list of badly named somethings. If someone really, really wants to copy loadouts from someone else, person1 can place their crates, then let person2 into Zeus' seat to save them through the module.