VehicleLocking: Allow locking of static weapons to a specific team. #177
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Locking script only applied to vehicles with a driver / co-pilot position -- StaticWeapon objects don't have a driver or a co-pilot.
With vanilla config settings, this bugfixes the `m101` assets not being locked to ACAV (even though there's a config for it)
```
//Howitzer
class vn_b_army_static_m101_02 : acav {};
class vn_b_sf_static_m101_02 : acav {};
```
Allows server owners to include any static weapon in the respawn + locking configs (feature).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Locking script only applied to vehicles with a driver / co-pilot position -- StaticWeapon objects don't have a driver or a co-pilot.
With vanilla config settings, this should only affect the locking of the
m101assets for ACAVAllows server owners to include any static weapon in the vehicle locking config.
Note -- may well be possible to go through the same config lookup as the existing
isCopilotcheck but forisGunnerinstead, but I went with the simple, happy path route.