-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An event not working in a non-english version #33
Comments
Hello I've noticed this bug too, here is any way to fix ? |
It looks like French translation uses cs+ as a base. |
@isage WOAW excellent you have a solution !!!! |
Can't believe nicalis did something that stupid -_- Indeed the french NX version used the files of cs+ to avoid rewriting all the text, since the text files are similar... EDIT: That was it. Removing the <ACHxxxx worked. Works like a charm now. I'm gonna update the package in a few. |
The form on your site doesn't work, i can't write you. |
I have DL and test your new FRENCH version 1.2, and now all is working fine, thanks :) |
@maxlefou i was wondering if i can include your translation with nxengine-evo? |
@isage of course, with pleasure! ^^ |
Thanks @isage |
(thanks to github for erasing my message while i was writing it btw! :D )
One particular event doesn't work on the french version of Cave Story: The event #1000 in Barr.tsc (when the player shoots Toroko at the beginning and speaks to her to talk to her about the pendant and trigger the fight with Balrog) Toroko doesn't reply when she is down. Quote doesn't display a ? at it but no dialog triggers, making the player stuck there forever.
I believe it comes from the NX Engine because:
For those who want to try, here's the french translation made ready for NX engine and having this strange glitch. This happens in the Linux and Windows versions of the engine.
(Is there a way to have a debug log of this core so maybe i can provide more info about this? Because RetroArch doesn't report any log at this point)
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: