Some people don't understand how to submit descriptive RAM addresses, so I feel like this thread absolutely needs to be made.
I'm getting sick of the idiotic descriptions some people give their RAM submissions, and I'm surely not the only RAM map moderator who thinks that.
I discussed this with (part of) the staff, and this is the set of rules we put together:

RULE #1:
Try to make the description as clear as possible, give an indication of what the RAM address does and is being used for.



This is NOT ACCEPTABLE! (This is what bugs me most.)

RULE #2:
<common_sense>Try to avoid erroneous descriptions.</common_sense>

RULE #3:
ALWAYS SUBMIT THE CORRECT ADDRESS! USE $7Exxxx / $7Fxxxx MAPPING!



This is wrong. Just, wrong.
It is an understandable mistake, but an address like this is NOT acceptable.

RULE #4:
ALWAYS TRY TO DENOTE A NUMBER OF BYTES A RAM ADDRESS TAKES UP!



No-one likes this. Do your research as accurate as possible.

MODS HAVE THE RIGHT TO NUKE ALL ADDRESSES WHO FAIL TO OBEY TO ANY OF THESE RULES!

Thank you in advance.

--------------------
--------> Don't follow "Find Roy's Dignity", my hack. Because it's pretty outdated. <--------

I'd prefer "unknown sprite table" to it not being listed at all, imo. Rest of the stuff seems cool and reasonable.

We want to host some quality RAM submissions, not some random unknown junk which nobody knows what it does.

e:

[01:54:55] <@Roy> Seriously
[01:54:59] <@Roy> I could submit this
[01:55:09] <@Roy> 7E:1234
[01:55:10] <@Roy> 2 Bytes
[01:55:13] <@Roy> Misc.
[01:55:25] <~Ersanio> "Unknown? SMW related"
[01:55:27] <@Roy> "I don't know what it does, but it does something."

--------------------
My blog. I could post stuff now and then

My Assembly for the SNES tutorial (it's actually finished now!)

And? If it's unlisted, it's completely unknown. If it's listed as "unknown sprite table" I at least know messing with it will affect sprites.


SMW related =/= sprite related (and similar stuff)


Of course, an actual description of how it affects sprites (or whatever) will be preferable, but enforcing this on previously submitted RAM addresses won't make people go back and fix them.

That's what all.log is for. In all.log you can clearly notice that $15B8,x and $1510,x are sprite tables.
Why don't we submit them? Because research isn't done for them.
Yes, it's a sprite table. But that's all you know, unless you actually GO FOR IT AND RESEARCH IT.
And to make SMWC's RAM map actually a valuable place to look in, 'Unknown sprite table' just doesn't do it. As Ersan said, it's quality what we go for.
Such a description is barely better than no submission at all, it only points you a bit into the direction, but the same could be done with all.log.
And now you might be thinking, yeah, but what about the new ASM learners then? They don't know how to control all.log.
Well, let me tell you this, with a description as vague as that, you're not helping them either.

And by the way, I'm starting on fixing each one of the current RAM addresses with such a description tomorrow.

--------------------
--------> Don't follow "Find Roy's Dignity", my hack. Because it's pretty outdated. <--------

This is pretty much all I was sayin'. Barely better, but still better.
Excuse me if I misunderstood; I thought you were going to go purge all the vague descriptions.

Excellent! I look forward to some of those being cleared up.

Thanks. I'm one of those wet-behind-the-ears newbies, and I am totally confused by the "unknown sprite table" stuff. The more specific for me, the better. Though I do agree that the vague description is better than none, but as far as hacking use, I can't find anything until I get the specifics. Or I could go, you know, LEARN the darn thing.

Okay, I will follow the new rules!

--------------------
________________________________________________
Check out my hack, Super Wario World in the
hack disscussion area.