you're still a spoon

you

you're a spoon

you're still a spoon. stop being a spoon.

Hiya folks, it's been a while since I really published any of my recent works, so I'm going to go ahead and throw what I've been working on recently to you.

You read it right. I have written a 2D tool that can display (but not edit, just yet!) Super Mario Party boards! It's only been a few weeks since SMP released, so talk about a quick hack.





I plan on a lot of features, such as text editing and more, but for now you can open up the maps in the Archive folder and open up the BEA archive (which the editor supports!) and it will automatically open the data you need.

Github:
http://github.com/shibbo/SMPe

Official development Discord:
https://discord.gg/eWNypQU

Enjoy ;)

I'm actually tempted to accept requests for banning those who persist on OMG RELEASE or OMG WHEN WILL IT BE DONE

Located at address 0x02088BDC in the game's memory (only when you're playing the story. Minigames overwrite this when playing minigames) lies the save file. It is 0x24C bytes long and contains a variety of information. The structure is defined below.

Value	Purpose
0x00-0x04	"7000" in ASCII. (7001 in NewerDS)
0x04-0x08	Most likely a flag that is set to 1 when the save has been initialized.
0x08-0x0C	Field responsible for calculating the user's profile stars.
0x0C-0x10	Number of lives.
0x10-0x14	Number of coins.
0x14-0x18	Unknown.
0x18-0x1C	Number of star coins.
0x1C-0x20	Number of spent star coins.
0x20-0x24	Current world. Setting byte 2 of this field will play the warp animation.
0x24-0x28	Unknown.
0x28-0x2C	Current world map node.
0x2C-0x30	Unknown.
0x30-0x34	Current powerup the player has.
0x34-0x38	Score.
0x38-0x3C	Current background the bottom screen uses.
0x3C-0x40	Current world possible duplicate. This value changes when 0x20 changes, and cannot be edited because 0x20 automatically sets it back to the previous value.
0x40-0x44	Unknown.
0x44-0x48	Unknown.
0x48-0x4C	Unknown.
0x4C-0x50	Unknown.
0x50-0x54	Unknown.
0x54-0x58	Unknown.
0x58-0x5C	Unknown.
0x5C-0x60	Current item in inventory.
0x60-0x70	WorldUnlocks[8]
0x70-0x137	StarCoins[200]
0x137-0x24C	Levels[240]

Level Flags

Flag	Purpose
0x00	Not unlocked.
0xA0	Used only by signboards. This value will be there while the animation for the sign disappearing is playing. Once it finishes, it will change to 0xC0.
0xC0	Complete.

Star Coin Flags

Below is a table of how the StarCoins[] get marked.

Flag	Purpose
0xD0	No star coins.
0xD1	Star Coin 1 Only
0xD2	Star Coin 2 Only
0xD3	Star Coin 1 and 2
0xD4	Star Coin 3 Only
0xD5	Star Coin 1 and 3
0xD6	Star Coin 2 and 3
0xD7	All 3 star coins.

World Map Flags

Flag	Purpose
0x00	Not unlocked.
0x3E	World was not completed, user "finished" world by shooting out of a cannon.
0x43	World was accessed by cannon.
0xFF	World is completed. (The world itself is unlocked if the value is >= 0x40)

the PMs are better than the thread

no

stop whining

I might not be a mod on here anymore because it was pretty much a request to be demoted, but I need to point something out.

Please, please, please, don't fucking wipe a sprite's data on the database and say "See X sprite", because it's stupid and useless. That means the user has to see the original sprite, therefore adding it to the level uselessly just to see the data. That's stupid and it shouldn't be that way. If you think it's good for space, you're wrong. A few fields will not kill anybody.

If it happens and somebody spots it, tell the mods.


StapleButter edit: from now on, anybody doing this gets a ban. Thank you.

congrats, you actually ended up in the Dimensoial Trash Can Forum.

no

when in doubt, delete the file and see if the game crashes

MAN FUCK THIS SHIT

YOU SHOULD HAVE RESPECT FOR THAT SKYPE CHAT, YOU OWN IT
FOLLOW YOUR MOTHERFUCKING DREAMS

who the fuck are you, even

So this is a (lame?) attempt and showing the newbies how the actors in NSMBDS really work. Now this tutorial assumes that you've already learned some C, C++, and ARM assembly. If you haven't learned any of these (but really ARM in general if you just want to get a tiny grasp), you should exit this thread and try to learn these languages. Oh, and you also have to have a version of IDA. I use 6.8 (used to use 6.1 but now the idb fails for some reason.)

So to actually figure out how an actor works, you first have to find the pointer to it's profile in the profile pointer list. This is located at address 0x0203997C in the game's code (I think it's US region, correct me if I'm wrong, and to get to this address you hit "g" in the IDA view, and then paste that address). The profile pointer list literally points each entry to the actor's constructor, which is what we'll get into later. Now during the 10 minutes I spent looking at the IDB, I'm not sure how one would calculate how to find an actor. But for the sake of example, we will use the Jumping Cheep Cheep's pointer. This pointer is at 0x0203997C.



if you're using a outdated IDB, it will appear as this. Highlight off_2228F10 in IDA and hit "n". In the field, simply type in "JumpingCheepCheep__Profile" and hit enter. Then it should show up as this:



and if it looks like that, highlight it and hit enter OR just double click on the name. After you click on it, you should get something like this, except that JumpingCheepCheep_ctor is labeled something else. Highlight it and name it what I have below.

Now to actually break this down. The first line, DCD, means to pretty much load into memory. So in this example, the constructor is loaded into memory and accessed. The second line just says that to get to this position, you had to come from the profile pointer table.



After renaming the routine, double click on it. You should have something like this:


yeah, that's a lot of information for you at once. But to be pretty blunt, this is what the code does:


So really, the constructor sets up the actor to be able to function, and it also "preserves" memory for it to work. It also has a pointer to the vtable, which contains all of the methods that the class uses. This will also lead us into inheritance and methods. If you see what I see, double click on "JumpingCheepCheep__vtable". You should get something like this:



yep, even more crap to worry about. However, we can walk through it. This table is a table full of methods that the actor uses. For instance, "Actor__SetXPosition" sets the actor's position. This function is a part of the Actor class, so it inherits that method to use in the Jumping Cheep Cheep class. It saves memory! However, there is something called "Method Overriding", where instead of inheriting a method from a previous class (or even many many classes if the inherited class doesn't use their own method either), the current class overwrites it with something else. This can be seen when the entry starts with "JumpingCheepCheep__", which means that the method is overridden. For example, "JumpingCheepCheep__executeState0". So instead of using something like EnemyActor::executeState0(), it uses JumpingCheepCheep::executeState0().

Since we know how method overrides work, we can now look at important methods that most sprites use.

Method Name	Purpose
beforeCreate	This method is executed before the actor is created onto the current scene.
afterCreate	This method is executed after the actor has been created.
beforeDelete	This method is executed before the actor is deleted.
onDelete	This method is executed once the actor has been deleted.
afterDelete	This method is executed after the actor has been deleted.
beforeExecute	This method is executed before the actor is executed.
onExecute	This method is executed once the actor has been executed.
afterExecute	This method is executed after the actor has been executed.
beforeDraw	This method is executed before the actor is drawn onto the current scene.
onDraw	This method is executed once the actor has been drawn.
afterDraw	This method is executed after the actor has been drawn.

Something common would be to click on a function and then see this:



this pretty much means:



which pretty much does nothing. I'm not sure what returns 2 and 3 do, but I think one of them deletes the actor. If not, then whoops, I overlooked something. But that's how NSMBU does it.

That's all I can really provide at the moment. I'll go deeper later, but this is my attempt at partially explaining it.

Dude. For the last time, stop making a million threads despite you breaking the rules. I can't ban you, but I am having somebody else do it when they get online.

Good day.