Battlescript variables...

Hi! Everything, it's quite a nice coincidence you came back to answer, despite your last log in vas in april anyway...

Oh, for some reason i forgot that forcefield was used outside the range of var 4-23
var 25 should be related to latest target, anyway...

Let me know if you're interested in making that happen, I'd be glad to help.

Interested? By all means!!! if you can help with that, i'll be very glad to accept your help, no doubt you'll get credit for that in my hack... besides it's a quite good patch in general, which modders might want to download, if they know how to properly use battle vars, of course.

Talking about not reset battle var code:

Code:

C2/49D3: E2 20        SEP #$20    (Set 8-bit A)
C2/49D5: A2 13        LDX #$13
C2/49D7: BD B4 3E     LDA $3EB4,X  (copy in-battle event bytes)
C2/49DA: 9D C9 1D     STA $1DC9,X  ( back into normal out-of-battle event bytes)
C2/49DD: CA           DEX
C2/49DE: 10 F7        BPL $49D7    (loop 14 times)

Normally it would be easy to just increase LDX #$13 in order to cover an higher range, unfortunately battle var 24, 25 and 26 store important temp values ;[ that would take some nasty change to the code... anyway i believe it's necessary to extend the range until var 35... until 34 or 33 should be good too, i need to have at least one var to store escape check and eventually some other feature i might implement in the near future.

The solutions are two, i believe:

1) placing some extra code between those 2 lines...
C2/49D5: A2 13 LDX #$13
C2/49D7: BD B4 3E LDA $3EB4,X (copy in-battle event bytes)
3 CMP (18, 19 and 1A the 3 cmp values) to detect if you're checking var 24-26, if then if the check is true... a branch on equal, i guess, you skip the code that save the value outside battle and go directly to DEX code line, in that way you can extend LDX value, without any consequence... what do you think about that, could it work?

2) move var 24-26 values to var 33-35, but that would mean change the code related to forcefield, targeting and monster types count too, which i believe it really requires too much work, attention and time, to not skrew things up
__________________

Actually there's another obstacle: battle vars are stored from 1DC9 to 1DDC, but as RAM map Madsiur's document says:
$1DDD-$1E1C: Monster formations beaten (to fight on veldt) (64 bytes)
$1E1D-1E3F: (35 bytes which appear to be unused, at least in my save files)

yeah, saving extra vars would mean invade monster formations beaten area...
Now, coincidences want i wanna banish Veldt from my hack (Rages will be got in the same way of Beyond Chaos hack, in the case) so if i erase all the script that change their value after you win a battle and then erase the script that makes start a battle with veldt packs, instead of conventional world map packs, then 64 bytes would be free to use as i wish and well... there are also 35 bytes which are appearently unused, now a confirmation from Madsiur about them being safe to use would be great, in that case i'd kill 100 birds with one stone!
Of course, to break var 36 bound, i should also change the code that set the value to 36, if you target a variable number greater than var 36, do you know which one battlescript AI commands have this bound, in the case? (among set, increase, if var X = value then... etc. commands)