User:Snert: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==Resources== | |||
===Debug monitor=== | |||
Resource to easily be able to view server and client debug messages. (remotely) | |||
Images: | |||
Server-side debug message viewer: http://dl.dropbox.com/u/4504893/images/debugmonitor_editor_s.png | |||
Client-side debug message viewer: http://dl.dropbox.com/u/4504893/images/debugmonitor_editor_c.png | |||
[http://dl.dropbox.com/u/4504893/misc/debugmonitor.zip Download] ('''Note:''' Only works in 1.1 r2019 and later) | |||
==Function suggestions== | ==Function suggestions== | ||
Some functions I should work on sometime soon. | Some functions I should work on sometime soon. (sort of my "TODO") | ||
===Server-side=== | |||
<syntaxhighlight lang="lua"> | |||
setWaterColor | |||
</syntaxhighlight> | |||
===Client-side=== | |||
<syntaxhighlight lang="lua"> | |||
-- None at the moment | |||
</syntaxhighlight> | |||
=== | ===Both=== | ||
<syntaxhighlight lang="lua"> | <syntaxhighlight lang="lua"> | ||
setElementFrozen ( element theElement, bool toggle ) -- Would replace setPedFrozen, setVehicleFrozen and setObjectStatic | setElementFrozen ( element theElement, bool toggle ) -- Would replace setPedFrozen, setVehicleFrozen and setObjectStatic | ||
isEventAdded ( string eventName, element attachedTo[, function handlerFunction ] ) -- Should be fairly obvious | isEventAdded ( string eventName, element attachedTo[, function handlerFunction ] ) -- Should be fairly obvious | ||
getWaterColor -- The opposite of setWaterColor | |||
getSkyGradient -- The opposite of setSkyGradient | |||
</syntaxhighlight> | </syntaxhighlight> | ||
==Event suggestions== | ==Event suggestions== | ||
Events which might be quite useful | Events which might be quite useful. I should work on these sometime soon. | ||
===Server-side=== | ===Server-side=== | ||
<syntaxhighlight lang="lua"> | <syntaxhighlight lang="lua"> | ||
onSettingChange ( string name, var oldValue, var newValue ) -- Should be quite obvious. Detecting settings changes can be quite useful for dynamic resources | onSettingChange ( string name, var oldValue, var newValue ) -- Should be quite obvious. Detecting settings changes can be quite useful for dynamic resources | ||
onElementCreated ( ) -- Said it will be very slow, but still, it's a quite useful event. Besides, if onElementDestroyed isn't slow, why would this be slow? | onElementCreated ( ) -- Said it will be very slow, but still, it's a quite useful event. Besides, if onElementDestroyed isn't slow, why would this be slow? | ||
| Line 28: | Line 53: | ||
<syntaxhighlight lang="lua"> | <syntaxhighlight lang="lua"> | ||
onClientElementCreated ( ) -- See server-side | onClientElementCreated ( ) -- See server-side | ||
onClientVehicleNitrousActivated ( ) -- See server-side | onClientVehicleNitrousActivated ( ) -- See server-side | ||
Revision as of 13:49, 27 November 2010
Resources
Debug monitor
Resource to easily be able to view server and client debug messages. (remotely)
Images:
Server-side debug message viewer: http://dl.dropbox.com/u/4504893/images/debugmonitor_editor_s.png Client-side debug message viewer: http://dl.dropbox.com/u/4504893/images/debugmonitor_editor_c.png
Download (Note: Only works in 1.1 r2019 and later)
Function suggestions
Some functions I should work on sometime soon. (sort of my "TODO")
Server-side
setWaterColor
Client-side
-- None at the moment
Both
setElementFrozen ( element theElement, bool toggle ) -- Would replace setPedFrozen, setVehicleFrozen and setObjectStatic isEventAdded ( string eventName, element attachedTo[, function handlerFunction ] ) -- Should be fairly obvious getWaterColor -- The opposite of setWaterColor getSkyGradient -- The opposite of setSkyGradient
Event suggestions
Events which might be quite useful. I should work on these sometime soon.
Server-side
onSettingChange ( string name, var oldValue, var newValue ) -- Should be quite obvious. Detecting settings changes can be quite useful for dynamic resources onElementCreated ( ) -- Said it will be very slow, but still, it's a quite useful event. Besides, if onElementDestroyed isn't slow, why would this be slow? onVehicleNitrousActivated ( ) -- Should be fairly obvious onVehicleNitrousDeactivated ( ) -- Should be fairly obvious onVehicleTireStateChanged ( int tire, int state ) -- If you'd want vehicles with bulletproof wheels or something, you'd need to detect the state change first
Client-side
onClientElementCreated ( ) -- See server-side onClientVehicleNitrousActivated ( ) -- See server-side onClientVehicleNitrousDeactivated ( ) -- See server-side onClientVehicleTireStateChanged ( int tire, int state ) -- See server-side
FX functions
Doomed_Space_Marine did research on some particle effects on custom models. It would be very cool if we could make functions to do this instead, like we already can with some particle effects. (for instance: fxAddBlood) This would especially be very cool if we would be able to alter the fx, so for instance we could create colored smoke.
fxAddHeliKillBlood fxAddCarWashEffect fxAddCement fxAddClouds -- Note: It's a rather vague type of effect fxAddCokeTrail fxAddShower -- Note: Classed as "some water effect", but unknown what type of water effect. Assuming shower fxAddSmoke fxAddPour -- Seems more like it should be fxAddPee or fxAddPiss though fxAddLeaves fxAddSpray fxAddFireExtinghuiserEffect fxAddFlamethrowerFlame fxAddInsects
Want to add another function / event?
Feel free to edit this page. The more suggestions there are, the more *might* be implemented.