It now logs it`ll wait *before* waiting, and "Preparing game now" once the connection is established.

The chrome browser does not support the "headless-old" option anymore, and "headless-new" will show pop-ups, and alike. So we need the standalone executable.

This server needs to be started manually currently

This made a lot of C# Code obsolete. Moved it into individual obsolete functions and created a region for them.

Moved all ScrollView related Files into a new Folder for that.

WHY do they implement a JSONsavable Interface, only to throw 'NotImplementedException' on mandatory members they would otherwise not need?

All of those ints should be enums, but at least now Intellisense can tell you, what a specific value represents.

A script can reference the gameObject it is attached to by default. Requiring a explicit reference just invites bugs caused by miss-clicks.

Doesn't work in the launch menu, because globalObject doesn't exist there yet, but still better than nothing

Added "Quit Application" button to pause menu. Set menus to disabled by default if they got disabled by default

Couldn't bear the visual clutter in the editor, and having to go back to the launch menu.
Opening those prefabs caused Unity to change a whole lot of other prefabs and assets as well. At least some of those changes are strings getting surrounded by quotes, but for most others I have to guess option names changed in Unity 6. Gonna commit all at once, because I don't want to accidentally break something if a specific combination of changes shouldn't work.

By default unity 6 only allows for the use of HTTPS.

This setup will make working with JS easier. Also allows for the use of TypeScript. Might turn out useful later.

Disable more controlMappings when leaving a world

Not disabling them causes a memory leak according to unity. There is still one more instance of this happening I couldn't find.

.. missed two files

Instead of telling the player to do so

There are a bunch of ".. deprecated .." warnings, but the game runs

The ControlMapping has been changed, and now complains about not disabling the Actionmaps. If this persists through the next update, it should be investigated (likely a small fix, once it is clear *where* to call disable() )