Lord J's FF6LE 'Rouge Version'

One more important thing...

The map data gets relocated to the F1 bank now, so be very careful if you are using that bank for anything else, like events.

Thankfully, J made a quick remedy for that as well. (what a guy!) I will quote him.

Lord J: "I've had time to squeeze in one more feature that might help with your bank $F1 problem. The bank can now be changed through an undocumented registry key. Just fire-up notepad, enter the following lines, change the "f1" to another value, save-as something.reg and double click on the new file.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\FF3LE\FF6LE]
"ExpBank"=dword:000000f1

Please, please do not use bank $F0, $FC or $FD as they are used by FF3usME for expansion purposes!!"

---

Finally, here's a technical breakdown he made for what exactly is happening:

Lord J: "The way the map expansion works is as follows:

1) You need to know that each overworld map is divided in two sections, individually compressed: first, the tile map (a series of index representing which tile is used at every spot of the map), second, the tile graphics (the bitmaps)

2) When the new FF6LE saves a map, it first will save the tile map and'll ask
2a) Is the new compressed size is equal or smaller than sizeof(regular tile map location) + sizeof(regular tile graphics location)? The answer to that question should be 95% of the time, yes
2b) Then a calculation is made: remainder = sizeof(regular tile map location) + sizeof(regular tile graphics location) - sizeof(new tile map)

3) Then FF6LE will save the tile graphics:
3a) Does sizeof(new tile graphics) <= remainder?
if yes, the data fits in the old location, bank $F1 is not used
if no, the data must be saved to bank $F1

4) same question for mini-map, it'll always fit the old location because ATM the data is not manipulated in any way (that'll be the next thing to implement in FF6LE

5) the process is repeated for the WoR

Overwritting location $F10500 and above totally depends on the WoB / WoR data size and expansion usage. A more "noisy" map and graphics will result in poor compression performance and thus higher probability to use bank $F1"