This ticket will be related to two other tickets :
this one which looks dead : https://feedback.bistudio.com/T76478
and this one which has been closed : https://feedback.bistudio.com/T117338
As far as i know, there is only one way to lock the door of a building within a script :
_building setVariable ["bis_disabled_door_1", 1, true];
this variable is used in BIS_fnc_door to check if the door should open or not.
We can't change this behaviour on our side without reconfiguring all houses or changing BIS_fnc_door.
The problem is simple but apparently has no solution.
Because of map objects streaming, sometimes, randomly in multiplayer, a building on a specific player's machine will be deleted and created again.
Which means that this player will loose all variables (bis_disabled_door_X) set on that building, and will be able to enter freely inside.
This seems to happen more often when there are a lot of players connected on the server.
So this task would be either one of these solutions :
- [Bug] Set the variables back when the object is created again after being deleted
- [Feature] Or create a new way to lock doors on buildings, which doesn't use setVariable
- [Feature] Add a config parameter serverside to disable map object streaming ? ...