[BUG - Develop] Global Scripts loading doesn't catch parse errors

Describe the bug

When there’s an error with loading a global scripts module, e.g. it imports the Room class but that class has a syntax error, the loading error isn’t caught and the traceback points to this line with a KeyError

To Reproduce

Steps to reproduce the behavior:

1. Create a simple global script which imports a class such as Room from your game dir, and add it to settings.py
2. Introduce a syntax error to your Room class, such as an extra space in an indent.
3. Reload the server.
4. See error

Expected behavior

It’d be more useful if there was an error thrown which indicated that the script had failed being loaded (and, ideally, why), as the current error invariably leads people to think there is a problem with the global scripts dict in settings.py.

Develop-branch commit

f093c8bcb

Additional context

I feel like it should be catching that kind of an error in class_from_module or it should at least be throwing an exception in load_data but neither seem to be doing so. Instead, they just silently don’t load the script.

[InspectorCaracal]

The error is much clearer, which is a definite improvement, but I’d prefer if the game failed to start due to a broken global script rather than continuing to start without it. If I have a global script, the chances that I have other systems relying on it are very high, so having the game start without that script available could cause a cascade of broken systems.

[InspectorCaracal]

@Henddher That’s the one!