2009-10-26, 11:08 PM
For now my only major proposals (space permitting) is we stop using LEAF to refer to the stages of "events" and start using STAGE instead. Beginning with translation work.
Leaf whatever the original Japanese is not appropriate here. Leaves accurately describes the items in the trees you see on the PIECE SETUP window, including the Objects, Enemies, Items, and the Event leafs below them. Leaves in technical jargon are the nodes on a tree. Either the nodes at the tips of the tree or the inner nodes before they're expanded to reveal more leaves.
So an EVENT LEAF should mean what we call an EVENT currently, because they're bound to objects in the piece setup tree.
Next, instead of COMMAND, in the "EVENT LEAF SETUP" window, the word INSTRUCTION should be used instead of COMMAND. There is a big difference in technical jargon, and these are technically not commands. If AVAILABLE INSTRUCTIONS cannot be fit, then INSTRUCTIONS/INSTRUCTION LIST would suffice.
Counters should be called something like Registers if possible. The word Counter is possibly technically more correct, but I think it creates a lot of confusion for people because it implies a lot of stuff that doesn't make sense to people who don't understand how computers work. Register is also an esoteric word, but it's less ambiguous. And I think Register also fits in with the Registry pages in the Parameter Editor, in the sense you're working with a finite number of ids. We could call these technically Event Instruction Registers. And the slots in the Parameter editors would be like Item Parameter Registers for example.
I suggest instead of using "REGSTER" in the parameter editor, CHANGE or something simple should be used. Just to avoid using double terminology and to pull everything inline with the Event Setup dialog. I think for example Change Register Value should be used instead of Alter Counter Value. If you click on "Alter Counter Value" it even says "CHANGE THIS COUNTER" (presently)
^I actually think "Change Register State" would be more appropriate since I will soon be developing extensions which will change many registers without a direct instruction from the Event Instructions available via the map editor. It will make more sense then to think of many of the counters as a state machine instead of containing fixed values. Basically how the "Timers" already work.
And "Change Event Stage" should be used instead of "Control Active Leaf".
There are other things I'd prefer to change for my own purposes (in extension development) along the way like Display Text instead of Display Message. Though I suppose technically speaking the text does not have to be a message anyway (I have intentions to vastly expand the capabilities of "messages" btw, including more than 2 choices and the ability to let players input names into counters for like the name of a character/protagonist or saved game name minimum... on top of an endless menu of text manipulation options including substitution of values so an NPC or item can confer dynamic information, such as a changing number or the players chosen name)
Leaf whatever the original Japanese is not appropriate here. Leaves accurately describes the items in the trees you see on the PIECE SETUP window, including the Objects, Enemies, Items, and the Event leafs below them. Leaves in technical jargon are the nodes on a tree. Either the nodes at the tips of the tree or the inner nodes before they're expanded to reveal more leaves.
So an EVENT LEAF should mean what we call an EVENT currently, because they're bound to objects in the piece setup tree.
Next, instead of COMMAND, in the "EVENT LEAF SETUP" window, the word INSTRUCTION should be used instead of COMMAND. There is a big difference in technical jargon, and these are technically not commands. If AVAILABLE INSTRUCTIONS cannot be fit, then INSTRUCTIONS/INSTRUCTION LIST would suffice.
Counters should be called something like Registers if possible. The word Counter is possibly technically more correct, but I think it creates a lot of confusion for people because it implies a lot of stuff that doesn't make sense to people who don't understand how computers work. Register is also an esoteric word, but it's less ambiguous. And I think Register also fits in with the Registry pages in the Parameter Editor, in the sense you're working with a finite number of ids. We could call these technically Event Instruction Registers. And the slots in the Parameter editors would be like Item Parameter Registers for example.
I suggest instead of using "REGSTER" in the parameter editor, CHANGE or something simple should be used. Just to avoid using double terminology and to pull everything inline with the Event Setup dialog. I think for example Change Register Value should be used instead of Alter Counter Value. If you click on "Alter Counter Value" it even says "CHANGE THIS COUNTER" (presently)
^I actually think "Change Register State" would be more appropriate since I will soon be developing extensions which will change many registers without a direct instruction from the Event Instructions available via the map editor. It will make more sense then to think of many of the counters as a state machine instead of containing fixed values. Basically how the "Timers" already work.
And "Change Event Stage" should be used instead of "Control Active Leaf".
There are other things I'd prefer to change for my own purposes (in extension development) along the way like Display Text instead of Display Message. Though I suppose technically speaking the text does not have to be a message anyway (I have intentions to vastly expand the capabilities of "messages" btw, including more than 2 choices and the ability to let players input names into counters for like the name of a character/protagonist or saved game name minimum... on top of an endless menu of text manipulation options including substitution of values so an NPC or item can confer dynamic information, such as a changing number or the players chosen name)