Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save Vars are still too confusing #66

Open
DLPB2 opened this issue May 20, 2017 · 1 comment
Open

Save Vars are still too confusing #66

DLPB2 opened this issue May 20, 2017 · 1 comment

Comments

@DLPB2
Copy link

DLPB2 commented May 20, 2017

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.

@DLPB2 DLPB2 changed the title Save "banks" are still too confusing Save Vars are still too confusing May 20, 2017
@DLPB2
Copy link
Author

DLPB2 commented Jul 18, 2022

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant