FF6AE

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.