øAslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=25;area=showposts;start=60e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index8123-2.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=25e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index8123-2.html.zx@›h^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ ,/KþOKtext/htmlISO-8859-1gzip0|ÖKþÿÿÿÿÿÿÿÿWed, 11 Mar 2020 08:19:36 GMT0ó°° ®0®P®€§²ð®?›h^ÿÿÿÿÿÿÿÿ!+Kþ 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

61
am clueless on this, so forgive any flailing..  is there a "Barrel Breaking" flag (or constant value in a Barrel State variable) that might be detectable with Cheat Search?  pretending there is, is the problem that the game lets Diddy pick up a barrel after this is set, or that the flag can be set after he's already picked up the barrel?  (or neither.)

how does the wall figure into breakage when there's no throwing?  even though the floor's moving parallel to it, is there some "is touching wall?" test?

63
Game Modification Station / Re: New patch: Menu Malarky Bug fix
« on: February 27, 2017, 07:50:14 PM »
The only values held in $86 and $87 are 0Fh, 1Fh, 3Fh, 7Fh and FFh. By the looks of it, these are related to map sizes and are used for clamping things like NPC locations to map coordinates (e.g. you can't have an NPC at (40, 8) on a 32x32 map).

thanks.

Quote
or maybe it'll make things worse, as entities "occupying" two tiles at a time increases their chances of colliding.

My patch doesn't do anything if there's already an object at the destination tile, and as far as I understand the game generally does a pretty good job of maintaining this.

to be sure, by "colliding", i didn't mean inhabit the same space, but just the game detecting the entities made contact, and triggered a battle.  a patch that temporarily enlarges the "hitboxes" of one or both entities would likely trigger battles more readily.

re Locke and guard: ah, that's a good explanation.

64
Quote from: me
oh, it's a bug.
That is speculation :laugh:

good sir, i would take deduction based on facts and reasoning over blind faith any day.  :terrydia:

what possible purpose would there be to ignoring the most significant byte of a stat?  while you see "speculation", i see borderline infatuation with Square.  if they'd spilled sake on their keyboard during development, would you worship the stain 15 years later?

Quote from: Jorgur
Here we go again.

i don't recall this aspect being argued here before.  in fact, it seems to have been agreed upon as a bug from the 2004 GameFAQs threads forward.  :eek:

=======================

Xardas:

download this patch and document if you haven't already: http://slickproductions.org/forum/index.php?action=dlattach;topic=2179.0;attach=1787

so with that patch applied, do this: at C2/862D, put "JMP $80E9" (4C E9 80).  done.

OR paste the new Knife code into the relevant part of the Chicken Knife function, which starts at C2/8626.  like you said:

Quote
So is there any possibility to copypaste the M from knife formula to Chicken Knife formula? Since the speacial part of Chicken Knife lies in Attack Power, not the multiplier.

that'd involve copying the 18 bytes at C2/810B (in "Delta 3 to Fractional M.txt") to C2/864F.

that said, an issue:
1) that alternate patch apparently uses my idea of flooring of M at 128, even though we'd agreed that Jorgur's method of doing away with Minimum M was better.  probably a copy+paste mistake from older patch versions, or being lenient on how "alternative" the patch is.

to remedy it, i recommend opening "Fractional M 1.2.txt" (found inside http://slickproductions.org/forum/index.php?action=dlattach;topic=1975.0;attach=1312), and pasting:
a. C2/8A0D , 9 bytes
b. C2/940C , 8 bytes

(use the bytes that include NOPs)

65
Game Modification Station / Re: New patch: Menu Malarky Bug fix
« on: February 27, 2017, 02:57:07 AM »
yep, tight code.  a few questions:

- how do the $86 and $87 bitmasks in Functions C0/7CE1 and C0/7D03 work?  what are the criteria for choosing different ones?
- what benefits and drawbacks might there be to achieving "proper" $087A,Y and $087B,Y (and thus $1E and $1F) for left/up movers by always doing rounding for them (e.g. using the [upper word] pixel coordinate plus 000Fh) in Function C0/7CE1?  your way is narrower and probably safer.  now, it might miss remedying some other cases.  but on the flip side, are there known cases that are direction-agnostic, where you'd want to keep the rounded down coordinate?
- sometimes, the direction in $087E,Y can be above 4, but apparently not when C0/5263 is called.  any idea what these higher values/bits mean, or in what contexts they are or aren't stripped out?
- there is weirdness with the Opera House rats encounter triggering:
http://mnrogar.slickproductions.org/phpBB3/viewtopic.php?f=2&t=236&p=2680#p2680

i wonder how much of that unfairness and/or lag is specific to cases where one or more entity is moving up/left, and thus the goofy rounding happens.  maybe your patch will fix some of this.  or maybe it'll make things worse, as entities "occupying" two tiles at a time increases their chances of colliding.  now, even if it is the latter answer, it'd be hard to blame your patch, as the idea that an entity straddling two tiles is in both seems pretty sound to me... and it's ultimately the limited tile-based placement system that's probably at the root of things.

66
oh, it's a bug.  unless you actually believe Square was trying to L? Pearl-ize or Ogre Nix-ize Knives (to borrow FF6 terms).  and if they were truly going for what amounts to a random roll, why wouldn't they be creative and take it from some other input value?

while the discussion did get spirited, i don't think the fact that Square mucked up was ever a point of contention.  rather, it was whether if had they done the more sensible, coherent thing formula-wise, would the resulting damage had been deemed suitably balanced if and when they observed it in play testing?

67
Game Modification Station / Re: New patch: Menu Malarky Bug fix
« on: February 21, 2017, 04:44:13 PM »
Phantom Train exterior is super wide, but there being two locations might mean there're two maps:
Quote from: Corundum
141 08D Phantom Train, exterior (after detaching rear cars)
142 08E Phantom Train, exterior (before detaching rear cars)
also, i'm not sure whether you needing to go inside some train cars to progress serves to break it up into pieces (further).

anyway, this is a good reference:
http://vgmaps.com/Atlas/SuperNES/index.htm#FinalFantasyVI

as the maps seem to be actual size, and you can rule stuff out if the listed dimensions are smaller than the threshold.  (but will still need to view some contenders, as it'll combine multiple maps onto some images.)

68
Game Modification Station / Re: Possible FF6 event bug on game reloading
« on: February 19, 2017, 12:55:59 AM »
Madsiur: yes, identifying patches for allocation documents.  as mentioned, the reason is interoperability with other patches: "however, a theoretical hacker that's treating the original function as more standalone might lean on its not clobbering certain things, not wanting to consume push/pull space themselves."  iow, while i might clobber registers in a patch based upon observing that the caller doesn't "need" them kept a certain way, a hacker calling a vanilla function might be looking at it from an opposite direction: the routine doesn't alter the registers (at least not without preserving them), so why should the hacker feel the need to preserve them?  they're two valid ways of looking at things, but their difference, plus the two hackers' commonality of wanting to minimize code space, sets the stage for conflicts.

i won't say this is as important to list as code addresses or RAM variables, but it does fall under resource consumption, and concerns interoperability.

---------

Imzogelmo: speaking of stack usage, one thing perhaps worth reporting is increase in maximum stack depth during the function.  hopefully, the makers left GOBS of stack space to spare, but we don't know that for sure.  ultimately, it's absolute stack address that matters, but i have no idea how to say what that'd be in all the situations a function can be called..  so i'd probably keep it relative, and go for delta from vanilla at whatever the most stack-extended part of the function is.

69
Game Modification Station / Re: Possible FF6 event bug on game reloading
« on: February 16, 2017, 12:41:49 AM »
let the Topic Creator be the arbiter of that. :P  he didn't seem to mind discussing Patch Allocation and things consumed by a patch two weeks ago.  register clobbering is another form of consumption.  code addresses aren't the be-all and end-all.

creating another topic as a follow-up to a discussion that developed in this one would've been pointless and wasteful, imho.

70
Game Modification Station / Re: Possible FF6 event bug on game reloading
« on: February 15, 2017, 08:59:09 PM »
maybe also registers clobbered, i.e. ones that the vanilla version of a function doesn't alter.  if vanilla doesn't care about a register that a patch changes, e.g. it overwrites it shortly before or after calling the patched function without reading it, that might be good enough to get the patch made without using free space for push/pull.  however, a theoretical hacker that's treating the original function as more standalone might lean on its not clobbering certain things, not wanting to consume push/pull space themselves.

computer science teachers would probably demand every function list these things at the top under the description.  along with annoying crap like "input" and "output", and big-O notation of execution time.

now, some judgment needs to be used as to whether vanilla altering the register is an existing form of "clobbering", or if it's setting a meaningful value that a caller might look at.  but that's fairly obvious in most cases, even if i couldn't readily define it.

there's currently a patch i'm dragging my feet on updating because while i can shrink free space by 3 bytes as-is, i could shrink another 2 bytes by clobbering Y.  vanilla overwrites Y shortly before and somewhat after the function in question.  so it ought to be safe, but has potential compatibility issues.

71
haha.. i didn't even remember what the kid's name was.  anyway, i prefer bloodwine.  it is a good day to die!!

------------

swiped from MathOnNapkins' disassembly:

Code: [Select]
        ; branch if torch is already lit
        LDA $0540, Y : ASL A : BCS .return
       
        ; Light the torch?
        LSR A : ORA.w #$8000 : STA $0540, Y
       
        LDA $08 : BNE .notZero
       
        ; why would this ever happen give the code base we have?
        ; seems like this would permanently light the torch?
        LDA $0540, Y : STA $7EFB40, X
   
    .notZero
   
        LDA $0540, Y : AND.w #$3FFF : TAX : STX $08 : PHX

        LDY.w #$0ECA

(37 bytes)

wow, somebody at Nintendo really likes "LDA $0540, Y".  i don't (or at least not to the point of needing a "Do Not Disturb" sign every time we occupy the same room):

Code: [Select]
; branch if torch is already lit
LDA $0540, Y
BMI .return
       
; Light the torch?
ORA.w #$8000
STA $0540, Y

ldy $08
bne .notZero

STA $7EFB40, X

.notZero

; rest unchanged

AND.w #$3FFF
TAX
STX $08
PHX

LDY #$0ECA

(29 bytes)

if for some reason a caller looks at Carry (they don't seem to, as it's not like the function returns meaningful results on it), i can keep the first three instructions, then do "SEC / ROR".

am editing a bit further up than i set out to, but might as well make use of the already-commented code.

72
so a minor detail? ;P  oh man..  good catch.  i pasted traces of the function execution for this patch and prior one, then stared at the screen for awhile, as they were identical when possible.  finally found it:

Quote from: me
; total = 57 bytes versus 63 original

that should read "53 original".  i was absent the day they taught subtraction in 2nd grade (or counting in kindergarten?).  so the new patch overwrote 4 innocent bytes.  i'm not sure how the Lamp didn't crash it as well; Fire Rod must get the function called more times, where one of them tries to branch to the end.

back to the drawing board on fitting this inline.  the code itself seems to be fine, when it's not trampling something else.

73
that also means you'll be blamed when it malfunctions.  :tongue:

thanks.  also, what partially-lit rooms can you name off the top of your head?  i wanna visit as many as possible.

74
when assembling, this replaces light-torch-new1.asm and torch-go-out-new1.asm:
http://assassin17.brinkster.net/forum-posts/zelda-torches/torch-light-and-go-out-new-complex1a2.asm

it tests Var $0458 to exclude the Uncle/Lamp room (and probably the Ganon fight, Aginah room, and old man mountain cave) from the spotlight.  also, it adds a check for the Lamp to the torch lighting and extinguishing routines, to close a loophole hacks could have if you get the Fire Rod before the Lamp.  if $0458 isn't == 1 (and you have the Lantern), this falls back to the game's original lit torch cutoff of 0/1 as opposed to just disabling the spotlight.  i do this to defer to the fact that the original game has no $0458 checks in these two routines, and still works fine.

i should probably add a check to skip the spotlight if $0414 is 2, even though i don't yet know of any places where that'll be the case with $0458 equaling 1.  what's holding me back is not understanding how $0414 works, as well as not being able to fit the additions inline. :/

finally, my interrupt palette code should probably check for Var $1D == 1 instead of just > 0, which'll be an easy change.

75
Game Modification Station / Re: New patch: Menu Malarky Bug fix
« on: February 11, 2017, 09:04:20 PM »
like stepping off a switch and quick-switching?