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
Crowbar settings have strange naming convention. Server convar ttt_crowbar_unlocks manages if crowbar tries to open doors. Unlocking is instead handled by ttt_map_settings entity, although if the server convar is set to false no opening or unlocking is possible at all.
To reproduce
Steps to reproduce the behaviour:
Set the server convar to false; suddenly, crowbars can't open doors.
Further, you can't turn off the unlock server-wide while leaving one open.
Expected behaviour
Unlock convar only controls unlocking, not opening.
An additional separate convar for just unlocking would be good.
Further, it seems to be believed that ttt_map_settings controls door opening behaviour as well, while it currently only controls unlocking. A separate key value might be nice to control exactly that in TTT2.
The text was updated successfully, but these errors were encountered:
Your version of TTT2 (mandatory)
Both:
Describe the bug (mandatory)
To reproduce
Steps to reproduce the behaviour:
Further, you can't turn off the unlock server-wide while leaving one open.
Expected behaviour
An additional separate convar for just unlocking would be good.
Further, it seems to be believed that ttt_map_settings controls door opening behaviour as well, while it currently only controls unlocking. A separate key value might be nice to control exactly that in TTT2.
The text was updated successfully, but these errors were encountered: