Search
Members
HelpUsers browsing this thread: 1 Guest(s)
Battlescript variables...
07-20-2015, 11:55 PM
Merchant
 |
Total coincidence! Weird....
Hmm, I was initially thinking about moving the veldt data back to $1E00-$1E40, and then increasing the #$13 in the line of code you pointed out. But you make a good point about forcefield and the other variables. They could be moved somewhere else, but it would be tedious. The game relies on them getting cleared at the start of battle too, so it would probably mess things up if you let them get saved. I guess this wouldn't be as easy as I thought.
As another option, I realized that there are 12 other battle variables that don't seem to be utilized by the game at all. From my notes, vars 9 to 16 are the only ones that get used. Vars 4 to 8 and vars 17 to 23 are unused. How many saved variables do you plan on using? Also, how can I get my hands on Madsiur's RAM map?
To change the 36 byte limit, I think you would only need to change the code for AI command $F8. The code is really efficient. It looks like the other AI commands that affect variables jump to this code too. There's a problem though. During a battle, the variables are getting saved in RAM at $3EB0-$3ED3. And if you expanded that, you would be overwriting other stuff.
Hmm, I was initially thinking about moving the veldt data back to $1E00-$1E40, and then increasing the #$13 in the line of code you pointed out. But you make a good point about forcefield and the other variables. They could be moved somewhere else, but it would be tedious. The game relies on them getting cleared at the start of battle too, so it would probably mess things up if you let them get saved. I guess this wouldn't be as easy as I thought.
As another option, I realized that there are 12 other battle variables that don't seem to be utilized by the game at all. From my notes, vars 9 to 16 are the only ones that get used. Vars 4 to 8 and vars 17 to 23 are unused. How many saved variables do you plan on using? Also, how can I get my hands on Madsiur's RAM map?
To change the 36 byte limit, I think you would only need to change the code for AI command $F8. The code is really efficient. It looks like the other AI commands that affect variables jump to this code too. There's a problem though. During a battle, the variables are getting saved in RAM at $3EB0-$3ED3. And if you expanded that, you would be overwriting other stuff.
Code:
C2/1E1A: A6 B9 LDX $B9
C2/1E1C: 20 57 1E JSR $1E57
C2/1E1F: A6 B8 LDX $B8
C2/1E21: 20 45 1E JSR $1E45
C2/1E24: C6 B6 DEC $B6
C2/1E26: 10 04 BPL $1E2C
C2/1E28: 45 EE EOR $EE
C2/1E2A: 80 0C BRA $1E38
C2/1E2C: C6 B6 DEC $B6
C2/1E2E: 10 04 BPL $1E34
C2/1E30: 05 EE ORA $EE
C2/1E32: 80 04 BRA $1E38
C2/1E34: 49 FF EOR #$FF
C2/1E36: 25 EE AND $EE
C2/1E38: E0 24 CPX #$24 <- change this
C2/1E3A: B0 05 BCS $1E41
C2/1E3C: 9D B0 3E STA $3EB0,X
C2/1E3F: 80 03 BRA $1E44
C2/1E41: 99 AC 3D STA $3DAC,Y
C2/1E44: 60 RTS
C2/1E45: 48 PHA
C2/1E46: E0 24 CPX #$24 <- and this
C2/1E48: B0 05 BCS $1E4F
C2/1E4A: BD B0 3E LDA $3EB0,X
C2/1E4D: 80 03 BRA $1E52
C2/1E4F: B9 AC 3D LDA $3DAC,Y
C2/1E52: 85 EE STA $EE
C2/1E54: 68 PLA
C2/1E55: 18 CLC
C2/1E56: 60 RTS![[-]](https://www.ff6hacking.com/forums/ff9/collapse.png)
« Next Oldest | Next Newest »
Users browsing this thread: 1 Guest(s)
2017