DSB/Locking Flags: Difference between revisions
From DmWiki
Jump to navigationJump to search
Created page with "; LOCK_ACTUATORS : Triggers will not work ; LOCK_MOVEMENT : Party cannot move ; LOCK_MOUSE : Mouse clicks will not work at all ; LOCK_MAGIC : Cannot enter runes or cast spells ; ..." |
added category |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
To lock multiple aspects just put them together with a '+'. Such as, to lock both movement and actuators use: | |||
<code> | |||
dsb_lock_game(LOCK_MOVEMENT + LOCK_ACTUATORS) | |||
</code> | |||
; LOCK_ACTUATORS : Triggers will not work | ; LOCK_ACTUATORS : Triggers will not work | ||
; LOCK_MOVEMENT : Party cannot move | ; LOCK_MOVEMENT : Party cannot move | ||
| Line 9: | Line 16: | ||
; LOCK_MESSAGES : Message timers will not run | ; LOCK_MESSAGES : Message timers will not run | ||
; LOCK_ALL_TIMERS : No game timers will run at all | ; LOCK_ALL_TIMERS : No game timers will run at all | ||
[[Category:DSB|Locking Flags]] | |||
Latest revision as of 14:03, 9 May 2011
To lock multiple aspects just put them together with a '+'. Such as, to lock both movement and actuators use:
dsb_lock_game(LOCK_MOVEMENT + LOCK_ACTUATORS)
- LOCK_ACTUATORS
- Triggers will not work
- LOCK_MOVEMENT
- Party cannot move
- LOCK_MOUSE
- Mouse clicks will not work at all
- LOCK_MAGIC
- Cannot enter runes or cast spells
- LOCK_INVENTORY
- Cannot view inventories
- LOCK_ATTACK
- Cannot trigger attack methods
- LOCK_FLYERS
- Flying objects will not update
- LOCK_CONDITIONS
- Timed conditions will not update
- LOCK_MESSAGES
- Message timers will not run
- LOCK_ALL_TIMERS
- No game timers will run at all
