What's new in SayWhat 4.3.0
Jan 16, 2022
- Continuing on with the whole “translations” thing I’ve added a new button to the toolbar.
- This new button will auto generate static translation keys for any lines that need one.
- So, changing something like this.
- Using static translation keys is totally optional - this just helps speed things up if you do choose to use them.
New in SayWhat 4.2.2 (Jan 15, 2022)
- Another quick bugfix release that helps translations exports play nice with existing files. It will now match the column count against the rest of the CSV file while merging with it.
New in SayWhat 4.2.0 (Jan 14, 2022)
- It hasn’t been that long since the last update but I’ve had some time to add an important new feature (and a few less important features).
- First up, translations!=:
- You can now export a translations CSV file of your dialogue. What this will do is grab any dialogue or response lines and add them to a CSV for translation. The key for each line will either be itself (the dialogue of a dialogue line or the prompt for response lines) or a manual key if there was one specified.
- To add manual translation keys to a line, add [TR:SOME_KEY] to the line just after the dialogue or prompt that needs translating (where SOME_KEY is the manual key you want to use).
- If you have a duplicate key on a line that doesn’t have duplicate text to other occurrences of that key then you’ll be shown an error.
- If you don’t want to manually add keys then each line will use itself as the key, de-duplicated in the final list.
- Next up, I’ve added some settings that can be changed:
- SayWhat will now alert you if there is a new version (either automatically, if you want, or manually).
- You can also choose to turn off the periodic error checker (if off the error checking will only happen on save).
- And lastly, you can choose to treat lines without manual keys as errors. This is handy if you’re trying to get 100% of lines to have manual keys and you’re not sure if you’ve missed any.
New in SayWhat 4.1.0 (Jan 11, 2022)
- On top of updating the Itch page with some more documentation, I’ve added a couple of new features to the editor and fixed a few bugs.
- So you can now jump to a known title, create one if it doesn’t exist, or pick a title from the list of known titles to insert.
- I also fixed an issue with the Godot addon which previously required a reload of the project before it could be enabled.
- There were also a few minor parsing bugs that I’ve fixed up too.
New in SayWhat 4.0.0 (Jan 11, 2022)
- A whole new SayWhat:
- SayWhat has been rewritten from the ground up.
- The new workflow is smoother and comes with new features. Gone are the clunky conditional prefixes - now you have proper conditional blocks! And responses can have their own blocks too!
- You also get syntax highlighting and better error checking.
- You can export out to Godot Resource, JSON (I now have a proper JavaScript runtime), as well as to a standalone HTML page.
New in SayWhat 1.7.0 (Oct 28, 2020)
- This update adds support for inline node jumps. Now you can have conditional node jumps in the middle of a dialogue node:
- Character: Some dialogue. [if some_condition] -> Another node
- Character: More dialogue.
- This change also renames options to be responses in the exported XML, JSON, and Godot Resources. If you are using my Godot addon then you’ll need to update to version 3.
New in SayWhat 1.6.0 (Oct 3, 2020)
- I’ve updated the Godot resource export so that it can be more easily used with my new SayWhat Godot addon.
New in SayWhat 1.5.0 (Sep 26, 2020)
- This update adds an initial export option for Godot resources (.tres) that packages a list of dialogue nodes into a dictionary keyed by node IDs.
- To use the resource you will need to create a script at Text/DialogueResource.gd with this in it:
- extends Resource
- class_name DialogueResource
- export(Dictionary) var lines
- …where lines is the dictionary of dialogue nodes.
- In future updates (and as I find the time) I’ll add some options and streamline this process but it’s workable for now.
New in SayWhat 1.2.0 (Aug 1, 2020)
- This update makes a change to the IDs in the exports. Where entry points used to use sequence and node names, they now use IDs.
- My reasoning behind the change is that IDs are meant to be unique across a whole project and will never change, whereas names can’t guarantee either of those things.
- Node IDs now show up in the UI and are clickable to copy to your clipboard.
New in SayWhat 1.1.0 (Jul 19, 2020)
- Added support for Resx
- Fixed an issue with exporting
New in SayWhat 1.0.1 (Jun 22, 2020)
- This update fixes an issue in the exported XML or JSON where blank lines were breaking the ID chain.