Introduction

This system is still under development

The MassTrace module is a system that provides a framework who's main goal is to create complex traces for complex gameplay mechanics.

This is achieved through a TraceConfig class that hosts various settings to design complex traces in a re-usable manner.

The second goal of MassTrace is to improve performance of systems that heavily rely on traces by providing an interface that allows regular gameplay code to interact with async traces inside of a ECS framework. The Mass Processor will use the settings provided by the TraceConfig to create your complex traces.

Managing collision settings

I am a firm believer that the current collision settings have a few pitfalls that are too easy to fall into. This is why I suggest watching this video before going into MassTrace to better understand how traces are preferred to be handled:

Summary:

• Do not ever use "Custom" collision preset.

• Use collision profiles.

• Each collision channel needs a purpose and team members need some way of knowing what presets and what channels are used for what. Suggests making a table detailing each collision channel and its purpose.

To-do

• Improve debugging

• Implement async traces for sweep traces