PowerupManager: Difference between revisions
Jump to navigation
Jump to search
(→Events) |
No edit summary |
||
| Line 4: | Line 4: | ||
Advanced features contain: custom clientside animations (spin, up-down), custom collision element for triggering, server side triggering (to prevent cheating), change powerup object on the fly (for example triggering such a powerup gives a random advantage based on current modelID), ... | Advanced features contain: custom clientside animations (spin, up-down), custom collision element for triggering, server side triggering (to prevent cheating), change powerup object on the fly (for example triggering such a powerup gives a random advantage based on current modelID), ... | ||
=Used by= | |||
* self | |||
=Exported scripting functions= | =Exported scripting functions= | ||
Revision as of 12:20, 17 September 2007
The powerupManager library was created to ease the use of advanced, more custom pickups (powerups).
It exists out of server and client scripts to create, handle and destroy custom powerup items.
Advanced features contain: custom clientside animations (spin, up-down), custom collision element for triggering, server side triggering (to prevent cheating), change powerup object on the fly (for example triggering such a powerup gives a random advantage based on current modelID), ...
Used by
- self
Exported scripting functions
Server
- createPowerup
- destroyPowerup
- destroyAllPowerups
- setPowerupDimension
- getPowerupDimension
- setPowerupAnimation
- getPowerupAnimation
- setPowerupCanRespawn
- getPowerupCanRespawn
- setPowerupRespawnTime
- getPowerupRespawnTime
- getPowerupObject
- setPowerupObject
- setPowerupModelID
- getPowerupModelID
- setPowerupColShape
- getPowerupColShape
- setPowerupTemporaryTime
- getPowerupTemporaryTime
- setPowerupIsTemporary
- getPowerupIsTemporary
Client
- getPowerupDimension
- getPowerupAnimation
- getPowerupCanRespawn
- getPowerupRespawnTime
- getPowerupObject
- getPowerupModelID
- getPowerupColShape
- getPowerupTemporaryTime
- getPowerupIsTemporary
Events
Events prefixed with pum are ceated for internal usage only. You still can hook them, but I suggest you don't.