Difference between revisions of "Talk:Scripting"
| Line 13: | Line 13: | ||
Will DebugText print the text exactly as you put it in? Like printing out the float value 0.47 exactly as "0.47"? | 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. | ||
Revision as of 05:29, 10 September 2017
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.
