I have been debugging and working on completing my hack. In doing so I have found a lot of sprite DB fixes. There are a lot of things left to do. If anyone else can contribute some time, I think we are getting pretty close to having it reliable.

The 168 sprite is in bad shape. If you compare it with the original game it is off. Plus it only activates reliably with "touching the ground in".

Anyway, Dirbaio and Piranhaplant are working on editor revisions to get the 5.2 into a stable release. All of us here can contribute to this stable release by getting the database as solid as possible. So I guess I am asking if each of you can pick a problem sprite and clean it up.

168 is a good one
the spiked balls do not work well
any of the unknown checkboxes could be hiding something cool that can improve all our hacks.
Better English is good too. We don't have many words we can use in the sprite data, so quick and accurate are key. Of course spelling.

I've helped clean up English.ini in NSMBe so it's easier to understand. Some of the dialogue boxes were very long and confusing.

Sprite 83, has LOTS of things to work on. Practically EVERYTHING is unknown, because certain combinations create unexpected results.

The Lava is another one to be worked on.

And I think some FG effects need to be worked on also.

Aside from fixing obvious problems by looking at the data, we need to test them thoroughly to make sure they function properly (which, will take probably the longest time to accomplish).

I wondered the same thing, why are there different ones?

It would be nice to be able to change the speed of the rising lava as well. You know I haven't looked to see if the water and lava data is shared now in the database since they behave relatively the same.

See a lots of creative DS Hacking here
If you want to support me, you might check out my Patreon Page : )

Does someone here know how to log the Sprites being created/destroyed with the spritedata during the execution of the game? This will help a lot. I think Dirbaio knows how to.

I do not completely understand.

You could create a ASM hack that scans block 6 for changes and show something when it changes.I am not sure that that is what you mean.

For example you COULD make it so that every time a sprite is being created the screen goes black for 60 frames with a message with the number of the sprite/ sprite id but I do not know that that is what you want.

Also where would you want the log to be saved?

Another goofy sprite is the 45 coin in bubble. It has a bunch of different data entries even in level 1-1-1, but does exactly the same thing. Well, one did nothing, but there rest did the same thing as a invisible coin block.