PowerupManager: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (Seems to be a resource and not a module) |
||
| Line 21: | Line 21: | ||
{{PowerupManager/ClientEvents}} | {{PowerupManager/ClientEvents}} | ||
[[ru:PowerupManager]] | [[ru:PowerupManager]] | ||
Latest revision as of 13:31, 12 May 2013
|
This article is (partially) outdated and the information may no longer apply. |
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), ...
Also since it allows you to set a custom colShape, you can use it to create tripmines, ...
Used by
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 we suggest you don't.