Object names should have a description

[AlexField442]

One suggestion to improve ease of access could be to change how objects are named. Right now, they are just listed as ObjXX with their raw ID value, unlike the other two disassemblies, which instead name them based on what they actually are. We could name objects with both, for example:

• Obj01 > Obj01_Sonic
• Obj2E > Obj2E_MonitorContents
• Obj5F > Obj5E_EndingController

This also applies to routines within objects, however given that we tend to avoid multiple _ in a function name (Obj01_Sonic_Normal), we could omit the ObjXX_ part for them altogether.

[Clownacy]

I'm in favour of this, though I've never really seen the point in the number being there at all: the ID is an implementation detail which is supposed to be hidden by ObjID constants and the like. Even SonLVL primarily presents objects by name rather than by ID. The Sonic & Knuckles disassembly goes this route, and just has labels like Obj_Sonic.

If it's important for people to be able to search for objects by ID, there could always just be a comment before the label that provides it; heck, since this disassembly preserves old labels, even that would suffice.

[RealMalachi]

I'd visually prefer a format like ObjSonic, but Obj_Sonic does have the advantage of Obj_ being a good keyword for locating object code.

[Selbi182]

As long as the old Obj01 format is preserved as a comment above, I'm in favor of this. This is actually something I wish the S1 community disasm did as well.

[Brainulator9]

The Sonic & Knuckles disassembly goes this route, and just has labels like Obj_Sonic.

I'm reminded of this comment from @tiddlets in #4:

(While we're on bugbears, for that matter, the mystery meat "Objnn" style object labelling always rubs me up the wrong way, seeming barely a step above "loc_n", but perhaps that comes from spending too much time with S3&K where the actual object ID is barely relevant.)

[AlexField442]

A demonstration of what this will look like, using Sonic and Tails. Also, some routines were already named Sonic_/Tails_, so this also helps give some consistency to the naming schemes.

Also, we might need to apply this to the mappings as well, as they use the ObjXX_MapUnc_XXXXX format. Should the files also be renamed at this rate?

[Clownacy]

A demonstration of what this will look like, using Sonic and Tails. Also, some routines were already named Sonic_/Tails_, so this also helps give some consistency to the naming schemes.

Looking good!

Also, we might need to apply this to the mappings as well, as they use the ObjXX_MapUnc_XXXXX format. Should the files also be renamed at this rate?

That would be fantastic; I hate trying to remember what object each file belongs to!

[AlexField442]

So, this is ObjBB. It behaves like a badnik, and clearly isn't using the right art. Implemented around the 14 September 1992 build, where it behaves the exact same, complete with the broken art. Going to name this "Obj_WFZUnknown" unless something is found out about it.