Blueprint GUI can now handle resolution changes.

Percent signs should no longer cause saving to fail. I needed to escape any % signs in the strings in lua.

Spaces should now appear normally when saved as part of strings inside components. They were being changed by my whitespace clearner function when they should have been ignored.

Fixed a bug that allowed hidden control characters such as carriage return to wreak havoc on the save file.

New version of saving that should allow more string types. Before I was copying barotrauma's natural style of quotes, but that limits what you can store. Anyone who tried to store quotes in a string would mess up the save formatting.

The new version uses <<<STRINGSTART>>>yourStringHere<<<STRINGEND>>> so users would have to use those specific strings to screw up the file format now, which is unlikely.

Fixed a localization bug in languages other than english. Thanks Yun-Shan for the bug report and fix.

Registered the new components that were added. They have not been included in lua yet by default so this is needed.

I also changed the explainer text on unit tests to explain how failure occurs in a more detailed way. False positives are common with that so don't freak out if it says you failed a unit test. There is a reason its off by default.

Fixed a bug causing crashes if playing the game in testing mode inside the sub editor (if you actually hit the play button in the sub editor). Thanks Massive Bubble Phenomenon for the bug report.

Added popup box to load failed dialog explaining what to do and what caused it.

Update to loading complete check. This new version is not as strict as the unit test and is not a gaurantee the loaded circuit is identical to the blueprint. It only gaurantees that all relevant load functions ran to completion without crashing or throwing an error.

On the bright side its way less sensitive to changes in the circuit such as input values changing.

Unit tests are now off by default. They can be temporarily toggled on with the console command "bp toggle tests". No underscore for that one. They will turn back off when you restart lua or restart the game.

The tests are generating too many false negatives. The tests do work, but the problem is if you load a circuit after it already has its inputs wired, then those inputs can change the values in the components. This triggers a failed test even though the circuit is actually fine.

Perhaps I will come up with a better version of it in the future.