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 [2020/02/02 15:25] – [Magic Damage] simbu | battle_mechanics [2025/03/25 17:06] (current) – [Run Buffering] - adding link to example antidale | ||
|---|---|---|---|
| Line 24: | Line 24: | ||
| Tables of all the different modifiers listed [[Formulas# | Tables of all the different modifiers listed [[Formulas# | ||
| \\ | \\ | ||
| - | After all these modifiers, you are left with an attack value, which is then multiplied by a random number between 1 and 1.5, and then defense is subtracted. Note the multiplication is before the subtraction, | + | After all these modifiers, you are left with an attack value, which is then multiplied by a random number between 1 and 1.5((Note that the upper limit will actually be lower than 1.5x if attack power is over 510. See details [[formulas## |
| ** Damage Per Hit = Final Attack Power * (Random between 1 and 1.5) - Target Defense. ** | ** Damage Per Hit = Final Attack Power * (Random between 1 and 1.5) - Target Defense. ** | ||
| \\ | \\ | ||
| Line 36: | Line 36: | ||
| **Accuracy** is **weapon base accuracy + level/4**. \\ | **Accuracy** is **weapon base accuracy + level/4**. \\ | ||
| \\ | \\ | ||
| - | Several things effect accuracy as well, most notably being in the back row. If you don’t have the longrange | + | Several things effect accuracy as well, most notably being in the back row. If you don’t have the long-range |
| - | A list of all accuracy modifiers can be found [[formulas# | + | * Your accuracy is halved when attacking from the back row |
| + | * Your accuracy is halved | ||
| + | This means accuracy can be 1/4th its value if both conditions are active. \\ | ||
| + | |||
| + | A list of all accuracy modifiers can be found [[formulas# | ||
| \\ | \\ | ||
| For each attack multiplier, a random number is rolled, and based on accuracy its determined if it hits or not. So for 10 attacks with 80% accuracy, about 8 of them should hit, though this could be more or less.\\ | For each attack multiplier, a random number is rolled, and based on accuracy its determined if it hits or not. So for 10 attacks with 80% accuracy, about 8 of them should hit, though this could be more or less.\\ | ||
| Line 64: | Line 68: | ||
| Magic damage is handled much the same as physical damage is, except spell power is drawn from a table. You can look [[spell_data|here]] for a list of most spells power and accuracy, or refer to the Magic Guide, for the base power of every spell. This is also modified by resistances and stuff, much the same as physical attacks. Refer to the algorithm guide for a complete list of spell power modifiers. \\ | Magic damage is handled much the same as physical damage is, except spell power is drawn from a table. You can look [[spell_data|here]] for a list of most spells power and accuracy, or refer to the Magic Guide, for the base power of every spell. This is also modified by resistances and stuff, much the same as physical attacks. Refer to the algorithm guide for a complete list of spell power modifiers. \\ | ||
| \\ | \\ | ||
| - | Accuracy and spell attack modifiers are also handled similar to physical system.\\ | + | Accuracy and spell attack modifiers are also handled similar to the physical system.\\ |
| **White magic multipliers** are **Will/ | **White magic multipliers** are **Will/ | ||
| **All other magic Multipliers** are **Wisdom/ | **All other magic Multipliers** are **Wisdom/ | ||
| Line 71: | Line 75: | ||
| **Spell accuracy** is the **base spell accuracy+ wisdom or willpower/ | **Spell accuracy** is the **base spell accuracy+ wisdom or willpower/ | ||
| \\ | \\ | ||
| - | Just like physical damage, spell damage per hit is spell power after modifiers, times random number between 1 and 1.5, minus magic defense.\\ | + | Just like physical damage, spell damage per hit is spell power after modifiers, times random number between 1 and 1.5((Note that the upper limit will actually be lower than 1.5x if attack power is over 510. See details [[formulas## |
| \\ | \\ | ||
| If a spell has the option to be single cast, or multi-targeted, | If a spell has the option to be single cast, or multi-targeted, | ||
| \\ | \\ | ||
| - | Enemies are bugged such that magic evasion is never applied, but for characters you can calculate | + | Enemies are bugged such that magic evasion is never applied, but for characters you can calculate |
| \\ | \\ | ||
| Note that if magic defense equals 255, all spells automatically miss (valvalis and some twinharp bosses). | Note that if magic defense equals 255, all spells automatically miss (valvalis and some twinharp bosses). | ||
| Line 83: | Line 87: | ||
| [[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. 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 | + | At the start of every fight, FF4 runs a calculation to determine the "base speed" of everyone in battle, both party members and enemies. We refer to this as **Relative Agility (RA)**. This is how many atb ticks the character/ |
| \\ | \\ | ||
| 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 106: | Line 109: | ||
| \\ | \\ | ||
| 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. \\ | ||
| \\ | \\ | ||
| - | 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 139: | 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 level 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.1580657139.txt.gz · Last modified: 2020/02/02 16:25 (external edit)
Page Tools
