Hacking Queen's Blade: Spiral Chaos Translation Project ( Hackers needed )

[2PhoneShorty]

I think I noticed a few months ago. I asked our hacker Flame1234 about it, and he checked an old build from July last year and they were working fine.

I don't know if they got glitched sometime during the changes in process for compiling/building, I want to check building the game the old way but I'm too busy lately

Do you think a different save file would help? I could send one of mine if you wanted.

 

[leecherboy]

Hmm, it shouldn't have anything to do with the save file, we've always used the same ones...
If only I had some time to mess around with the different builds...

--------------------- MERGED ---------------------------

 

[dawnbomb]

Don't give up, get a playable build! ;~;

atleast try to get a compiled working playable build of what all you have so far, as it looked from the outside like this project is dying

 

[Arahabaki]

Still rooting for you guys. Its a lot to take on and its nice to see such dedicated fans doing so. Good Luck!

 

[Shrike]

Hey.. I don't want to be a necro-poster.. But is this project still alive ?

Would love a translation for this game :3

 

[NANASHI89]

I wanna know this as well. Still working on this?

 

[2PhoneShorty]

Hmm, it shouldn't have anything to do with the save file, we've always used the same ones...
If only I had some time to mess around with the different builds...

--------------------- MERGED ---------------------------

I know someone who may be able to give some feedback or advice but his account is on a different website. If you'd like to know more shoot me a PM.

 

[darksix]

Project is still operational.

Thinking of turning what was python into pure C, and making the whole process a bit easier with a reverting function
in case of any odd hangs, or screw-ups that might happen. I may actually do that first in the python scripts for at
least saving backups of the EBOOT and shared.bin files with an appended date at the end. I'm not to certain on
eboot and all, but will find some specifications pages hopefully and get up to speed on that. I may do a clean version
and start from the beginning using a batch conversion, just to see what is, and isn't working since it's mostly translated
and all, or looks to be.

Thanks,
Six

 

[2PhoneShorty]

Project is still operational.

Thinking of turning what was python into pure C, and making the whole process a bit easier with a reverting function
in case of any odd hangs, or screw-ups that might happen. I may actually do that first in the python scripts for at
least saving backups of the EBOOT and shared.bin files with an appended date at the end. I'm not to certain on
eboot and all, but will find some specifications pages hopefully and get up to speed on that. I may do a clean version
and start from the beginning using a batch conversion, just to see what is, and isn't working since it's mostly translated
and all, or looks to be.

Thanks,
Six

Wow you're a life saver for the project Six. I'm forever grateful for your help!

03

 

[Meeep]

Hi, complete newbie to PSP hacking here and I had a question regarding the instructions back on page 4. Namely the first step, applying the patch to the ISO. Where would I go to get the tool that applies the xdelta patch to it? What program do I use for that?

Thanks!

 

[2PhoneShorty]

Hi, complete newbie to PSP hacking here and I had a question regarding the instructions back on page 4. Namely the first step, applying the patch to the ISO. Where would I go to get the tool that applies the xdelta patch to it? What program do I use for that?

Thanks!

Hi there!

Since it doesn't seem like that many people check up on this thread,
it may be best if you go to the beginning of the thread and read through
the pages. There has been helpful snippets and info posted throughout.

Hope it helps!

 

[RagoXXXX]

I'm glad that they're stadly working on it cause the translation would end up cleaner ^>^

 

[darksix]

I'm glad that they're stadly working on it cause the translation would end up cleaner ^>^

A good bit has been translated, just mainly now a few display glitches here and there.

Would be really nice if I could get hold of exactly what was done to 02.bin with that xdelta differential patch. Going through all the pages on the forum
it's hard to distinguish really, what happened where and all. But mostly deciphered now at least.

Thanks for all the optimism and the extreme waiting for the finished product. -Six.

 

[mouthbreathe]

I'm having a lot of trouble applying the patch and building the ISO with the patch as described on page 4. Is it not possible for someone to apply the patch and upload the patched ISO somewhere?

 

[darksix]

I'm having a lot of trouble applying the patch and building the ISO with the patch as described on page 4. Is it not possible for someone to apply the patch and upload the patched ISO somewhere?

Hi there, if you are talking about the xdelta patch that redoes EBOOT.bin and SHARED.bin you shouldn't need to use the Xdelta patch, and just run build.py as this also runs the assembly code which runs the code from Mod.asm and redoes it in the same way that patch was originally made. (I may be mistaken here, since I do not know if anything else was originally added into that delta patch, but It successfully works without it.)

Do you have the Mod.asm assembly file? keep in mind if you do, it is probably a very old version of it that has had some tweaking since then as well as the building tools. At this time I cannot post the latest assembly code since it is in an unfinished state. I have been pretty busy on something for a good while now, but I plan to pick back up and finish it all in the coming week or so. If the build still fails then throw a message on here, and I'll help rectify it.

A reason we don't throw up a patched ISO is because of the reason with legality for one mostly, and secondly It's not bug free totally yet. The end goal is to make a patch that you can add on to your existing original ISO.

Thanks, Six.

 

[mouthbreathe]

Hi there, if you are talking about the xdelta patch that redoes EBOOT.bin and SHARED.bin you shouldn't need to use the Xdelta patch, and just run build.py as this also runs the assembly code which runs the code from Mod.asm and redoes it in the same way that patch was originally made. (I may be mistaken here, since I do not know if anything else was originally added into that delta patch, but It successfully works without it.)

Do you have the Mod.asm assembly file? keep in mind if you do, it is probably a very old version of it that has had some tweaking since then as well as the building tools. At this time I cannot post the latest assembly code since it is in an unfinished state. I have been pretty busy on something for a good while now, but I plan to pick back up and finish it all in the coming week or so. If the build still fails then throw a message on here, and I'll help rectify it.

A reason we don't throw up a patched ISO is because of the reason with legality for one mostly, and secondly It's not bug free totally yet. The end goal is to make a patch that you can add on to your existing original ISO.

Thanks, Six.

The only file I downloaded was the xdelta patch but all of this is way beyond my realm of knowledge anyways. I think it'd be safer for me to just wait for the finished product lmao. Still, I'm just glad this is still getting worked on! Best of luck to you.

 

[leecherboy]

Thanks for the interest everybody, and sorry it's taking so long, but we're mainly a couple guys working regularly on this--while also managing a weekly blog.

On happier news, we're close to finishing the story proofreading, and we're trying to get some internal playtesting going, to cover all the many routes and stuff while squashing all the bugs we can.

The main bug that has us stumped right now, however, is a certain character limit. Most notably, when you finish an enemy, you can get a message saying "In the broken X armor, you found Y!" However, this seems to cap at 31 chars, which is really not optimal considering some of the item's names are rather on the long side:



There's always the possibility of erasing the first part and just go with the "Found Y", but we'd be losing information. I'm not sure if someone here has faced these kind of hardcoded limits...?

 

[aw013]

thanks been waiting for this game

 

[Shrike]

I suggest you just go for "Found X".

You also could just say "You found smth. in that Armor!".

This would be super lazy .. I know.. But actually that are not the things I rly care about when playing the game Item descriptions are much more important

 

[corn2222]

There's always the possibility of erasing the first part and just go with the "Found Y", but we'd be losing information. I'm not sure if someone here has faced these kind of hardcoded limits...?

Maybe you'll erase words "broken" and "armor" and save "in the x you found y"?