°Aslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=25;area=showposts;start=450e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index2b8a.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=25e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index2b8a.html.zxJЫh^                    ╚рХдпрOKtext/htmlISO-8859-1gzip0|╓пр        Wed, 11 Mar 2020 08:19:47 GMT0є░░ о0оPоАз▓ЁоIЫh^        M"пр Show Posts - assassin

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - assassin

451
yep, see the Event Commands file:
http://www.angelfire.com/al2/imzogelmo/patches.html

452
Game Modification Station / Re: FF6 - possible bug
« on: August 05, 2013, 02:14:19 PM »
Yeah, probably skip the added call if somebody's currently in the Item menu.  Per Terii's C2/111B comment, $2F41 holds whether you're currently in a menu.  Do you know what indicates whether you're specifically in the Item menu?

453
Game Modification Station / Re: FF6 - possible bug
« on: August 05, 2013, 01:04:33 PM »
well, doing frame-based update would be uber slow.  but the idea i was considering (have C2/1423 do a "LDA #$0A / JSR $6411" right after the C2/62C7 call) probably isn't that bad in speed.  however, my prior post is showing concern as to what happens if the menu is updated while you're browsing it -- in particular, if you've already got an item slot highlighted with the cursor (perhaps as the first step of switching it with another slot).  it seems like discrepancies could be created.

454
Game Modification Station / Re: FF6 - possible bug
« on: August 04, 2013, 12:04:19 PM »
then again, doing an instant update could allow for the Item menu to be updated while you're browsing the Item menu.  could this cause problems?  if so, maybe the current lag is desirable (or any fix for it would need a check to see whether you're in the menu).

455
Game Modification Station / Re: FF6 - possible bug
« on: August 01, 2013, 11:46:02 AM »
Quote
The item doesn't reappear in inventory until the character that uses it gets their ATB refilled.

i don't think you need to have their ATB refilled, but rather change from one character to another with X or Y.  iirc, the Item List you see can't update while you're just sitting on a character's main battle menu as somebody else is altering the Item inventory.  so it's the same deal with Stolen items.   X/Y triggers the "refresh".

or besides X/Y, having a character take a turn, so another gets first in line.  iow, i think it's tied to having the triangle cursor switch onto a new character.

anyway, it turns out that the inventory adding, after the C2/54DC call in C2/62C7, has two steps:
1) Copy $2E72-$2E76 buffer to a $602D-$6031 [plus offset] buffer , as many as 4 times
2) Copy $602D-$6031 buffer entry/ies to Item menu

C2/62C7 does the first step.  if we're at the end of battle, C2/492E does the call to handle #2 (one call, which loops if there're multiple buffer entries) right after that.  if we're mid-battle, we're reliant on the triangle cursor switch.  or if that never happens, then it's addressed when the battle is finished.

this explains the lag in the Item menu update after acquiring an item, if we didn't move the cursor off of a given character in the process.  this can be prolonged awhile, if we have characters acting automatically.  i don't think there are any problems beyond wait (i.e. no item loss), since the $602D buffer apparently has 16 entries maximum, which is plenty.  (6 stealings + 6 Metamorphings = 12.  though Pandora's Box can exceed that if you indeed implemented the multiple stolen items per enemy?)  the only way i can think of to exceed this in a normal, For-What-Ails-Ya-fixed game involves a character Life 3'ing themselves, trying to use an item, and coincidentally getting killed before they can act -- and doing this at least 5 times (12 + 5 > 16).
EDIT: ok, that last sentence is wrong, because having their main menu come up again when their ATB refills after revival will refresh the Item menu.

elsewhere (i.e. won items), Square just calls C2/6279, which handles Steps #1 and 2 in one shot.  so why do they split up the steps in these cases?  my guess is speed.  at battle end, C2/492E doing step #2 for all characters with one Bank C1 call (LDA #$0A / JSR $6411) is faster than having C2/62C7 do this far call for each character separately.

however, as mentioned, Step #2 doesn't always instantly follow #1 mid-battle.  since i don't favor editing C2/62C7, a fix for the lag would be to have C2/1423 do a "LDA #$0A / JSR $6411" right afterwards.  a far call consumes some cycles, but it can't be *that* bad.

to refresh: this lag behavior is in the original game, and isn't caused by the "For What Ails Ya" patch.

456
Submissions / Re: FF3us - 255 hours on timer
« on: June 05, 2013, 11:54:58 PM »
it was horrible! ;)  either:

1) change all references to $326C to have your new function's address, wherever that may be.  suppose it were located at C3/1234.  you'd change C3/311F to "20 34 12    JSR $1234", and C3/354B to "4C 34 12   JMP $1234".  C3/3143 and C3/3167, which enter Function C3/326C midway through at C3/3295, would also need to be adjusted.

so more generally, the format of the (non-relative) calls and branch instructions is: opcode (20h for the JSR, which is a call, or 4Ch for the jump JMP), low byte of offset, high byte of offset.  for a far call or jump, it's: opcode (22h for JSL, or 5Ch for JML), low byte of offset, high byte of offset, bank.

2) keep the original function in the same place, and just branch to free space to finish executing the added part.  so you'd include the first 7 instructions of Leviathan Mist's new code as written, then the first "JSR $04B6" would become "JMP $1234".  then at C3/1234, you'd have everything from the "JSR $04B6" through the end of his function.

this has the advantage of using less free space and not having to modify the functions that call or jump to C3/326C.  a disadvantage is that it's slightly slower due to the added "JMP $1234" instruction, but i doubt that matters.  hell, changing the "JSR $04B6" right before the "RTS" to a "JMP $04B6" like the disassembly recommends will make up for some of that.

457
Submissions / Re: FF3us - 255 hours on timer
« on: June 05, 2013, 08:58:22 PM »
Quote from: assassin
that said, i still need to do the frame-by-frame check, and verify that there are indeed 61 frames between display updates.

confirmed this as well.

:wtf: were they thinking?

i did call them "monkeys" for it, but i can understand their mistake.  they want to update the display every 60 frames, so they set a "frame delay" variable to 60 in Function C2/B936.  if Function C2/B925 worked like:

- decrement frame delay variable
- branch to C2/B936 if the variable is zero

their delay would be as intended.  but the function does the variable check *before* decrementing it.  apparently, this is to make the timer display update the very first time C2/B925 is called in a battle.  i think that the frame delay variable is a default of zero to start a battle (as are many other variables), so my hypothetical order above wouldn't work right in that case.

anyway, Square's order means that C2/B936 won't be called on a frame where the variable goes from 1-->0, but on the frame _after_ that.  to compensate for that extra 1-frame wait, they should have made Variable $628F one smaller, at 59.

and that's what i shall do, in The Easiest Patch Ever (tm).

458
Submissions / Re: FF3us - 255 hours on timer
« on: June 05, 2013, 05:14:57 AM »
hah; confirmed.  the 2-second jump will occur 61 seconds into the battle, but maybe sooner..  i'm not sure on what frame alignments a battle can start, but suppose the real timer is at 20 seconds and 0 frames when a battle commences.  the initial display will indicate those 20 seconds.  then the display is updated 61 frames later, when the real timer is at 18 seconds and 59 frames -- meaning you'll see the seconds go from 20 to 18 without the 19.

those monkeys were apparently confused by C2/B925, even though it's right above C2/B936.  i think changing the "LDA #$3C" at the start of the latter function to "LDA #$3B" oughta solve it.  that said, i still need to do the frame-by-frame check, and verify that there are indeed 61 frames between display updates.

459
Submissions / Re: FF3us - 255 hours on timer
« on: June 05, 2013, 04:41:30 AM »
if you're in a battle, C2/B936 converts the timer into minutes and seconds for display.

looking at Variable $628F, it seems that this function is called every 61 frames rather than every 60?  meaning the display update will lag 1 frame behind each actual second update.  and if you're in a battle for over 60 seconds, you might see a 2-second decrement in this timer display..

maybe i'm misreading something here.  i'll test it in an emulator going frame-by-frame.

460
Game Modification Station / Re: New Skill Help
« on: May 28, 2013, 10:20:43 PM »
no prob.  ah, i didn't stop to think that things like the "REP #$20" were missing.

461
Game Modification Station / Re: New Skill Help
« on: May 28, 2013, 07:34:19 PM »
When removing the JSR, did you replace it with 3 NOPs?  Normally, I wouldn't harp on your pasted instruction addresses, because that would make me a dick, but it's worth asking, given the damage failure is puzzling me.

462
Game Modification Station / Re: New Skill Help
« on: May 28, 2013, 04:23:09 PM »
Change C2/3DF7 to point to 3BCB .  Keep your C2/4263 function, but drop the "JSR $3BCB".

463
Game Modification Station / Re: New Skill Help
« on: May 28, 2013, 01:20:45 AM »
the functions reached from Table C2/42E1 are the once-per-strike special effects.  those pointed to by C2/3DCD are the once-per-target special effects.  add a Mantra function of the latter category that calls Evil Toot.

464
Game Modification Station / Re: FF6 Improvement Project
« on: March 09, 2013, 09:37:09 PM »
or you could duplicate The Sealed Door Fix's change using a map editor.  shouldn't take long, though it won't do anything to address gobs of bytes being altered.

465
Game Modification Station / Re: FF6 Improvement Project
« on: March 08, 2013, 06:35:18 AM »
ok, Novalia's added to the patch documentation to address this.  the patch itself is unchanged, indicating he's confident it works.

i can't think of any other patches in the Improvement Project that edit Maranda's interior map (nor Jidoor's, as previously stated).  if one interprets the Readme warning verbatim, simply modifying the ROM with a map editor is enough to possibly cause clashes, even if it's a different map you're editing.