FF7/DamageFormula - Revision history

NFITC1: /* 0: Physical Accuracy Check */ There is an enemy check on the Dex bonus that I didn't notice before. Physical Chance is unaffected.

2021-05-20T13:16:40Z

‎0: Physical Accuracy Check: There is an enemy check on the Dex bonus that I didn't notice before. Physical Chance is unaffected.

2021-05-17T17:00:23Z

‎0: Physical Accuracy Check: I can't decide on a layout, but this is slightly more organized and understandable

2021-05-17T16:57:10Z

‎0: Physical Accuracy Check

2021-05-17T16:49:55Z

‎0: Physical Accuracy Check: Added pseudocode for physical accuracy check

2019-05-23T02:11:14Z

39 revisions imported

2018-04-04T09:34:18Z

38 revisions imported

2016-02-29T17:00:00Z

‎X1:: Bad human can't math. :(

2016-02-29T16:59:32Z

‎Variance( Damage ):

2016-02-29T15:34:54Z

‎X1:: Conciseness

2015-02-23T15:37:00Z

‎Damage Formula's description: Sorry, Akari. This section needed a rewrite.

@@ Line 377: / Line 377: @@
 Physical Chance = (Actor's Dex >> 2) + action physical hit rate
-Actor's evade = (Actor's Dex >> 2) + Actor's Physical evade
+If Actor is enemy then
-Target's evade = (Target's Dex >> 2) + Target's Physical evade
+	Actor's evade = Actor's Physical evade
 If HitChance = -1 Then

@@ Line 401: / Line 401: @@
 if HitChance < Miss Chance then
 	Set Miss flag
-End IF
+End If</pre>
-Check_For_Cover() {
+====Check_For_Cover====
 	This is where the game checks if the target is covered under a "cover"ing ally.
 	It only applies to Player Characters
-	It might be more complicated that I'm seeing, but that is definitely ONE of its functions
+	It might be more complicated than I'm seeing, but that is definitely ONE of its functions
-FuryAdjust(HitChance) {
+====FuryAdjust(HitChance)====
-	If HitChance < 255 then
+<pre>	If HitChance < 255 then
 		If Actor is in Fury Status
 			HitChance = HitChance - ((HitChance * 3) / 10)
 		End If
 	End If
-	return HitChance
+	return HitChance </pre>
 ===1: Magical Accuracy Check===

@@ Line 399: / Line 399: @@
 Miss Chance = (([0..65535] * 99) / 65535) + 1 ;essentially [1..100]
-if HitChance > Miss Chance then
+if HitChance < Miss Chance then
 	Set Miss flag
 End IF

@@ Line 358: / Line 358: @@
 ===0: Physical Accuracy Check===
 ''0x5DDBB0''
-<pre>
+<pre>;For the purposes of this code, "Dex" means the adjusted Dexterity of the actor/target if any in-battle dex bonuses have been granted.
-todo
+;Same holds for the Physical Evade. Physical Hit rate has no in-game bonus opportunities.
-It's long so I'll tackle it when I have a lot of time on my hands
 </pre>

@@ Line 73: / Line 73: @@
 z = z * ( 512 - target's defense ) * Attack's Power
 Damage = z >> 13
-//This is a bit-shift left by 13 which is mathematically equivalent to dividing by 4096, but it's important to note that it doesn't actually divide as this is the source of the damage overflow glitch
+//This is a bit-shift left by 13 which is mathematically equivalent to dividing by 8192, but it's important to note that it doesn't actually divide as this is the source of the damage overflow glitch
 If Critical Damage Flag is set

← Older revision	Revision as of 02:11, 23 May 2019
(No difference)

← Older revision	Revision as of 09:34, 4 April 2018
(No difference)

@@ Line 259: / Line 259: @@
 ''0x5DE988''
 <pre>
-Damage = Damage ([0..255] + 3841) / 4096  //from RNGLUT in KERNEL.BIN
+Damage = Damage ([0..255] + 3841) >> 12  //from RNGLUT in KERNEL.BIN
 If Damage == 0

@@ Line 1: / Line 1: @@
-== Damage Formula's description ==
+==Accuracy Function considerations==
+Each of the upper nybble of the damage calculation determines what checks are done to accuracy of the action and whether or not it will connect, be critical or miss. Here are the functions in order processed based on the upper nybble:
 =Damage Calculations=