Also, if some people are in favor of decoupling from the board altogether, I won't force you to keep using it. I will however finish the documentation process up to what my existing knowledge includes.

NSMB namings mess

Object IDs

Object IDs, also referred to as Class IDs or Actor IDs, are the identifiers of spawnable entities, aka classes that inherit from Object and provide their ObjectProfiles (or ActorProfiles) as entries in the process table.
When you spawn an Actor, or switch to a Scene, you are spawning an Object identified by its ID.

Stage Object IDs

Stage Object IDs, also referred to as Sprite IDs (yes, the ones shown in NSMBe), are the identifiers of the Stage Object, wrongly known as sprites.
Stage Objects are not actors, they are abstract entities which are bound to Objects completely independently.
When the game loads a stage, it goes through the placed Stage Objects and, to spawn the corresponding Object (aka, the Actor), it goes through another table.
Adding up, ObjectInfos should be actually named StageObjectInfos as they are structures only used for when the game spawns the Actor as a placed Stage Object in the level and they have no effect on standard spawning.

But Why?

The distinction exists, and nothing can be done about it; the modern names used throughout the Reference are what they are and, indeed, they can be at times confusing (especially due to Object vs Stage Object).
Some day this will be definitely picked up again and changed once and for all.

Platform Colliders

These colliders can create semisolid surfaces (platforms) of various shapes.

- RotatingPlatform:
Line platforms which are handled by position, length and rotation angle.
This type is useful for when you want the platform to rotate around its center, or even for static platforms with a specific angle.

- SegmentPlatform:
Line platforms which are handled by two positions representing the two segment points.
This type is meant for when you want to change the platform's individual points.

- DeformingPlatform:
Line platforms which deform and act like springs based on the colliding player position.
These ones are specifically used for the W1-Castle's "rope platforms".

- RoundPlatform(s):
Circle shaped platforms, handled by a position and a radius, which are semisolid either on the lower semicircle, creating a concave shape ("internal"), or on the upper semicircle, creating a convex shape ("external").
These platforms have really weird and unfinished physics, so their usage is not recommended; you reading this, sorry but rolling hills from NSMB Wii aint that simple to implement.
The internal round platform is unused, however, the external one is only used for collision with the giant wiggler in W7.

For those who are using a custom actor and want to adjust the sprite data settings inside the NSMB editor (5.4.1), that might be a little helpful for you.

I was confused by "field ID", wondering what it does and it didn't take long before I fully understood it. I made a list, what each value from 1-48 does, but I have to admit that I didn't check every digit. However, it seems to follow a certain pattern, so it's probably correct
file

ffuck it this works ig

stupid graphics only using one colour from some random ass palette

What's wrong with the existing database format for you to say it's completely wrong, specifically?

Originally dirbaio thought that settings were 48 bits, and that decision ended up in the editor too:

In reality, this is how stage object data is actually stored in the format:

The actor settings are only the last 8 hex digits in "Raw Sprite Data", the first two are not settings but the eventIDs (which are used, obviously, to store the events that are being triggered by the actor/events that the actor is waiting)

- Community contributions to the documentation are too open; people kept adding unexisting settings in the forum's database with no code knowledge or by trial and error and this is not what we want

(…)

If you're going to rename sprites to "stage objects", then how would you call what NSMBe calls objects?

There is no new database, apart from a spreadsheet to track down reverse engineering progress.

Regarding the naming conventions and their issues, read the last part of what Keeper quoted.

fwiw i use "tile objects" when i feel distinction helps

Also, be wary of the "my terms are the only correct ones and the rest is bad" because people will call stuff what they want to call them.

Probably his way of saying "won't add", but he's too lazy to explain why. Surprising he'd just ghost you like that, that's the sort of thing I'd expect him to do to those he sees as below himself and the other "old staff".

Also, be wary of the "my terms are the only correct ones and the rest is bad" because people will call stuff what they want to call them.