User Tools
battle_mechanics
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| battle_mechanics [2023/12/26 20:45] – external edit A User Not Logged in | battle_mechanics [2025/03/25 17:06] (current) – [Run Buffering] - adding link to example antidale | ||
|---|---|---|---|
| Line 116: | Line 116: | ||
| This can also lead to virus/sap, wall, and other status effects never running out. \\ | This can also lead to virus/sap, wall, and other status effects never running out. \\ | ||
| \\ | \\ | ||
| - | Typically this is referred to as queue jam, there are so many actions waiting to be processed, that each character has to have multiple atb ticks pass before their timers are checked, and during these ticks, their timers do continue to count down. Example uses of this include, using enemy/ | + | Typically this is referred to as queue jam, there are so many actions waiting to be processed, that each character has to have multiple atb ticks pass before their timers are checked, and during these ticks, their timers do continue to count down. Example uses of this include, using enemy/ |
| \\ | \\ | ||
| On this same line of thought, its important to recognize how this interacts with your party order. Characters are added to a queue to have their menu pop up based on this same system, which is why in low agility situations you will find your party tends to not change its order too much.\\ | On this same line of thought, its important to recognize how this interacts with your party order. Characters are added to a queue to have their menu pop up based on this same system, which is why in low agility situations you will find your party tends to not change its order too much.\\ | ||
| Line 142: | Line 142: | ||
| ==== Run Buffering==== | ==== Run Buffering==== | ||
| ---- | ---- | ||
| - | One way to artificially slow down the game is to try running during a fight you can't run from. This will cause a message to pop up, which halts the atb from advancing until the message goes away. This can give you a little bit more time to get into your menus. Typically any fight that has monsters lower level than 97 will let you run away the first atb tick you press the buttons. If the fight is marked as one you can't run away, the can't run message will display, freezing the atb for 1-2 seconds. | + | One way to artificially slow down the game is to try running during a fight you can't run from. This will cause a message to pop up, which halts the atb from advancing until the message goes away. This can provide |
| \\ | \\ | ||
| Just don't use it too much, because every time the message does pop up, 1 atb is advancing, and if you use it before your character' | Just don't use it too much, because every time the message does pop up, 1 atb is advancing, and if you use it before your character' | ||
| + | |||
| + | An advanced example of run buffering, where consecutive inputs are successfully run buffered can be seen [[https:// | ||
| ==== Practical Take-aways ==== | ==== Practical Take-aways ==== | ||
| ---- | ---- | ||
battle_mechanics.1703623533.txt.gz · Last modified: 2023/12/26 20:45 by A User Not Logged in
Page Tools
