well if your providing the unpacked exefs you could just get the name from the icon.bin, but really the name doesn't really do anything, i think its just being displayed so you can confirm the titleID was read correctly so it can then auto fill the Serial field, but you should be able to provide the correct serial if the game isnt recognized, afaik the serial isnt stored anywhere in the exefs,romfs,exheader its only stored in the actual cci image for the partition names, i guess if skiresM wanted to he could just add an option to read it from the original packed rom, but i think people should be ok to figure it out on themselves if it isn't in the listthank 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
I've tested it with WRC 2014, the generated file was a failure.
Stops @ Nintendo Logo.
-- 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
Even that list alone is great.https://github.com/SciresM/3DS-Builder/blob/master/3DS Builder/Resources/txt/3dsgames.txt is the table I made of titleids -> Product codes and names.
Can't you make a linux version? :3
I know, old thread and all but it's still very relevant with what's going on today and the new need to compile .3DS files from .CIA's created with seeddbd.binManual 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).
You can't build an update as .3ds-file.There is a problem where it won't let me build if the serial is CTR-U- instead of CTR-P-, am I doing something wrong? I want to build an update.
Alright, makes sense.You can't build an update as .3ds-file.
Updates only works as CIA.
You can't build an update as .3ds-file.
Updates only works as CIA.
There is a RSF generator for the old makerom version here. Most of the lines in RSF file is not really important, because those information is already included in exheader. A minimal RSF file and ExInjector would generate the same cxi as the carefully made RSF.Has there been any decent RSF generators or am I still going to need to use CTRTool to try and figure out all the stuff I need to set up correctly in the RSF? The new makerom builds went to a changed RSF layout so now all my old RSF files need reworking...Not looking forward to that.
There needs to be a better way of repacking CIA related things. RSF files are a mess to deal with if one intends to rebuild an existing title. Homebrew on the other hand is easier to do. But retail stuff can get tricky. Has there been any decent RSF generators or am I still going to need to use CTRTool to try and figure out all the stuff I need to set up correctly in the RSF? The new makerom builds went to a changed RSF layout so now all my old RSF files need reworking...Not looking forward to that.
You know what would be great? The ability to replace the contents of an existing CXI. Why go through the trouble of recreating the CXI when you can just change the contents of an existing one if you're just repacking an existing title?
The way hashes and offsets of the sections of the CXI are well known now so I'm surprised this hasn't become a thing either. I did try doing it manually in a hex-editor once, but it wasn't fun and what ever I did didn't work in the end.
ctrtool --content=$NAME $NAME.cia
3dstool -xvtf cxi/cfa $NAME.$ID.content --header ncch.header --exh exheader.bin --exefs exefs.bin --romfs romfs.bin --plain plain.bin --logo logo.bcma.lz
3dstool -xvtf exefs exefs.bin --exefs-dir exefs.O --header exefs.header
3dstool -xvtf romfs romfs.bin --romfs-dir romfs.O
EDIT STUFF
3dstool -cvtf romfs romfs.bin --romfs-dir romfs.O
3dstool -cvtf exefs exefs.bin --exefs-dir exefs.O --header exefs.header
3dstool -xvtf cxi/cfa $NAME.$ID.content --header ncch.header --exh exheader.bin --exefs exefs.bin --romfs romfs.bin --plain plain.bin --logo logo.bcma.lz
makerom -f cia -o TITLE.CIA -content $NAME.$ID:0:0x$ID (-content $NAME.$ID2:1:0x$ID2) -major $MAJOR -minor $MINOR -micro $MICRO