- Fixed a bug where newly created legacy attack box couldn't be edited ChronoCrash Modders Tools @kimono
- Fileselector will now parse "steamer" entity type @O Ilusionista
- Various optimizations in text editor
New "alternate versions feature"
- this is a neat feature I pulled from another project, very useful if for some reason you need to maintain several branches of the same file. I use it mostly to test radical changes in a file while preserving the old model.
Here's how it works :
- While in "Text" tab, in the right panel you can click the green add button to add a version of your file. Enter a name for the version.
- When you load a version "B", then the content of the actual file is swapped with the content that is in the version "B" model
- From here, each change in the actual file will also be replicated in the version "B" model, because the file and the current version model are tied.
- When you load another version, let's say version "A", then the content of the actual file is swapped with the content that is in the version A model.
- But all the content of the version B is still intact and available in the version B model, which you can load at any time
Previous versions of CMT tried to preserve files character encoding for files that were created outside of CMT. This could cause save/overwriting issue when trying to save characters that were not supported by the file original encoding scheme. Because this error occurred during the writing process, in the worst case it could cause the content of the file to be wiped (but if you didn't disabled CMT backup systems then there would still be two backups made before trying to actually overwrite the file, so nothing was really lost).
To prevent these issues, I added two options (activated by default) : "Safe file write" and "Change file encoding on write error".
The first option ("Safe file write") when enabled, adds an intermediate step in every save process : the file to be saved/overwritten is copied, then the changes are saved in the file's copy and not in the original. If no error occurred during the save process using the copy, then and only then we replace the original file with the copy, and delete the copy. This intermediate step is transparent from the user perspective, nothing changes.
The second option defines what happen when an error occurs during the "safe file write" step explained above.
When "Change file encoding on write error" is disabled, then the user will just be warned that the file couldn't be saved, and he will have the error crash to report. The original file will stay as it was, the changes won't be saved.
When "Change file encoding on write error" is enabled (default), then CMT will first try to save the file using a different encoding, starting with UTF-8. If this still fails, then the user will just be warned that the file couldn't be saved, and he will have the error crash to report.
So, if you absolutely want to keep your files encoding scheme, disable "Change file encoding on write error". If you don't mind, then keep it enabled. Again, this change of encoding will only occur when required, which for most users is never or very very rarely. If you never had this error before in CMT, it means this error never happened to you, so it probably won't happen at all.
@bWWd
- Level direction "leftright" now processed @dantedevil @maxman
- Fixed this bug (I think not 100% sure) : ChronoCrash Modders Tools @O Ilusionista
Fixed this bug : ChronoCrash Modders Tools @O Ilusionista
and also fixed this bug (I think that was it, not 100% sure) : ChronoCrash Modders Tools @maxman
Fixed this bug ChronoCrash Modders Tools @maxman
In addition to the fix, CMT will ask you if you want to re-affect files with unknown project to the current project. This should happen only when reopening old CMT sessions.
Also now when you re-open a session that have files from multiple projects, the first time you try to re-open a file from a project you didn't reopen yet, CMT will automatically load the project before loading the file.
- Added option "Entities type NONE - facing hack", for Level Editor.
When enabled, entities type none facing will be processed separately
When disabled, entities type non facing will be processed the same as any other entity @dantedevil
Warning : this option was basically always enabled in recent versions of CMT, but in the new version it is disabled by default, so if you want the previous behavior back, you will have to enable the option @O Ilusionista
Added minors improvements to "colored projects" feature. All these changes require at least two projects opened :
- Now pressing "F1" will switch from one filter project to the next
- In file selector, added option "open equivalent in project X" in context menu of files. This neat feature allows you to quickly open the same file in another project.
- This last feature is also accessible from the context menu of recent files bar (just above the main editor, in the center)