Users browsing this thread: 1 Guest(s)
Summon Command Acts like Magicite
if you do my recommended C2/4D9C hook:
1) expand it to XBA, and then "JMP $4DA6" instead of RTS. no longer counts against Summon limit.
2) have the new code reached from C2/19C7 test Bit 6 of $B1 to differentiate between the two Summon types. admittedly, you'd be expanding this bit from its original purpose, but it's a way to do things without taking a custom RAM byte. hopefully, this won't break Mimic; i think it's safe, because Mimic just sets that bit with X-Magic, and summons aren't usable with that.
alternatively, i wonder what happens if you have the C2/4D9C hook instead put a null ID [EDIT: FFh - 36h, rather] (or something outside the Esper range, at least) in top of A. if that doesn't break the queuing or anything else, maybe have the C2/19C7-linked function test for that instead.
1) expand it to XBA, and then "JMP $4DA6" instead of RTS. no longer counts against Summon limit.
2) have the new code reached from C2/19C7 test Bit 6 of $B1 to differentiate between the two Summon types. admittedly, you'd be expanding this bit from its original purpose, but it's a way to do things without taking a custom RAM byte. hopefully, this won't break Mimic; i think it's safe, because Mimic just sets that bit with X-Magic, and summons aren't usable with that.
alternatively, i wonder what happens if you have the C2/4D9C hook instead put a null ID [EDIT: FFh - 36h, rather] (or something outside the Esper range, at least) in top of A. if that doesn't break the queuing or anything else, maybe have the C2/19C7-linked function test for that instead.
« Next Oldest | Next Newest »
|
||||
Users browsing this thread: 1 Guest(s)