Wednesday 31 December 2014

3.0 Status

This is just a quick update before the new year to outline where things stand with regard to RPGMaker Trans 3.0
  1. Ruby Parser: Pretty much done. It needs one modification to it to be complete, but that should be easy.
  2. Patch file format 3.1: Done. There's a lot of features here, but the most prominent are that patches in 3.1 format have proper support for comments, are file agnostic (so a translation can be shared between multiple files), and don't have translations jump around (if a translation is in a given file at a given place, it will remain there). One feature is missing, which is for translations with no context.
  3. VX Backend: Pretty much done. The only feature that requires implementing is translation of embedded scripts. This isn't too difficult, but it may not make the 3.0 release.
  4. GUI/CLI separation: Previously, I had a single executable which could in principle handle both GUI and CLI modes. In practice, Windows broke the CLI when running from an executable, and given most people use RPGMaker Trans on Windows, that pretty much killed it. So the GUI/CLI have been separated out, and so there will be two executables available from now on; one handles the GUI mode, and the other the CLI. The CLI should be handy for scripting etc.
  5. Frontend: Still working on embedding the backend into the frontend. Nothing too technically demanding, just annoyingly time consuming.
  6. (editted to add) Unpacking: Also need to bake in the support for unpacking a VX game. It's implemented, but needs reworking for the RPGMaker Trans frameworks. 
  7. (also editted in) Windows Support: I use Linux for development, and so I do need to add in Windows support. Mostly this is just packing up runtimes and stuff, so hopefully not too bad.
So, unfortunately, RPGMaker Trans 3.0 will not quite make it for 2014. But it should make it within the first month of 2015, which is something.

4 comments:

  1. I look forward to seeing the release. Will this update break translations like happened a year ago? Just so we know whether to back up our projects in advance.

    ReplyDelete
    Replies
    1. Not intentionally, at the very least (to be fair, I've never intentionally broken translations). The only change to 2k games is a fix for a race condition (which could have been eating bits of patches occasionally). In the future, I'll be providing an option to update version 2 patches to the new version 3.1, but that's not for now.

      Delete
    2. Sorry, Habisain. I didn't mean to imply that it was or would be deliberate. Hopefully you'll have more users willing to test the beta for you this time around to report that sort of thing to you before the official release - I seem to remember you being quite upset about that last time because there were so few.

      Delete
    3. Oh, that's not what I meant. I've just got a somewhat defensive-sarcastic way of replying to a lot of stuff. Fortunately though, a lot of the code has been through beta already, and because this is feature adding rather than bug-fixing, hopefully more people will be willing to test it...

      If anything, the prospect of a universal partial translation patch should be tantalising enough that people will test it.

      Delete

Note: only a member of this blog may post a comment.