Difference between revisions of "Talk:Scripting"
(Added a section for typo/mistake (requests for corrections)) |
|||
| Line 1: | Line 1: | ||
| + | === Mistakes/Typos === | ||
| + | |||
| + | In the section "CHECK or IF", ACTIONS needs to be declared after the INTERRUPT, above Reset(). | ||
| + | |||
| + | [[User:LaughingLeader|LaughingLeader]] ([[User talk:LaughingLeader|talk]]) 19:10, 11 December 2018 (CET) | ||
| + | |||
| + | === Misc === | ||
| + | |||
Some very useful information here. I'm slightly confused about the purpose of SCRIPTFRAMES. It would be nice to see an example of one, including the Osiris code. Also an example of a LIST in action would be nice. I also think the example EVENT is not super helpful, since most people aren't going to know what the archetypes are. | Some very useful information here. I'm slightly confused about the purpose of SCRIPTFRAMES. It would be nice to see an example of one, including the Osiris code. Also an example of a LIST in action would be nice. I also think the example EVENT is not super helpful, since most people aren't going to know what the archetypes are. | ||
Revision as of 19:10, 11 December 2018
Mistakes/Typos
In the section "CHECK or IF", ACTIONS needs to be declared after the INTERRUPT, above Reset().
LaughingLeader (talk) 19:10, 11 December 2018 (CET)
Misc
Some very useful information here. I'm slightly confused about the purpose of SCRIPTFRAMES. It would be nice to see an example of one, including the Osiris code. Also an example of a LIST in action would be nice. I also think the example EVENT is not super helpful, since most people aren't going to know what the archetypes are.
I also find the Behavior example confusing. It looks like maybe there's a ! on the second condition (for dangerous surfaces), that shouldn't be there?
Under common mistakes there's CHECK or IF. Are there situations where you would use IF over CHECK in behavior?
Another common mistake I think could be checking things in the wrong order. Something like:
IsGreaterThen(_Vitality,.5) CharacterGetStat(_Vitality,__Me,Vitality)
(I mean, that is a mistake, right?)
Will DebugText print the text exactly as you put it in? Like printing out the float value 0.47 exactly as "0.47"?
Going over types of variables (INT, FLOAT, FIXEDSTRING, STATUS, CHARACTERTEMPLATE, etc.) here or somewhere else would be useful too.
