27
edits
Difference between revisions of "Talk:OnLockStateChanged - ObjectReference"
Talk:OnLockStateChanged - ObjectReference (edit)
Revision as of 12:40, 26 November 2023
, 12:40, 26 November 2023→On calling Lock(): event will fire twice when unlocked via lockpicking
TwilightSky (talk | contribs) (Created page with "== On calling Lock() == The note on the main page appears to misunderstand how this event works. Any change made to an object's lock state will trigger this event. If you lock...") |
TwilightSky (talk | contribs) (→On calling Lock(): event will fire twice when unlocked via lockpicking) |
||
| Line 1: | Line 1: | ||
== On calling Lock() == | == On calling Lock() == | ||
The note on the main page appears to misunderstand how this event works. Any change made to an object's lock state will trigger this event. If you lock it, this event fires. If you unlock it, same thing. This is intended behavior and it is not designed to store nor report the previous lock state. --[[User:TwilightSky|TwilightSky]] ([[User talk:TwilightSky|talk]]) 01:17, 12 November 2023 (EST) | The note on the main page appears to misunderstand how this event works. Any change made to an object's lock state will trigger this event. If you lock it, this event fires. If you unlock it, same thing. This is intended behavior and it is not designed to store nor report the previous lock state. --[[User:TwilightSky|TwilightSky]] ([[User talk:TwilightSky|talk]]) 01:17, 12 November 2023 (EST) | ||
: However, when a container's lock state is changed via lockpicking, this event will trigger twice. It is unknown why this happens. --[[User:TwilightSky|TwilightSky]] ([[User talk:TwilightSky|talk]]) 11:40, 26 November 2023 (EST) | |||