You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We discussed this some time ago. It's no fault of yours that the design team decided to do it in such a ridiculous way, but the current system is posing a problem for novice modders. And it is a little too confusing regardless.
As we know, there are 6 blocks: 1-5 in the Savemap, and a temp bank. Each is 0-255 bytes long.
The only difference between field var [1] and [2] is that one is 8 bit and the other is 16 bit. It's possible for all instructions in the game to use the actual block reference instead of this. For example:
Updated naming convention. I could maybe look into adding this one day - but what are the logistics? It should definitely be possible to streamline all this into the above and reference the blocks directly?
Low priority. Enhancement.
We discussed this some time ago. It's no fault of yours that the design team decided to do it in such a ridiculous way, but the current system is posing a problem for novice modders. And it is a little too confusing regardless.
As we know, there are 6 blocks: 1-5 in the Savemap, and a temp bank. Each is 0-255 bytes long.
The only difference between field var [1] and [2] is that one is 8 bit and the other is 16 bit. It's possible for all instructions in the game to use the actual block reference instead of this. For example:
Var[2][0] = 0 (16 bit)
becomes
16bitVar [1][0] = 0
Compare 8 bit
If Var[3][22] == Var[13][11] (else goto label 1)
becomes
If 8bitVar[2][22] == Var[4][11] (else goto label 1)
Field [5] and [6] become Var8bit[6] or Var16bit[6]. Or even Var8bit[temp] or Var16bit[temp].
This should be possible, no? And would remove any need for silly field vars entirely.
The text was updated successfully, but these errors were encountered: