VehSpawner: Fix Advanced Logistics blocking static weapon respawns. #178
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.
When an advanced logistics container vehicle is destroyed, static weapons created by the vehicle spawner (vehicle asset manager) system can be blocked from respawning.
The static weapon object is still alive, hidden and attached to the player who loaded it into the now destroyed container vehicle... meaning the static weapon will not respawn at the vehicle spawn point.
This change fixes the block on spawning by checking if the spawn point's
_currentVehicle
was loaded into a container vehicle with advanced logistics, and whether the container vehicle is still alive. If not, force respawn of_currentVehicle
.additional
_vehicle getVariable ["log_inventory_loaded", false]
should hopefully double up as a check for whether the advanced logistics module is enabled -- variable should not be set otherwise.Would be nice to unload static weapons from a destroyed adv-log container vehicle if they are configured for WRECK. but that's more complex.
Tested this pretty thoroughly, not encountered any issues.