Register - Login
Views: 10817101 Main - Memberlist - Active users - Calendar - Discord - Online users - Featured threads archive - News
Ranks - Rules/FAQ - ACS - Stats - Latest Posts - Color Chart - Smilies
04-23-24 10:40:04 PM

SMB3 Prime - Tutorials and Info - Object and Enemy Data (and orders) - New reply

   
Login Info: Username: Password:
Reply:
 
Options: - - |

Thread history
User Post
BlueFinch
Posts: 3/8
About vanilla (stock) SMB3 hacking:
1) LIMITS ARE YOUR FRIEND!
Starting out, you ought to observe the limits of a given level space. In saying that, I am telling you that SMB3 hacking is not like working with Super Mario Maker. Though this may change in the future, currently one must observe the limits of a given level space. Some level spaces were given more room for objects and enemies by the developers, while others were given just a few objects and enemies. Stay at or below the enemy / object limits for a level when you first start hacking to avoid the level breaking.

2) ORDER?
Though level 1-1 is followed by 1-2 on the overworld map, it rarely lines up like this code-side. If you overrun the byte limit in 1-1, it won't spill into 1-2, but it will spill into somewhere! Observe the order of a level codeside (nominal location) to know where you can borrow bytes from.

3) QuickCurly has done a lot for romhacking, and the documents below are his work. I am distributing them here because it is really good information.

4) I am also including an excel spreadsheet that KP made and shared in the discord a while back. This shows the grouping of the levels by object set. This is a great resource as it quickly shows what kind of levels fall into a certain category. (For instance, but not exclusively, this could be handy for someone making rigidly-themed worlds that only have a certain kind of level.)
SMB3 Prime - Tutorials and Info - Object and Enemy Data (and orders) - New reply





SMB3 Prime

Acmlmboard - v1.92.596 (02/01/2019)
©2000-2024 Acmlm, Xkeeper, Inuyasha, et al.

20 database queries.
Query execution time: 0.017180 seconds
Script execution time: 0.001122 seconds
Total render time: 0.018302 seconds