SWATEliteForce
SWATEliteForce copied to clipboard
eezstreet
Stack up/Check lock no longer default commands for doors that are already open(due to new door roster system)
Self explanatory. If a door is set to open by the door roster it'll no longer ask for stacking up first.
I think it was an intentional change. I also find it to be uncomfortable tho.
This is indeed intentional and not something I'm going to change.
From: semodo [email protected] Sent: Friday, April 27, 2018 4:42:47 PM To: eezstreet/SWATEliteForce Cc: Subscribed Subject: Re: [eezstreet/SWATEliteForce] Stack up/Check lock no longer default commands for doors that are already open(due to new door roster system) (#419)
I think it was an intentional change. I also find it to be uncomfortable tho.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/eezstreet/SWATEliteForce/issues/419#issuecomment-385088673, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABvmRUgykEKeWzBzax9eomcvbu3je7pKks5ts4LHgaJpZM4TdULa.
This is verified as a bug. I misread the initial post. The door knowledge doesn't get reset when a non-SWAT AI closes the door, which can lead to weird instances of "OPEN AND CLEAR" being the default instead of "TRY LOCK"
In the code this logically makes sense though. The player knowledge of the door being unlocked results in the default action being “open and clear”. This makes sense to me. If I unlocked a door and opened it, when I go back to the same door I assume it is unlocked. Unless we want the player logic to be more paranoid. This also makes sense. Like if a door that the player knows was open is now closed, then the player knowledge assumes someone locked the door. The most simple fix would be that any closed door results in the default action being stack up”. This makes the fix easier but then removes the open and clear from the default after trying the lock.
Which would we prefer?
