Difference between revisions of "Category talk:Events"
Jump to navigation
Jump to search
imported>HawkFest (→Events) |
imported>HawkFest m (→Events) |
||
Line 10: | Line 10: | ||
:: -- [[User:Cipscis|Cipscis]] 15:37, 16 February 2012 (EST) | :: -- [[User:Cipscis|Cipscis]] 15:37, 16 February 2012 (EST) | ||
:::Qazaaq and Cipscis, are you saying that the sole "native" event is the OnHit event? That would be odd, but why not... Understand the confusion of any reader fumbling onto such a description while searching for some vanilla (and reusable) list of events, or looking forward about what they are and how they work : he'll be left in the ditch considering all the events that take place in the game, and considering all those events accessible "natively" from a modder's standpoint (i.e. no need to reprogram event mechanisms that are already offered as functions). A more complete description is REQUIRED : documentation authors limiting themselves to such thin descriptions, should not even bother to loose their time writing incomplete and obscure documentation (even a single phrase can do so much for something to be made understood). A documentation is not solely appreciable by its structure and looks, but mostly by its content. At the very least, a link to some vanilla event function list, with a note regarding this "native vs funct." (which seems to be of importance only to those developing the engine btw), would be most relevant. We're not Cyborg monkeys. As creators we need to UNDERSTAND the why's and how's and where's, else it's quite counter-productive. | :::Qazaaq and Cipscis, are you saying that the sole "native" event is the OnHit event? That would be odd, but why not... Understand the confusion of any reader fumbling onto such a description while searching for some vanilla (and reusable) list of events, or looking forward about what they are and how they work : he'll be left in the ditch considering all the events that take place in the game, and considering '''all those events accessible "natively" [[from a modder's standpoint]]''' (i.e. no need to reprogram event mechanisms that are already offered as functions). A more complete description is REQUIRED : documentation authors limiting themselves to such thin descriptions, should not even bother to loose their time writing incomplete and obscure documentation (even a single phrase can do so much for something to be made understood). A documentation is not solely appreciable by its structure and looks, but mostly by its content. At the very least, a link to some vanilla event function list, with a note regarding this "native vs funct." (which seems to be of importance only to those developing the engine btw), would be most relevant. We're not Cyborg monkeys. As creators we need to UNDERSTAND the why's and how's and where's, else it's quite counter-productive. | ||
:::--[[User:HawkFest|HawkFest]] ([[User talk:HawkFest|talk]]) 12:54, 17 December 2012 (EST) | :::--[[User:HawkFest|HawkFest]] ([[User talk:HawkFest|talk]]) 12:54, 17 December 2012 (EST) |
Revision as of 12:59, 17 December 2012
Events
Are these all the events we can use? If not, is there a more complete list somewhere? --Mr6 12:05, 16 February 2012 (EST)
- The list is complete.
- --Qazaaq 13:54, 16 February 2012 (EST)
- This is a complete list of native events. As events are functions (although they can't have return values) it's possible to define and call custom events, but only native events are called by the game engine so any custom events you define will not be able to act as entry points.
- Take a look at the Critter script for some examples of creating and using custom events.
- -- Cipscis 15:37, 16 February 2012 (EST)
- Qazaaq and Cipscis, are you saying that the sole "native" event is the OnHit event? That would be odd, but why not... Understand the confusion of any reader fumbling onto such a description while searching for some vanilla (and reusable) list of events, or looking forward about what they are and how they work : he'll be left in the ditch considering all the events that take place in the game, and considering all those events accessible "natively" from a modder's standpoint (i.e. no need to reprogram event mechanisms that are already offered as functions). A more complete description is REQUIRED : documentation authors limiting themselves to such thin descriptions, should not even bother to loose their time writing incomplete and obscure documentation (even a single phrase can do so much for something to be made understood). A documentation is not solely appreciable by its structure and looks, but mostly by its content. At the very least, a link to some vanilla event function list, with a note regarding this "native vs funct." (which seems to be of importance only to those developing the engine btw), would be most relevant. We're not Cyborg monkeys. As creators we need to UNDERSTAND the why's and how's and where's, else it's quite counter-productive.
- --HawkFest (talk) 12:54, 17 December 2012 (EST)
- -- Cipscis 15:37, 16 February 2012 (EST)