Difference between revisions of "Category talk:Events"
→Events: The list is further down the page
imported>HawkFest m (→Events) |
imported>Cipscis (→Events: The list is further down the page) |
||
| Line 12: | Line 12: | ||
:::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) | ||
::::The OnHit event is just the one used as an example. The list we're talking about is further down the page, where all pages within the category are shown with links to all of the pages. Descriptions of each event is on its own page. | |||
::::When I talk about ''native'' events, I mean the events that will be called directly be the engine. Events with any acceptable name can be defined and called in code just like functions without a return value. Take a look at the vanilla scripts handling critters for some examples of custom events, from memory I think a custom "OnStart" event is used there. This is not a ''native'' event because it is never called directly by the engine, and can only be triggered from a Papyrus script. | |||
::::-- [[User:Cipscis|Cipscis]] ([[User talk:Cipscis|talk]]) 22:29, 17 December 2012 (EST) | |||