User Tools
battle_draft
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| battle_draft [2020/01/26 05:12] – [Number of hits] simbu | battle_draft [2020/01/26 05:37] – [The Timer System] simbu | ||
|---|---|---|---|
| Line 81: | Line 81: | ||
| [[https:// | [[https:// | ||
| [[https:// | [[https:// | ||
| - | [[https:// | + | [[https:// |
| + | [[https:// | ||
| + | [[https:// | ||
| ==== Relative Agility ==== | ==== Relative Agility ==== | ||
| ---- | ---- | ||
| - | At the start of every fight, FF4 runs a calculation to determine the "base speed" of every character | + | At the start of every fight, FF4 runs a calculation to determine the "base speed" of every character. We refer to this as **Relative Agility (RA)**. This is how many atb ticks the character will have to wait after their last action until they can join the character queue. \\ |
| \\ | \\ | ||
| In order to keep fights a somewhat consistent speed, the vanilla game determines everyone' | In order to keep fights a somewhat consistent speed, the vanilla game determines everyone' | ||
| Line 100: | Line 102: | ||
| However, FF4 also only allows 1 timer to resolve every atb tick, so it has a pointer that loops thru the characters and enemies, and if a timer is expired on the target, processes that specific timer. If no timer is expired it moves on.\\ | However, FF4 also only allows 1 timer to resolve every atb tick, so it has a pointer that loops thru the characters and enemies, and if a timer is expired on the target, processes that specific timer. If no timer is expired it moves on.\\ | ||
| \\ | \\ | ||
| - | This is a pretty complicated topic, but the gist of this is, if more then 1 timer is expired on an atb tick, the game handles only 1 of the timers, then advances to the next atb tick. In practice, this means if you add timers quickly enough, the game must handle the actions in character order.\\ | + | This is a pretty complicated topic, but the gist of this is, if more then 1 timer is expired on an atb tick, the game handles only 1 of the timers, then advances to the next atb tick. In practice, this means if you add timers quickly enough, the game must handle the actions in character order.\\ |
| + | If you want to see this in action, watch the [[https:// | ||
| \\ | \\ | ||
| As well, since each person can have multiple timers on them at once, and only 1 can be processed each time this can lead to some timers never getting processed. An example of this is if you use enough very fast zerkers against plague, even when the count reaches 0, your characters won't die, as it processes the attack timers before the count timer. \\ | As well, since each person can have multiple timers on them at once, and only 1 can be processed each time this can lead to some timers never getting processed. An example of this is if you use enough very fast zerkers against plague, even when the count reaches 0, your characters won't die, as it processes the attack timers before the count timer. \\ | ||
| + | This can be see in the [[https:// | ||
| \\ | \\ | ||
| 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. \\ | ||
Page Tools
