About

Package Hierarchy

All DuskModules are Packages and handled by the unity Package Manager. To keep the large amount of modules organised, they've been split up in four categories.

• 0 - Utility - scripting tools, interfaces and base classes. Used extensively by other modules to ensure strong compatibility.

• 1 - Tech - features that expand upon base Unity features, making them much easier to drag, drop and setup into the game.

• 2 - Game - gameplay features that provide common game mechanics or support faster iterations of your core gameplay experience.

• 3 - Meta - progression features that last between play sessions.

Dependencies

One module sometimes has a dependency on another module. The Unity Package Manager handles dependencies and ensures all required modules are included. All Unity Asset Store downloads are kept up to date whenever dependencies are updated.

A module can only depend on a module of equal or lower category. For example, a Tech module can't depend on a Game module, but the other way around is fine. Utility modules can depend on other Utility modules.

Optional dependencies are exempt from this limit.

Demo Packages

Each module contains a Unity Package which contains all demo content of that module. It contains at least one demo scene, which provides an example and description of how to use the module.

All demo folders are dropped in Assets/DuskModules/Demo.

The DemoUtility folder contains generic assets used by most module demo scenes, to reduce script and sprite redundancy.

Addon Folders

Some modules contain an Addons folder. The scripts within these folders only compile when the optional dependency module is available in your project, using both modules to provide extra features. If you don't have the required module, you won't be hindered by compile errors and can safely ignore the script.