 |
Fixed in svn rev 8494. The problem is that frob system is one-side communication. When player frobs something, a method UseBy us called on that entity. It can be called with "press", "repeat", and "release" signals. Neither the lock nor the player saves information about the other side during frobbing. So when player breaks frob by moving or turning away, the signals simply stop coming: there is no place in the code which handles this situation explicitly. The solution was implemented by Grayman in 0003643, and it sounds like what people do with HTTP protocol. There is a event scheduled 300 ms in the future, and this event is rescheduled everytime player frobs the lock (aka keep-alive). If player stops frobbing, then the event is not refreshed, and triggers pretty soon. This event was used only to raise weapon back (until now). Now it also sends a "release" signal to the lock. As the result, whenever player breaks frob for 300 ms, lockpicking is canceled automatically. |
- Anonymous
