So, as you may or may not know, NSMB2 has couple unused prototype levels, however many of these levels have the shared problem of incorrect IDs for various aspects of the level and because of this they are unplayable.

Here is an example of how these levels look in coinkiller:


However, I have spent some time analysing these stages and have been able to (almost) fully restore all of these stages. I have produced tables for each of these levels, listing both the incorrect/old ID, and the ID of each of the objects in the retail game.

Here is the same level after being restored:


The tables I have created are available here, and a copy of the restored proto levels is available here

If anyone has any ideas about the last few IDs that have yet to be restored, your help would be appreciated.

RouteEdit

A World Map Info Editor For NSMB2 World Maps

RouteEdit is a tool that allow you to configure how the paths on the world map works.

It allows for you to:

• Modify what paths and nodes are unlocked upon the completion of a stage.
• Select the material used for path segments.
• Change the action used when following a path.
• Configure the path koopalings take when running across the map.

RouteEdit can be used to edit the standard world maps, however is especially useful when paired with a custom world map model as this allows for the user to create entirely custom paths.

Disclaimer - this guide will not cover modeling or importing your map.

Before you start you will need two things, RouteEdit, and modeling software capable of manipulating bones, in my case I am using Blender, but feel free to use anything.

There are various node types that are used within the NSMB2 world maps, their names and purposes can be seen below. (Any x's or y's in the node names are placeholders and are intended to be replaced by a number.)

Node Name	Description
WxMy	The start node/rainbow level node y in world x
Wx0y	Numbered level node y in world x, the range for this node type is levels 1 through 7
WxSy	Lettered level node y in world x, the range for this node type is levels 0 though 2 (A though C)
WxGy	A Ghost House level in world x
WxTy	A Tower level in world x
WxCy	A Castle level in world x
WxPy	A Cannon level in world x
WxKy	A Toad House in world x

Node Name	Description
F00y	Path junction node y
Fg0y	Star coin gate node y
WxDy	Warp pipe node y in world x
K00y	Path corner node y

Node Name	Description
cobDokan0	Adds a Pipe model at that location
cobCannon0	Adds a Cannon model at that location
cobTower0	Adds a Tower model at that location
cobGhost0	Adds a Ghost House model at that location
cobCastle0	Adds a Castle model at that location
cobPeachCastle0	Adds a Peach's Castle model at that location
cobKinoko1up0	Adds a green Toad House model at that location
cobKinokoRed0	Adds a red Toad House model at that location
cobKinokoSpecial0	Adds a star Toad House model at that location

Setting Up A Basic Map Structure

First you should plan your map layout, determine where you want your level nodes to be, then after deciding on a layout, you should go ahead and model it.

Things to keep in mind when modeling:

• Paths must use 90 degree angles, anything else will cause problems.
• Your model should ideally be below 8000 tris.

For demonstration purposes, I have created a simple map containing only some paths.

Adding Level Nodes To Your Map

Once you are done modeling your map you will want to create the bone structure. Every map needs a bone structure with a root bone named "CS_Wx", replacing the x with the world number, and two child bones named "course" and "route".
I would recommend placing these bones in the center of your map, however these bones don't have to be placed anywhere specific.



Now, to add your level nodes you will want to create bones that are child bones of the "course" bone. These bones must be one of the Course Nodes listed above. The only required course node is a "WxMy" node, this will create your maps start node.
When creating your bones you may notice an issue, the bones are attached directly to the "course" bone, to fix this in Blender you will want to open the bone properties panel and uncheck "Connected", this will allow for your bone to be moved freely.



Once you have created your bone, position it where you want the node to be. Repeat this procedure for any other level nodes you wish to add to your map.



When you are done placing all of your level nodes you should have something that looks similar to this.

Adding Map Objects

If you have added nodes for a level such as a Castle or a Tower you will want to add the associated map object for that level type.
To add a map object you will first want to select the bone for the associated level, and add a child bone to that node, this child bone must use one of the Map Object Node names listed above.

Here I have added a castle object to my castle level.



After adding this object you will want to position it appropriately.



You will want to repeat this process for any of your level nodes that have an associated map object.

Adding Routes To Your Map

An important aspect of a map are the routes that connect the level nodes, so to create these you will want to add child bones under the "route" bone.

All routes must have an "R" prefix in their name.

Creating Normal Routes

Routes must be named using the following structure:
"RNODE1NODE2" - an "R" prefix, then the name of the two nodes that the route connects.

For example the name of the route going between the nodes for W1-1 and W1-2 would be named RW101W102.

Once you have create a route node you will want to position it between the two level nodes it connects.

Creating Junctions

In some cases you may want to add a junction to your map, allowing the player to go down multiple paths, in this case you will want to add a route that leads to a junction.
To do this, you will want to create a route that has NODE2 replaced with a "F00y" node. Then, to this newly added bone you should add a child with the same name as your "F00y" node.



You will then want to position these nodes with the route between the two nodes, and the "F00y" node in the center of your junction.

Creating Corners

To Create a corner in a route you should create a route the same way you would a normal route, following the "RNODE1NODE2" naming structure, but then after creating this you will want to add a child bone, this child bone should be a "K00y" node.



Once these two bones are created you will want to position them so that the route node is between the first node and the "K00y" node, and the "K00y" node is positioned on the corner.

Configuring Route Properties

If you have made any changes to the bones in your map you need to edit the route info, the original route info is likely not going to work with the changes you have made and therefore we need to configure it appropriately.
To modify the route info we use RouteEdit, you can download it here.

Inside of the "CourseInfo" folder in your romfs you will find a file called "RouteInfo.sarc", you will want to open this file with RouteEdit.

Configuring Nodes

To configure nodes you will want to select the "Node Unlocks" tab then select the world you want to edit from the dropdown.

I recommend you use the "Remove Row" button to remove all of the existing info for the world you have selected.
Next you will want to add a new row for each course node in your model file.

In the ID column you will want to increment the number for each row, starting from 0.
In the Node Name column you should add the name of each of your level nodes.

You will also want to add additional rows if you used any junctions or star coin gates, adding the appropriate names in the Node Name column.



Next you will want to fill out the node and path unlocks, these are the nodes and paths that will be revealed when beating a level.
You can also do the same for the secret node and path unlocks, these being the nodes and paths revealed upon getting the secret exit of a level.

If you wish to have multiple paths or nodes unlocked at once, surround these with quotation marks, and separate them with a comma.



If your map contains junction nodes you will want to make it so the player stops when passing over them, to do this add the "stop" flag to the node flags for each junction.



If you want the minimap to show certain paths before they are unlocked, you will want to add them to the Revealed Path Connections column.

Configuring Paths

To configure paths you will want to select the "Path Settings" tab then select the world you want to edit from the dropdown.

I recommend you use the "Remove Row" button to remove all of the existing info for the world you have selected.
Next you will want to add a new row for each non corner route node in your model file.

In the Path column you will want to add the name of one of the routes in your bone structure, do this for all routes that do not contain corners.



If you have a path that contains corners you will need to add two new rows. In one of these you should add a route that is named RNODE1K00y, and in the other you will name it RK00yNODE2.

For example this bone structure would form these entries:

Configuring Koopaling Paths

To configure koopaling paths you will want to select the "Boss Path" tab then select the world you want to edit from the dropdown.

I recommend you use the "Remove Node" buttons to remove the existing data.

Next you will want to add the names of each of the nodes the Koopaling will run to.

I noticed your demo download contains the entirety of nsmb2's romfs, you should probably update that to only contain any modified or custom files. Redistributing the entire romfs could not only potentially cause legal problems due to you redistributing files you don't have the right to, but it also causes the download to take a lot longer than it otherwise should.

Unfortunately, 6-castle contains some hardcoded elements that cause the level to crash if certain elements are edited, such as editing any entrances or adding/removing zones, so if you do want to edit 6-castle it is the least likely to crash if you only change tiles/sprites and avoid changing entrances or other things within the level.