Sly 1:LOCKG: Difference between revisions

When the trigger volume associated with a LOCKG is triggered it sets off a sequence of events. It starts with the animation that spawns a [[Sly 1:KEY]] for each [[Sly 1:LOCK]] in the <code>apLock</code> array. Each key flies to its assigned lock and then despawns.

At some point a message with ID 0xXXX{{check}} is sent to the [[JT (Sly 1):JT|JT]] struct. This message is processed by <code>HandleJtMessage</code>, which checks if the <code>ckey</code> on the current [[{{Sly 1|WS]]|world (World State)state}} is greater than the <code>cpLock</code>{{check}} on the LOCKG (iei.e. it checks if you have enough keys to open the lock).

If the check passes, it uses the LOCKG’s <code>LOCKG->FWS</code> as a bit maskbitmask to set the corresponding flag on the FWS of the current WS. It then unlocks the locks and sets the [[Sly 1:SMA|SmaGoal]] goal based on the LOCKG’s <code>LOCKG-> smaGoal</code> pointer. The SMA goal, which seems to beis processed by [[{{Sly 1|Splice]],}} determinesto thetrigger outcomewhatever (ie.scripted whatevent happens as a result of the locks being opened)unlocked.

Once all locks complete their unlock [[Sly 1:ASEG|animation]], theythe areassociated removedlocks fromdisappear from the game world along with the LOCKG itself.{{check}}

=== Example ===