You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Smokebombs can be equipped in every weapon slot, this allows for up to 4 smoke bombs to be equipped by each player.
We want to restrict the the smoke bombs to the ExtraWeapon / Pike / Banner slot to make it a decision if you bring a smoke bomb or another ExtraWeapon slot item and reduce the overall amount of smoke bombs that can be active at the same time.
Since smoke bombs are setups like stones the best way to lock them to the slots could be part of the item id as filter.
crpg_smokebomb_
The text was updated successfully, but these errors were encountered:
I think Flags are validated by BL and throw errors if they are unknown but I am not a 100% on that since lots of things changed with 1.2.
If we could make it a working flag so the game can deal with it, that sure would be a great addition for utility items like deployable stakes or siege shields at some point.
ExtraWeapon is designed for weapons which have either tags: ItemFlags.DropOnWeaponChange | ItemFlags.DropOnAnyAction
You cannot 'swap' back to an extra weapon slot, as you equip the item when you first spawn and it is not designed for items which are not dropped when swapped away from.
Perhaps we can prevent players from equipping the same item twice, but keep it in the normal weapon slot.
Currently Smokebombs can be equipped in every weapon slot, this allows for up to 4 smoke bombs to be equipped by each player.
We want to restrict the the smoke bombs to the ExtraWeapon / Pike / Banner slot to make it a decision if you bring a smoke bomb or another ExtraWeapon slot item and reduce the overall amount of smoke bombs that can be active at the same time.
Since smoke bombs are setups like stones the best way to lock them to the slots could be part of the item id as filter.
crpg_smokebomb_
The text was updated successfully, but these errors were encountered: