Poll: What should be prioritized (multiple choices allowed) This poll is closed. |
|||
Events | 3 | 6.82% | |
Monster Graphics | 3 | 6.82% | |
Maps (FF6LE clone) | 3 | 6.82% | |
Sprites (characters) | 2 | 4.55% | |
Monster AI | 5 | 11.36% | |
Strings / Dialogues / Names | 3 | 6.82% | |
Spell data | 4 | 9.09% | |
Item data | 3 | 6.82% | |
Monster Data | 6 | 13.64% | |
Chest data | 3 | 6.82% | |
Animations data | 0 | 0% | |
Tilesets / Tiles Graphics | 0 | 0% | |
Shop Data | 2 | 4.55% | |
Monster Formation / Packs | 4 | 9.09% | |
Other misc data (see easy stuff) | 3 | 6.82% | |
Total | 44 vote(s) | 100% |
* You voted for this item. | Show Results |
Users browsing this thread: 2 Guest(s)
FF6AE
05-07-2016, 02:59 PM
(05-06-2016, 09:45 PM)Imzogelmo Wrote: I think the overhead of a pointer table would be worth it, and besides, the structural data that calls it (NPC struct, map struct, tile trigger struct) could shrink each entry from 3 bytes to 2, which would more than make up for the pointer table in absolute terms.
I can see some advantage to use a pointer table for reordering purpose of an event editor. If your event at CB/7900 once packed free up 10 bytes after its FE, you just go through all the table and you do if pointer > CB/7900; pointer -= 0x0A. You still have to do the same with all B2, B6, C0-CF commands concerned but it's a step in the right direction if I understand correctly. This example concern only code packing / optimization which is not a mandatory thing. I think an event editor should disallow expanding events directly in $CA-$CC if the editor does not perform optimization in those banks because of the little free space in ending of $CC, some of it being used by FF3usME and patches.
Also a pointer table could allow an event to land directly in expanded ROM (or other ROM free space), removing the need of a B2 call in $CA-$CC.
« Next Oldest | Next Newest »
|
||||
Users browsing this thread: 2 Guest(s)