ranwang520

Makinom Editor, I wonder if there are plans to improve the operational process for variables. I find the current process quite cumbersome, especially when the number of variables increases. For example, when the number of variables in a schematic increases to 20 or even 40, it becomes as tangled as spaghetti and difficult to distinguish. Is there another way to separate these variables (purely from the editor UI perspective)? For instance, could we simply add an independent editor window? Of course, this is just a potentially imperfect idea from me. Hmm... Or maybe there are other more refined ideas. I ask this because I believe Makinom + ORK has huge potential, but creating a finished game requires a lot of Makinom knowledge, which prompts me to ask this question.

==================

gamingislove

Makinom 2.14 (I think) brought some updates for variable fields, e.g. listing the local variables that are used in the schematic at the top and the rest after a separator in the variable field's popup.
E.g. if you press down (arrow key) in the varible field it'll open the popup with all variables (matching the one you already typed or all if the field is empty), with the local variables on top. Or the button beside the field will also list them in a different way, having local variables in separate child-popup.

I'm always open for improvements :)

ranwang520

Regarding the variable section, have you considered adding a strict mode?

For example:
Undeclared variables should not be usable. Similar to writing code, they must be declared in advance to be used; otherwise, an error should be reported. In scenarios like this, for instance, when using local variables in a schematic, they must be added in the schematic settings before they can be used.
========
Currently in Ork, both global and local variables can be manipulated regardless of whether they have been declared or not.
========
This approach facilitates management. Sometimes, for example, when I accidentally spell "speed" as "speed1," but "speed1" hasn't been defined in the schematic settings, it should throw an error. However, the current Ork does not report an error and simply uses the variable.
========

Additionally, I'm not sure if you fully grasp my meaning, as all the text was translated using ChatGPT, and there might be some areas where the expression is vague or unclear.

gamingislove

There'll be no change to how variables are handled - they can be used anywhere without declaring them first. When you do a variable setting, you'll already get a list of all currently used variables (locals listed first) to select from.