ArsenalsInit: Initialise arsenals (markers/trashcan init) during server init #207
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Was writing up the wiki and felt very weird having a dance between having N
arsenal_cleanup_ntrash cans, whereNmust match the index of the arsenal (what if someone wants to put down two trash cans for one arsenal?!).This adds some server side initialisation logic to make life simpler
missionNamespace setVariable ["vn_mf_arsenals", _arsenals]When a player joins, we can just load trash cans by finding relevant objects within 10m of the init'd arsenals instead of having to find different map markers and resolve the trashcans based on indexes of map markers.
--
TODO