Skip to content

Move gamestates to own library #3

@TheDudeFromCI

Description

@TheDudeFromCI

The game states plugin and loading screen plugin, (perhaps along with the splash screen?) should be moved into a separate library outside of WraithLib. They serve a very unique function and don't need to be implemented directly within WraithLib. Instead, it would make much more sense to migrate the core implement of these modules into their own library as a singular plugin while WraithLib just adds systems for implementing them to work with the other components like networking and the main menu.

Because game states works so closely with the loading screen, they should be combined into a single plugin that handles both. This includes the cheap asset loader wrapper which really should be built within the ActiveLoadingSystems resource by default. It might also make a lot of sense to merge the splash plugin code into that new game states library as well, since that plugin blends seamlessly with the game states plugin.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions