Main Site

Forum Index

1) Get a Hex Editor other than WindHex (which cannot perform step 7).
2) Extract a vanilla copy of the file the ASM hack edited and open it in your hex editor.  You will need CDMage to extract the file from your vanilla ROM.
3) Extract a hacked copy of the file the ASM hack edited and open it in your hex editor.  You will need CDMage to extract the file from your hacked ROM.
4) Go to the offset of specified in the ASM hack in both the vanilla copy and the hacked copy.
5) Count the number of hex digits in the hack (i.e. 0-9, A-F) after the listing of a filename surrounded by brackets <>
<BATTLE_BIN 0x122334>
009AB3DF
<>
In the example above, there are eight characters (0,0,9,A,B,3,D,F).
Divide your count by two and write the number down.  This tells you the number of bytes in the hack.
6) Starting at the offset given by the ASM hack, highlight as many bytes as you written down for Step 5 in the vanilla file.
7) Copy from the vanilla copy to paste into the hacked copy.
8) Reinsert the hacked copy into your ROM by CDMage, MagicISO, etc.

Faith Rod isn't a good idea when you have to face spell gunners.  That's a guaranteed 1HKO.

All right, I'm still going to continue this, but this is impossible to continue without giving ourselves the space to run.

All of the following are to be rerouted to Kanji space.

0x00 -        Flags 1
                0x80 - Break Toggle (if Uneqiup is on; then if this is on = break, if off = steal)
                0x40 - Display Ability Name
                0x20 - Learn on Hit
                0x10 -
                0x?9 - Movement
                0x?8 - Support
                0x?7 - Reaction
                0x?6 - Math
                0x?5 - Aim
                0x?4 - Jumping
                0x?3 - Throwing
                0x?2 - Item
                0x?1 - Normal
                0x?0 - None

0x01 -        Flags 2
                0x80 - HP
                0x40 - MP
                0x20 - Cancel Status
                0x10 - Add Status
                0x08 - Stats
                0x04 - Unequip
                0x02 - Target Enemies
                0x01 - Target Allies

0x02 -        Flags 3
                0x80 - Target Map OR Self-only
                0x40 - Reflectable
                0x20 - Drain Toggle (if attack is flagged stats, HP, or MP, on = drain Stat, off = just damage)
                0x10 - Follow Target
                0x08 - Use Randomly
                0x04 - Faith
                0x02 - Evadeable
                0x01 - Silence (on = affected by silence)

0x03 -        Flags 4
                0x80 - Arc Attack
                0x40 - Direct Attack
                0x20 - Linear Attack
                0x10 - Attack from Range
                0x08 - Brave
                0x04 - Triple Breath
                0x02 - Magic Defense UP
                0x01 - Defense UP

0x04 -        Flags 5
                0x80 - Usable by AI
                0x40 - Cannot Target Enemy
                0x20 - Cannot Target ally
                0x10 -
                0x08 - Same Target Toggle (if on, this means all three statii/procs hit the same target)
                0x04 -
                0x02 -
                0x01 - Evasion Toggle (if evadeable is on; then if this is on = P-EV, if off = M-EV)

0x05:         Flags 6
                0x80 - Zodiac Toggle (if on, Zodiacs modify effectiveness; if off, Zodiacs have no effect)
                0x40 - ???
                0x20 - Weapon Attack
                0x10 - Vertical Fixed
                0x08 - Vertical Tolerance
                0x04 - Weapon Animation
                0x02 - Centered at Self
                0x01 - Can't Target Self

0x06:         Flags 7
                0x80 - Weapon Damage Toggle (if on, take 2H and use weapon type and WP to determine XA and YA; if off, use given XA and YA)
                0x40 - Math Skill
                0x20 - Top-down Targeting (if higher elevation has target, do not hit lower elevation)
                0x10 - Can't Mimic
                0x08 - Random Target (Each attack only hits one panel in AoE range)
                0x04 - Persevere
                0x02 - Quote
                0x01 - Can't Hit Caster

0x07:         Flags 8
                0x80 - Counter Flood
                0x40 - Counter Magic
                0x20 - Animate on Miss
                0x10 - Countergrasp
                0x08 - Proc Toggle (If on, then spell proc, else, status proc)
                0x04 - Random Damage (If on, then variance is 0.5 - 1.5x expected, else no variance)
                0x02 - Poach
                0x01 - No Targeting

0x08           XA (takes multipliers--selecting more than one stat yields the average between them):
                0x80 - PA
                0x40 - MA
                0x20 - SP
                0x10 - (LVL / ?? + ??, to be determined by user)
                0x08 - WP
                0x04 - Naked Stat (if paired with WP yields PA * Br%)
                0x02 - + Toggle (If true, + ZA, if false * ZA)
                0x01 - Number (Sets XA as a number rather than as a stat)

0x09           ZA (does not take multipliers):
                Upper 6 bits are treated as a number for calculation.
                0x02 Control Toggle (See Subsection A)
                0x01 Variate Toggle (See Subsection A)

Subsection A:
If Control Toggle is off, then Variate Toggle behaves + Toggle does for byte 8.
ELSE,
IF Variate Toggle is on, then XA [?] ZA is the hit chance, and YA the damage.
IF Variate Toggle is off, then XA [?] ZA is the damage, and YA the hit chance.

0x0A           YA (does not take multipliers--selecting more than one stat yields the average between them):
                0x80 - PA
                0x40 - MA
                0x20 - SP
                0x10 - (LVL / ?? + ??, to be determined by user)
                0x08 - WP
                0x04 - maxStat (as referenced by HP / MP flags; if neither, this means nothing)
                0x02 - Naked Stat (if paired with WP yields PA * Br%)
                0x01 - Number (Sets YA as a number rather than as a stat)

0x0B           "B1"
                IF Unequip is flagged;
                0x80 = Accessory
                0x40 = Body
                0x20 = Head
                0x10 = Shield 
                0x08 = Weapon
                Lower 3 bits are checked regardless of flags:
                0x04 = Golem
                0x02 = Inflict Moldball Virus
                0x01 = Interchange XA with YA (meaning the + toggle on XA corresponds to YA [] ZA, and the + toggle on ZA corresponds to ZA [] XA, but XA still takes multipliers)
               
0x0C           "B2"
                IF Stats is flagged;
                0x80 = PA
                0x40 = MA
                0x20 = SP
                0x10 = CT
                0x08 = Brave
                0x04 = Faith
                0x02 = EXP
                0x01 = Gil
                0x00 = Level

0x0D          "P"
               Upper 4 bits determine recoil damage (0000 means no recoil, everything else (Upp4bits + 1) / 16 * damage dealt to self.)
               Lower 4 bits determine multiplier to base damage given by (1111 means 3/2 * base damage, everything else is (Low4bits + 2) / 12 * base damage.)

0x0E         "C"
               Upper 4 bits determine critical hit rate at (Upp4bits + 1) / 16 chance IF evasion toggle is on, ELSE, the critical hit rate is 0.
               Lower 4 bits determine proc rate at (Low4bits + 1)  / 16 chance.

0x0F         "N"
               Upper 4 bits determine the maximum number of times an attack hits, as given by Upp4bits + 1.
               Lower 4 bits determine the minimum number of times an attack hits, as given by Low4bits + 1.  If Upp4bits don't equal Low4Bits, then attack for a random number times bounded by the maximum and minimum.

0x10 - Inflict Status/Proc 1 (Unless Same Target Toggle is on, hit target at proc rate)
0x11 - Inflict Status/Proc 2 (Unless Same Target Toggle is on, hit self at proc rate)
0x12 - Inflict Status/Proc 3 (Unless Same Target Toggle is on, hit target at proc rate)
If Same TArget Toggle is on AND IF 0x10, 0x11, 0x12 are all non-zero:
Status/Proc 1 has proc rate * .6 chance to land.
Status/Proc 2 has proc rate * .3 chance to land.
Status/Proc 3 has proc rate * .1 chance to land.
If Same TArget Toggle is on AND IF 0x10, 0x11 are all non-zero:
Status/Proc 1 has proc rate * 2/3 chance to land.
Status/Proc 2 has proc rate * 1/3 chance to land.
If Same TArget Toggle is on AND IF 0x10, 0x12 are all non-zero:
Status/Proc 1 has proc rate * 4/5 chance to land.
Status/Proc 3 has proc rate * 1/5 chance to land.
If Same TArget Toggle is on AND IF 0x11, 0x12 are all non-zero:
Status/Proc 2 has proc rate * 1/2 chance to land.
Status/Proc 3 has proc rate * 1/2 chance to land.

If Same Target Toggle is on, only one status/proc from the above selections CAN be inflicted.  NOTE: If you have an AoE attack that hits multiple targets, it is possible to hit each target with a proc, regardless of type.

0x13 - Restriction Type (reads "ARH-style" table that restricts both attacker and target types as well as "ALMA-style" attack restrictions by support)
0x14 - Consumed Item ID
0x15          "S"
               Upper 4 bits determine chance to consume item if item ID is not 00, given by (Upp4bits + 1) / 16 chance.
               Lower 4 bits, if not 0000, determine the terrain type ID restriction.  Attack can only be executed on terrain with terrain type ID (given by separate table) of Low4bits.

0x16         "R"
               Upper 4 bits determine the maximum range, as given by Upp4bits + Innate Range [non-zero if weapon attack is on, or for THROW, JUMP, ITEM, etc].  If Innate Range > 0, then Upp4bits is signed (and is bounded by [-8, 7]).
               Lower 4 bits determine the minimum range, as given by Low4bits + Innate Range [possibly non-zero if weapon attack is on].  If Innate Range > 0, then Low4bits is signed (and is bounded by [-8, 7]).

0x17         "A"
               Upper 4 bits determine knockback chance (0000 means on physical critical only, everything else has knockback probability of (Upp4bits + 1) / 16.)  This will be considered only if the Lower 4 bits of "A" is 0 OR if random target is on.
               Lower 4 bits determine Area of Effect, but 1111 means target map.

0x18 - Vertical, as given by Vertical + Innate Vertical [non-zero if weapon attack is on, or for THROW, JUMP, ITEM, etc].  If Innate Vertical is not 0 or 255, then Vertical is signed.  If Area of Effect is 0, then 0 Vertical means to ignore this byte.  If Vertical is unsigned and has value of 255, target map.
0x19 - Element
0x1A - CT
0x1B - MP Cost

Status Infliction Flags
0x80 All or Nothing (If Status infliction passes proc chance check, inflict all statii marked)
0x40 Random (If status inflict passes proc chance check, inflict a random selection of statii marked)
0x20 Separate (Each status selected must pass proc chance check separately.)
0x10 Cancel (Replace the word "infliction" with "removal" in the descriptions of each flag other than "Strongly-blocked" under "Status Infliction Flags".)
0x08 Strongly-linked (If no status is inflicted, cancel the main effect of ability.)
0x04 Strongly-blocked (If any status to be inflicted is nullified, do not inflict ANY status)
0x02 Counter-inflict (If the main effect of the ability is blocked, inflict the status anyways at proc chance.)
0x01 Interlinked (If the "Same Target Toggle" is off, all three Inflict Status Procs are inflicted under one RNG check; if off, all three have separate checks)

I'm not sure how I'm going to use this make reactions (and especially their triggers) easier, but it will be the next topic.  The counter data will use the exact same format and I will post it soon.

Two questions:
1) Do you all want the map patch for Besrodio's House as Wiz made for S6?
2) Do you all want a mechanics patch for some things that contradict intended changes (like ninjitsu taking P-EV), or should we wait until after the tournament?

I cannot agree.  There should exist no safe number in this game; no one should have the mental security in this game that having 40 fury or faith will guarantee safety vs. enemy units.

I feel like you're comparing two incongruous things; Time Magic is mostly a support skillset, but Snipe is mostly an offensive one.  Snipe will do more damage, but Time Magic offers more versatility.  Damaging skillsets can be doubled up for a linear increase in power; support skillsets like Time Magic should not be duplicated on any team as the increase of team effectiveness from the second unit is minimal.  Thus, we cannot directly conclude that because snipe exists on more units in Arena than time magic, it is automatically better than time magic.
Damned, you're also confusing the Snipe and Time Magic skill commands with the Archer and Time Mage jobs.  The Time Mage job is awful (and probably could use 10 base SPD to make it easier to build a SC'd Haste2 user or staff spammer), but the time magic itself is not that inferior to snipe.

Faith is mostly irrelevant.  Ever since the changes to faith (+45% to base), any status spell other than odin usually has at least 50% hit outside of bad compats, high M-EV, or innocent.  Usually, it takes M-EV (or bad compat) and low faith to decrease the chance to less than 33%.
The only disadvantage for faith dependency is that a squad using haste/haste2 must then use either compats or faith of at least 50+ to ensure the hit, but the only thing that precludes on your team is ninjitsu spammers and 70/40 unit with DEFUP/cherche.
MP is a worthless consideration.  If your mage unit can't heal his own MP either passively or actively, then your mage wasn't built right.  Even spending one turn to reload MP is worth it as long as you aren't doing it every 2 or 3 turns.
You forgot to mention reflect, which impedes most status spells, but Time Magic is lucky to have Slow2 (arguably its strongest spell) pierce reflect.
Spell synchronization isn't a problem as long as you aren't using the Time Mage job (any 8 SPD job with the MP will do).

Now for the actual skillset comparison:
1) Status infliction favors Time Magic.  Stop is a stronger status than Don't Act and fewer people null it but has a lower hit chance than Arm Aim to compensate for its AoE.  Leg aim has about the same hit chance as Don't Move, but Don't Move has the AoE.  On top of this, Time Magic has slow and haste at mass AoE (which you simply cannot compare to the highly situational seal evil and execute).  TM >> Snipe
2) After some initial setup damage, balance is strong on a knight with no other ranged options.  Although its use is mostly restricted to mediators and armor users, its strength makes an equal to hawkeye (which sets up for a powerful attack).  TM = Snipe
3) The % HP attacks are fairly easy to absorb and while the HP breaks, despite their lower hit chance, are not blocked in the metagame and are permanent.  Snipe also has weapon and shield break, while two swords units with transparent get two chances to break, regardless of evasion.  TM << Snipe
4) Comet and sinkhole function as suppression attacks mostly meant to interfere and cut off enemies.  Cover fire's damage on a martial arts monk is on average stronger and at AoE.  TM < Snipe

My blind hack was meant to override concentrate.  You don't have to ask FFM on this.

I call monk.

What are you all talking about?  Transparent causes the defender to lose his evasion, not the attacker.

Sign extension is something that usually happens at the end of an instruction (e.g. lb is lbu with sign extension at the end); I don't know of any instructions that just do sign-extension and nothing else. Which ones do you mean?

http://personal.denison.edu/~bressoud/cs281-s10/Supplements/ISA_Vol_2.pdf
I was being unclear; I mean the commands labelled under Special3 in this file: the ones labelled EXT (Extend Bit Field), INS (Insert Bit Field), and SEB/H (Sign Extend Byte/Halfword).

From what I understand, coprocessor calls are very generic because the coprocessors were configurable, so the calls themselves are probably little more than "cop1 (argument)".  I could add a checkbox to the form to disassemble cop1 calls to PSP FPU instructions, but I don't think I can make that the default option, because then the tool would only be correct for the PSP.

Point taken.  I only wanted the floating point and possibly CACHE command calls.

For starting offsets, would it make sense to also map to another destination offset? e.g., to start disassembling the file at 0x10000 and map the addresses to 0x78000 (to correspond to a RAM offset, perhaps?)

For FFT, this is unnecessary, but in general, for other games that map sections of a file (in the ROM) dynamically into the RAM, that may be useful.

http://math-atlas.sourceforge.net/devel/assembly/mips-iv.pdf
This is another site that contains the opcodes for all the instructions the previous link does not have.