thanks both. nitsuja: i am able to replicate it consistently using those instructions, but what do you mean by "in any one direction"? like i tried letting a purple Foot get directly above me on the screen, swatting him, pushing up for 8-12 frames, then holding up and pressing attack, but i'll only do the bash move. likewise for moving downwards after hitting a Foot below me.
obviously, i'll be moving left or right if i want to play the game well, but i'm curious how flexible the throw is.
have you determined what makes you throw a Foot at the screen versus bashing it into the ground? the instruction manual and some FAQs talk about holding down the control pad or pressing it in different directions, but i've yet to find something that works consistently, even after exploring in slow motion. and curiously, i seem a lot more likely to get the bash in slow-mo (probably, i'm doing something small differently i'm not aware of).
yup, i'm sure. i just tested again, and got his 4th, sai-spinning hit after his 3rd, 5-point-damaging one.
besides, neither of his 3rd hits have the same windup as his 1st hit anyway.
i used the Geiger Snes9x emulator to put a watch on an address involved in choosing whether to swap Raph's 3rd attack, and it's constantly incrementing, so it's probably a timer of some sort. in particular, the bottom bit of it ($00:003A) is used in the decision. given how you crazy speedrunners weep over lost frames, you may've been reluctant to wait. ;)
actually, the 3rd hit for Raphael seems to (randomly?) choose between one that does 5 damage and one that does 3 damage. the two attacks have different animations and everything. 5 is what's in the normal position for this attack in the ROM, if that means anything.
i haven't found any such exceptions for the other turtles, although I can never get Mike to use his 3rd and 4th combo hits in Versus Mode; after the 2nd, he just starts over with the 1st one.
anyway, thanks for convincing me i wasn't hallucinating.. i *knew* i saw a 3 from Raph, but changed my notes to 5 and shook my head after getting that number a couple times in a row.
Thanks for the speedy reply!
to be sure: the player has the option to stop ducking, or the game will make you stop ducking? if it's the former, then how come i've been able to do the trick without letting go of Down on the control pad? (though it's possible my finger slipped off in the fury of it all.)
cool.. i was wondering what that crazy quadruple pump was for. :)
also, is the game ever ejecting him from the ceiling in this scenario, or does it merely do the ceiling collision test when ejecting him from the wall? i just want to be sure as to how many ejections are involved.
ah, so "steering" in this comment from the webpage:
means the actual direction of Mario's _movement_, not the direction he's facing?
is "Going through bricks" the only bug needed for this when Mario is large? i'm assuming "Walljump" is not needed.. and why don't you need to steer away from the brick wall in order to be pulled in?
yes, i've read: http://tasvideos.org/SuperMarioBrosTricks.html
but am not entirely sure what bug is responsible for what. and how exactly does the ceiling set-up the interaction with the right wall?
i see the animation here shows Mario facing forward for the jump, though everywhere else I've read about the bug has him facing backward, and i've yet to pull off the bug with him forwards. does his direction matter at all?
also, does anybody know which, if any, of the bugs on that page (particularly the wall-related ones) made it into Super Mario All-Stars? (i can get through said wall in 1-2, but haven't pulled off anything else.)
thanks
Given that Snes9x v1.43 displays the whole 7E0000-7FFFFF range in its default "Search for New Cheats" menu (unlike v1.39, which I'd been using until recently), I think it could double nicely as a memory viewer. However, scrolling to the address I want is a royal pain in the arse (i.e. when I don't know the memory's value, and just want to look at an address range).
Now I know Cheat Search does not purport to be a debugger, but how hard would it be to a add a little text box that lets you type in an address (e.g. "7E11A2"), and upon hitting Enter or some button, scrolls the list to the desired value?
Currently, I'm stuck using Snes9x-LT for DOS.. which is great for debugging, but is less than desirable in many areas (such as default key assignments I can't change.. :/ anybody know how to address that?).
"Memory Goto" would rock my socks (many others' footwear would be similarly jostled, no doubt), and I suspect it's simpler than lots of the feature requests you see. :)
note that those links are now dead. this documentation is now with the rest of the guides on my sites:
http://www14.brinkster.com/assassin17/http://assassin17.home.comcast.net/
also, it's been updated to account for the 1-60 frame counter, which means even more thwarted attack formations are listed.
How is that more screwed up? The older version wrongly suggested that Grass had a different encounter rate than Desert/Forest, undoubtedly based on tests in a "low encounter" grass area.
As explained in that link I gave, there are just TWO categories:
- overworld (the terrain type -- grass, dry land, desert, forest -- does not matter)
- dungeons (that includes caves, towns, etc)
Why Terii didn't give the four different encounter rates within each of those categories, I'm not sure. (Instead, he just gives the "normal encounter" rate, which is by far the most common, as you can see with FF3usME).
The bottom line is that while both versions are incomplete, the new one is more accurate and far less misleading.
Also, I just remembered that the Algorithms FAQ used to give different increment values for each terrain, but these have inexplicably disappeared (despite being apparently correct...). Anyways... here they are:
Grass 96
Desert/Forest 192
Elsewhere 112
The first screen of the first cave seems to be an exception. It adds 64 instead of 112.
i had a role in their disappearance, and i'll gladly defend the new ones. :P
http://assassin17.home.comcast.net/c0bank.txt
see C0/C29F through C0/C2DE. yes, the data layout means you can punish somebody who's stupid enough to combine Moogle Charm with Charm Bangle. >:)
note all my talk of "FF3usME values" doesn't mean much, because:
- FF3usME doesn't retain changes to this field anyway.
- Lord J is bound to fix the names quite soon.
if somehow the code i've studied is highly deceptive and you're sure the old values are right, do speak up. free free to ask any followup questions regardless.
if you said something different since Page 3 that i missed while skimming this thread, apologies.