Roadmap for Module Loading and Module Configuration

[skaldarnar]

Motivation

Terasology uses a modular approach to game assets, concepts and features - everything is a module.
When creating a new game players select which modules they want to use and then proceed to create a new world to begin a game in.

We want to offer players the possibility to configure the selected modules before they actually launch the game or the world is created. This includes

• preview of world generation
  • Provide Access to Module Assets in AGS #5012 Provide Access to Module Assets in AGS
• configuration of world generation
  • New create game phase / UI screen: Game universe pre-initialization #4068 New create game phase / UI screen: Game universe pre-initialization
• key and control bindings for module-specific features
• configuration of game play features
  • Player selection of avatar / character model #2476 Player selection of avatar / character model
• configuration of rendering options
• RenderingModuleSettingScreen is not working and giving Java NullPointerException #5075 RenderingModuleSettingScreen is not working and giving Java NullPointerException

Proposal

tbd

Concerns

There are a lot of dependencies between different aspects, and it will be hard to model and resolve them correctly. We frequently run into issue like the following ones, where we suspect some race condition or loading order issue to be at fault:

• Race condition / bad initialization order during game start vs chunk generation #2385 Race condition / bad initialization order during game start vs chunk generation

tbd

Task Breakdown

tbd

Additional Notes & Related Resources

• Engine Initialisation and Lifecycle improvement #1770 Engine Initialisation and Lifecycle improvement
• Split engine to subsystems #4304 Split engine to subsystems