Hi! Some of you may have noticed I've been on the board a lot within the past month or so.

This is because I am currently in the process of crawling all threads and centralizing the info I can find in a thorough, easy-to-digest package. Right now all I have is a myriad of text files that I will later post as threads. Some are huge, some are stubs.

There's notably going to be a lot of beginner-friendly guides on how to do just about anything (outside of ASM), along with what to watch out for, etc.
Looking at old threads made by users who struggle to understand how NSMBe or modding works can teach you a lot- some expect it to be as simple as making a level in Mario maker, and it's up to us to teach them that modding is not like that. NSMB may be flexible, but it wasn't meant to be modded. There will be crashes, there will be weird stuff, and there will be a lot of troubleshooting.
(Also- if you see threads move from one forum to another, that's because I am sorting threads as I go)

Crawling the board is only part of the picture, though. I'm also testing just about anything I can think of in an effort to document everything in an organized manner. I am preparing a lot of threads that reference one-another, therefore I will likely be releasing most threads all at once. There will be a lot of illustrations to make them easy to follow along. _{They can be converted into wiki pages if you wish, but I'd rather make them threads for a few reasons.}


Here's a non-exhaustive list of what I will be covering, in no particular order:

-Overview of how to run NSMBe (level editor, understanding the UI, level design guidelines, graphical editor, file handling, patching...)
-Troubleshooting methods (e.g. delete everything in a level until it starts working again)
-Basic tutorial on editing DS metadata
-Graphic editing (explain indexed palettes)
-Tips and tricks
-Tile behaviors (comprehensive)
-Jyotyu (I've listed all objects and all of their known quirks with extensive trivia)
-Blue coin palette
-Template setups (provided as NSMBeClips)
-NSMBe to CoinKiller clip converter (that one guy who's making a NSMB2 remake, this is for you)
-How to edit demo_castle like a level
-How to not perish
-Community remix retrospective
-Sprites (comprehensive)
-Sound sets
-Music hacking tidbits
-List of all graphical files and their respective uses (interactive)
-Slope control guide
-Tileset/background compatibility (comprehensive)
-Level hex recap
-External resources loaded by tilesets and backgrounds (NCG animations, NSBTX files)
-NSMBe gripes (5.1 abandoned features, 5.2 jank, 5.4 changes) and suggestions


All of this takes time to test out, document, illustrate and then convert into threads. I want to be thorough, why is why I plan to keep working on most of this alone as it gives me more control and agency. I am only one person however, hence it would only make sense to recruit people who are interested in this documentation effort.

For example, testing out tile behaviors is a very monotone endeavor (that could very well be automated) which could easily be worked on by several people at once with little risk of overlap.


Please reply if interested.

-Threads generate activity. If this can revive the board a little bit (yknow, kind of a "hey we aren't dead" publicity stunt) then I'm all for it.


-Threads are what users see right out of the box, while the wiki is kind of.. tucked into a corner.
(And then brought offsite because it was barely fleshed out at all)

I wouldn't be surprised some people never realized it existed.

Having both the threads and the wiki pages adds some redundancy where each can specialize in an area: threads can be especially beginner-friendly with a lot of padding, while the wiki can be more of a dense, thorough all-purpose reference akin to the Unity documentation if you've ever seen it.

If only the wiki stays up-to-date as it is now, a lot of people will be confused seeing the threads.


-Threads actually notify people and can be replied to. Talk pages are nice, but I never feel compelled to check them. For any given article, nothing tells me ahead of time whether there is anything in a given article's talk page.


-Threads aren't forced to be wiki-shaped. The format can very, some threads will be focused on being newbie-friendly while others will be nerdy with trivial details.


-Acmlmboard nostalgia



There's probably more, but I can't think of anything right now. It's a personal choice I'm sticking with since I'm leading this effort.

(this doesn't mean wiki pages can't be used btw- it just means just that I will be releasing the infobomb packages as threads for the mostpart)

I am not, no. I won't be handling code stuff, as I attempted to imply in my first post.

Also, searching for info in a Discord server is a fairly miserable experience as Discord was not made with archival in mind, only conversation. The search function is also limited. I will not be relying on this as a result.