No, first you have to pack the folder into an archive using SARCPack (you'll need to use command prompt because for whatever reason it doesn't like drag/drop, just "sarcpack.exe/py folder"), and then compress that archive using yaz0enc to get the SZS file. I'll fix that stuff some time when it finally matters.
sorry to ask again. was it the end of this month we are hopeing to see some releases? i did try looking for the answer but there is so many pages to this thread
I can't get the program to work.....
Forget it... now I know how.
I don't have SSB4, but I do have SM3DW, I don't know what's mario's file's name is, if "somebody told me/I find it" I will rip the model with textures.
My mario kart is version 3. So i'm guessing thats the latest? I've erased all my internet settings now until I get some time to block all the IP's through my router.
Hey,
Does anyone here have access to the Mario Kart 8 BFRES files? I'd like to mess around with some of the course models, but I don't know how to rip the game, etc.
Hey,
Does anyone here have access to the Mario Kart 8 BFRES files? I'd like to mess around with some of the course models, but I don't know how to rip the game, etc.
It seems like you're just starting out with this stuff, at least the type of programs and the command line.. Though, you should probably learn somewhere else, and not the hacking discussion thread.
I'm working on a one, also I'm doing some texture editing, then I would ask NWPlayer123 if he can test thing for me.It's nice to see someone messing with NSMBU though. Hope you can make some custom levels........
Uhm, ObjectData/Mario.szs maybe?
Ok, I have a small nuisance to report. As I mentioned a few pages ago, the current bug we're looking at doesn't work in firmwares lower than 3.0.0, because Nintendo implemented the Internet Browser on firmware 2.0.0 using a really old WebKit version as basis (534.52). It was later updated on firmware 3.0.0 (536.28) and has stayed the same up to firmware 5.3.2.
Considering that the IOSU exploit was designed with firmware 3.x in mind and it would be easier for me to test the new WebKit bug on firmware 3.x, I'm going to update my Wii U to firmware 3.0.1. This means I won't waste any more time looking for a way to exploit the browser for firmware 2.1.1.
I hope this is not a problem (I really doubt anyone would be interested in seeing an exploit for such an old firmware version anyway) since I began by stating that I would try to port an exploit for each firmware I could find.
Ok, I have a small nuisance to report. As I mentioned a few pages ago, the current bug we're looking at doesn't work in firmwares lower than 3.0.0, because Nintendo implemented the Internet Browser on firmware 2.0.0 using a really old WebKit version as basis (534.52). It was later updated on firmware 3.0.0 (536.28) and has stayed the same up to firmware 5.3.2.
Considering that the IOSU exploit was designed with firmware 3.x in mind and it would be easier for me to test the new WebKit bug on firmware 3.x, I'm going to update my Wii U to firmware 3.0.1. This means I won't waste any more time looking for a way to exploit the browser for firmware 2.1.1.
I hope this is not a problem (I really doubt anyone would be interested in seeing an exploit for such an old firmware version anyway) since I began by stating that I would try to port an exploit for each firmware I could find.
Have I missed something? Was there something that one could do with MK8 that they can't if they aren't on the latest version??
2.0.0 -> Version: 0x08 (534.52)
2.1.0 -> Version: 0x14 (534.52)
3.0.0 -> Version: 0x31 (534.52)
4.0.0 -> Version: 0x59 (536.28)
4.1.0 -> Version: 0x66 (536.28)
5.0.0 -> Version: 0x71 (536.28)
5.1.1 -> Version: 0x82 (536.28)
5.3.0 -> Version: 0xB1 (536.28)
5.3.1 -> Version: 0xC1 (536.28)