ROM Hack [Release] 3DS Builder

  • Thread starter Thread starter SciresM
  • Start date Start date
  • Views Views 63,236
  • Replies Replies 66
  • Likes Likes 21

SciresM

Developer
Developer
Joined
Mar 21, 2014
Messages
998
Reaction score
7,818
Trophies
4
Age
35
XP
9,489
Country
United States
I don't like .rsf files. They're stupid. So I made this thing.

uxvUvRN.png


It's designed to be as simple as possible.

Open a Romfs folder, or check the Pre-built box and select a pre-built decrypted Romfs binary.

Open an Exefs folder, or check the Pre-built box and select a pre-built decrypted Exefs binary.

Open the decrypted exheader for the game you're rebuilding. If the game in question was released before today, 3DS Builder should recognize the game's name and provide the correct serial. You can also enter a custom serial, if you want, of the form (CTR|KTR)-(P|U|N)-([A-Z0-9]){4}.

Choose a location to save the resulting file.

Hit go, and the program will generate a playable .3ds.

Source Code is available here: https://github.com/SciresM/3DS-Builder

And you can download it here: https://github.com/SciresM/3DS-Builder/releases
 
Could you add a way to use to use an extracted exefs ? (code.bin, icon.bin and banner.bin) ?

Or how can we rebuild en exefs ?
 
  • Like
Reactions: Margen67
Could you add a way to use to use an extracted exefs ? (code.bin, icon.bin and banner.bin) ?

Or how can we rebuild en exefs ?


It already supports both pre-built exefs_dec.bin files, and extracted exefs folders (containing .code.bin, icon.bin, and banner.bin.)
 
  • Like
Reactions: Margen67
Getting this alert when selecting my decrypted exheader. Its for pokemon x.
View attachment 19032


Spoiler: Like the alert says, your decrypted exheader is too small. I'm betting yours is only 0x400 bytes, it should be 0x800. Try extracting the exheader manually or with a newer version of ctrtool.
 
  • Like
Reactions: Margen67
Update: Just pushed v1.1 to Github, Kaphotics helped to refactor the code in a big way. Should be slightly faster for big ROMs, and the code is much less messy.
 
  • Like
Reactions: Margen67
I can add this, I mean, since I'm pretty sure a manual is just a second NCCH in the content array, but why would you actually care about having a manual?
Manual is another partition, right.
I care about a manual because I translated Zelda ALBW to Russian and working at LoZ OoT translation. Both have Russian manuals (in PAL roms for sure), so I'd like to include it.
Your tool is great for releasing translation (no makerom, rsf, bat, etc), it's pretty easy for target user (who will play my translated rom).
 
  • Like
Reactions: Margen67
thank you, rsf files are evil :)
i hope this runs nicely in wine


-- is there a problem if the content does not contain a romfs and we do not provide it? (not everything does right?)

if you are letting us give a custom serial, how about letting us give a custom title id? that is all in the exheader right?
and, is the name not in the exheader? why only current games and not future games will have their names recognized?

but still, very very helpful tool.
creating a fake ticket would be simple, i would make it completely barebones so we can tell it was made this something like this program. like, make the signature into a message of your choice :)
 

Site & Scene News

Popular threads in this forum