BankLogs address submission

[JAM]

This is a topic where everyone can post additions to the ROMMap by DC and BankLogs by James. If you know something that we don't, post is here and it will be there. I'll start.

D7200..D72FF Power Beam GFX
D7300..D73FF Unused
D7400..D74FF Ice Beam GFX
D7500..D75FF Unused
D7600..D76FF Wave Beam GFX
D7700..D77FF Unused
D7800..D78FF Plasma Beam GFX
D7900..D79FF Unused
D7A00..D7AFF Spazer Beam GFX
D7B00..D7BFF Unused
D7C00..D7C1F ?????
D7C20..D7FFF Unused


$A0|F153-F192 DNA|????????????????????F153
I dub you mini-Oub (as I discovered him). Unused enemy. Acting like Oub, but rolls in place and having different colors (orange body with green eye). Uses single 8*8 tile.

P.S. Can I ask for sticky?

[begrimed]

Just a reminder not to forget that this page has a lot of ROM map-esque stuff outlined as a good starting point. The hex page could probably also point you in the direction of some similar clumps of data for the ASM-minded to pick apart better than I could.

While I'm at it, it's not much, but it's something. Some unused data that I've noted over time, and some possibly unused stuff, which is noted in the descriptions. I'm sure you ASM wizards will be able to determine if the possibly unused stuff is *actually* unused.

13BC65-13BCA7
13BFAB-13BFF2
13C0BD-13C12E
13C17A-13C1FA
Non-essential routines in Kraid's AI that can be completely NOP'd without affecting the fight in any way that I can tell, and I tested pretty extensively.

120DA4-120DEC
120C95-120CCA
Routines in Crocomire's AI that can be completely NOP'd without any changes. Hijackable for new code, I suppose.

=====Presumably unused color clumps, noted in I'm-A-Genius form=====

764A2-0E, 764C2-0E, 764E2-0E - Duplicate hexagon map colors. Unused?

66AE9-CF = Unused duplicates of intro colors.

669E9-FF = Top half is presumably unused, or actual data for something shown as 'colors.' Bottom half looks like gray/brownish intro scene palettes.

66BE9-FF = Moar colors for things; I see Samus' ship's palette in there too, and Zebes/stars. Not sure if unused.

66DE9-FF = Moar colors again. Few gradual fades, and two instances of Zebes/stars.

66FE9-FF = Lots of color fades. Nothing but color fades. Dunno what they're used for.

671E9-FF = Lots of gray fades and blackness. Not sure if colors for smoke puffs (Samus' ship taking off?), or data, or unused.

5AAB9-FF = Lots of blue here.

D9780-3F = No idea what these are for; something suit-related. Not sure if unused.

D9540-BF = No idea what these are for either. Something suit-related. Not sure if unused.

D9440-3F = See above.

66B69-0F = Unused(?) duplicate colors for Samus' intro palette.

66509-0F = Part of "Intro" colors, but aren't included in SMILE. Doesn't look like these are used for anything.

66AE9-CF = Unused duplicates of intro colors.

[snarfblam]

This kind of stuff can also go in the wiki.

[-DC-]

This kind of stuff could also go to my ROM Map... I had a topic somewhere already to submit stuff, but I took a long break from it after I had finished up the statue animation stuff, getting worn out while mapping the map screen stuff.

http://mmxlegends.110mb.com/DC/smmapb.html

Topic: http://forum.metroidconstruction.com/index.php/topic,630.0.html

Sorry about vanishing, but I lost interest for a long time, got way too tired to concentrate on doing much of anything clearly, and got busy on some other stuff... sorta.

[Black Falcon]

38564 - 38B63  Water animation, East Crateria ocean

38B64 - 38E63  Unused lava animation graphics

38E64 - 38EE3  WS Conveyer graphics

38EE4 - 39603  WS background screen gfx

39164 - 396E3  Falling quicksand from Maridia

396E4 - 392E3  Falling quicksand, ceiling part

39364 - 394E3  Phantoon statue, eye glow animation frames

394E3 - 395A3  Ridley statue, eye glow animation frames

395A4 - 39723  Draygon statue, eye glow animation frames

39724 - 397E3  Kraid statue, eye glow animation frames

397E4 - 39963  Miscellaneous parts of statues

39964 - 39C04  Red Brinstar, man-eating plant animation frames

39C04 - 39F03  Spike animation frames

3A564 - 3AA03  Layer 3 atmospheric graphics (lava, spores, rain and acid)

3AD64 - 3C964  Rest of statue graphics, including main parts, sparkles and ghost(?) thingies

Need respective palettes.
To edit them in TLP, just put these values into the goto box.
Also, when you're pressing CTRL + LEFT/RIGHT, TLP will decrease/increase the current adress with 1 byte, allowing you to view graphics that appeared uneditable before (like the above examples. Goto 38560 and press CTRL + RIGHT 4 times and you'll see what I mean).
Now someone put this up to the wiki! *Black_Falcon is too lazy to create account* btw cookie for you finding this tiny text! :D

Edit: They are already listed in DC's ROM Map :>_>:

[-DC-]

Oh, BF, I completely disassembled that entire bank and labeled all those, but good tip to use for TLP. I have a guide for that bank at my rom map page, linked beside bank 87. It's also included in my tile animation stuff uploaded somewhere around here.

[Qactis]

Oh, BF, I completely disassembled that entire bank and labeled all those, but good tip to use for yy-chr.

fix'd

[Scyzer]

This thread seems completely useless to me. There are already VERY good bank logs by James, which already have most of everything that people will ever post here.
And unless someone is going to be keeping track of everything in here and writing it down, it's going to be a huge unordered mess.

And one more thing, how do you determine whether to make it noob friendly or for more experienced hackers?
How do you determine whether to write "Shinespark main routine" for one whole section of code, or 50 smaller addresses for stuff like "shinespark starting max speed, shinespark max speed, shinespark accelaration" etc. If you are going to have single addresses for values like that, you might as well disassemble the entire ROM.

[Quietus]

I would imagine that with the site aimed at the whole Metroid editing community, then it should always be targeted toward newcomers, and with as clear a description as (is practical and) possible.

[JAM]

This thread seems completely useless to me. There are already VERY good bank logs by James, which already have most of everything that people will ever post here.

Actually, I made this topic to make able people to post updates to the BankLogs, like the nearby topic for hex tweaks. Just forgot to mention it in the first post.

[DSO]

DC687: Location of single color loaded for grapple beam. (If anyone changed the ice beam color which grapple uses they'd notice the base would change but the trail of the grapple shot would stay blue, this is where you change that trail color)

[Qactis]

This thread seems completely useless to me. There are already VERY good bank logs by James, which already have most of everything that people will ever post here.

Actually, I made this topic to make able people to post updates to the BankLogs, like the nearby topic for hex tweaks. Just forgot to mention it in the first post.

So why don't we load up James' and DC's logs here on the first post in spoilers, and if you find something not there, then post it and we can keep updating it. Why put down people for trying to expand our Super Metroid data documentation Sad? :/

[-DC-]

This thread seems completely useless to me. There are already VERY good bank logs by James, which already have most of everything that people will ever post here.
And unless someone is going to be keeping track of everything in here and writing it down, it's going to be a huge unordered mess.

And one more thing, how do you determine whether to make it noob friendly or for more experienced hackers?
How do you determine whether to write "Shinespark main routine" for one whole section of code, or 50 smaller addresses for stuff like "shinespark starting max speed, shinespark max speed, shinespark accelaration" etc. If you are going to have single addresses for values like that, you might as well disassemble the entire ROM.

First, the rom's already being entirely disassembled, albeit, slowly... I want to write a program that can disassemble any rom, and already have ideas for how that would work that others seemed to not have before, but I need to learn programming in something else to make it.

My rom map lists all addresses of all parts of stuff and will have bank disassemblies / guides linked to in the title of the bank, and those will eventually list what routines use what data and other routines, as well as what routines jump to them.


To Qactis, those logs would be soooooooo long...

Anyway, I originally started a topic when I first built my first version of the rom map and gave a topic for it, stating the format to submit things in so that I could collect the data for help building the rom map.

http://forum.metroidconstruction.com/index.php/topic,630.0.html

Everyone thought it was cool and liked how my rom map turned out, but it never got another response in all the time I was away taking a break from SM hacking.

[JAM]

So why don't we load up James' and DC's logs here on the first post in spoilers, and if you find something not there, then post it and we can keep updating it.

That's exactly what I wanted. People don't understood me. Next time I'll re-read what I want to post several times.

First, the rom's already being entirely disassembled, albeit, slowly...

I didn't know about that, really.

[Qactis]

To Qactis, those logs would be soooooooo long...

One spoiler per bank, wouldn't be too bad... think Moonedit SMILE FAQ

[-DC-]

JAM, your quaote got kinda f'd, Sadfish didn't say that, I did.

Yeah, I was working on disassembling manually for a time, but after the disassembly of the animation bank, I took a break from doing that and was instead working on labeling as much as I could figure out from bank 82, since a vast portion of it pertained to the status, map, and file select screens that I had already taken a huge bite out of figuring out during my map patch stuff... but then things came up and I got worn out of doing that, and now I have my job to worry about while also not getting enough sleep to concentrate on things.

[M1CR0H4CK3R]

If anyone needs to access DChronos' ROM Map, it is now at http://dchronos.110mb.com/DC/smmapb.html, not http://mmxlegends.110mb.com/DC/smmapb.html. I'm posting this on his behalf, without permission.  :heheh:

[-DC-]

It needs a new site, the new owners of 100mb fucked everyone over and purposely let the grandfathered paid accounts' servers sit in limbo till everyone left.

Kinda surprised this topic hasn't had more data added.

[JAM]

It needs a new site, the new owners of 100mb fucked everyone over and purposely let the grandfathered paid accounts' servers sit in limbo till everyone left.

We have wiki. But nobody uses it.

Kinda surprised this topic hasn't had more data added.

Nobody cares. I'm even thinking of quit making patches. Nobody uses them. Well, almost.

[Quietus]

It shouldn't be assumed that people aren't using them.  It's possible that any number of them are being used.  There isn't really anywhere for people to say 'thanks, I'm using your patch', and it's kind of how a community like this works.  Some things will be more popular than others, but they're all helpful.  I know that I've dabbled with any number of patches by various people.  Even if only one person end up using a patch, it was worth somebody creating it.  Keep 'em coming, JAM. :^_^:

[begrimed]

We're a pretty small community, and making hacks is driven mostly by creativity. It makes sense that peoples' ideas wouldn't line up with many patches that have already been made, but dear got JAM please keep making them. Your patches fucking rule.

[MetroidMst]

Nobody cares. I'm even thinking of quit making patches. Nobody uses them. Well, almost.

I think you're selling yourself short there. How I normally go about making a hack nowadays means I won't look at patches or anything until I come across something I absolutely need. However, when starting a new hack, I browse through the patches/asm/gfx thoroughly to see if I can use any of it for interesting stuff in this new hack, and due to certain ideas I had, I had reason to do so within the past few months. I believe I grabbed about 13 different things just listed from you.

Point being, people with current WIP hacks probably don't have that great a need to browse through and find stuff for their hack, they already have a good idea (Or should) of what their hack will be and what they want. But once they get to another hack, it is very likely they will at least look through and see if something catches their eye. If they find one thing, the likelihood is that they will get their imagination working and pick up some more stuff too. Don't undervalue your patches because it appears no one is using them.

[Vismund Cygnus]

Basically what Mst said. I know that for basically every hack I've released I've used at least one patch, including multiple of yours (the item events patch is one I've found particularly awesome).
Basically, don't be disheartened just because it seems nobody is using them. Hell, if people used credits on their hacks more often, I imagine your name would come up in well over half of them.
Keep doing your thing mang.

[Quote58]

As great as your patches are, I do think you need to include the .asm more often. It would be helpful to see how some of your patches were made.
And obviously to echo what others have said, just because you don't see your patches in many hacks out there doesn't mean people aren't using them currently.

And finally to address the question brought up by DC, I think for a lot of people the ROM map so to speak is simply the collection of bank logs that were commented by PJboy. In fact there's even http://www.metroidconstruction.com/docs/pjboydissassemblylist.txt which is all of them put into one doc.

With what we collectively currently know, it'd probably be very easy to put together a general ROM map, and it could be useful for quickly finding certain routines.

[P.JBoy]

My logs are constantly getting updated, see here