Reply to thread

Message: <blockquote data-quote="RoSoDude" data-source="post: 4885" data-attributes="member: 2224">Oh, I get why freeze is an issue. Squaresoft made it so that freeze stops a character's ATB and stops them from executing any queued command, but it doesn't actually take the move off the queue (nor stop the player from queuing one if they had full ATB when they became frozen). This is a problem for the CTB Wait Addon since it stops ATB for all participants either1. If a command menu is open2. If a command is queuedThis design keeps things moving without letting the queue get backlogged. However, it doesn't play well with freeze status because the queued command prevents time from passing, so freeze can never wear off and the queued command can never execute, so the battle gets stuck.What you can do to get around this is to press L+R to flee until the character is unfrozen. Fleeing with CTB Wait reverts to Active ATB mode (pausing only during animations). In a bossfight you'll never actually flee, of course. I believe this would work even if your entire party were frozen, as I check for the fleeing input byte which is set independently from ATB.I may eventually run to fix this properly, but it will be difficult. Instead of just checking if the queue isn't empty, I'd need to check if the queue points to a character under the freeze status. For that I need to study the RAM to know how to interpret the queue pointer and to find the byte that stores freeze, and I'd also need to carve out some space for new assembly code by optimizing some other subroutines. I'll give it a shot sometime, but no guarantees!</blockquote>

Verification

This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.

Accept Learn more…