Aslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&topic=248.30e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index3d09.htmldelayedslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&board=8.160e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index3d09.html.zx&h^ЋPOKtext/htmlISO-8859-1gzip8:PHTue, 10 Mar 2020 23:59:22 GMT0 0P&h^ P FF6 - possible bug

Author Topic: FF6 - possible bug  (Read 11075 times)

assassin

  • Bane of Retards
  • *
  • Posts: 1,033
  • space bears are not gentle!
    • View Profile
    • My Barren Webpage
Re: FF6 - possible bug
« Reply #30 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).

Lenophis

  • Forum Overlord
  • *
  • Posts: 1,688
  • Gender: Male
  • I sad
    • View Profile
    • Slick Productions
Re: FF6 - possible bug
« Reply #31 on: August 04, 2013, 11:43:23 PM »
I'm not really sure how to get that menu updated in realtime, or more frequently than it is now. Probably very time consuming and slow. :hmm:

119 bugs fixed and counting.

assassin

  • Bane of Retards
  • *
  • Posts: 1,033
  • space bears are not gentle!
    • View Profile
    • My Barren Webpage
Re: FF6 - possible bug
« Reply #32 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.

Lenophis

  • Forum Overlord
  • *
  • Posts: 1,688
  • Gender: Male
  • I sad
    • View Profile
    • Slick Productions
Re: FF6 - possible bug
« Reply #33 on: August 05, 2013, 01:52:54 PM »
Yeah, that sounds like it could create a headache. Item replacement, item duplication, item loss. It's a mess.

119 bugs fixed and counting.

assassin

  • Bane of Retards
  • *
  • Posts: 1,033
  • space bears are not gentle!
    • View Profile
    • My Barren Webpage
Re: FF6 - possible bug
« Reply #34 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?

Lenophis

  • Forum Overlord
  • *
  • Posts: 1,688
  • Gender: Male
  • I sad
    • View Profile
    • Slick Productions
Re: FF6 - possible bug
« Reply #35 on: August 05, 2013, 02:21:24 PM »
Unfortunately, I do not.

119 bugs fixed and counting.

assassin

  • Bane of Retards
  • *
  • Posts: 1,033
  • space bears are not gentle!
    • View Profile
    • My Barren Webpage
Re: FF6 - possible bug
« Reply #36 on: December 20, 2013, 06:55:22 PM »
so i was talking to Novalia Spirit a couple weeks ago:

Quote from: novalia
$2BAF: Command selection for ally 1
$2BB0: First subcommand selection in queue

$2BB7: Command selection for ally 2

$2BBF: Command selection for ally 3

$2BC7: Command selection for ally 4

like his $2BB0 description suggests, the allies don't seem to be fixed numbers, but based on the order in which you're choosing their commands.

to know the latest ally (i.e. whoever's menus you're currently using), i think $3A6A is the pointer.

there's also the limitation that if you back out of a command menu into the main menu, the variable still holds the command's ID.  so you'd have to combine use of these variables with $2F41 to verify that you're indeed in a submenu at the time.

anyway, the commands to check for would be Item (01) and Throw (08).  Tools (09) shouldn't need a check, because its list is generated just at battle start, and you can't move stuff around with it anyway.