Overview
This The CVT project uses Commands as the nomenclature to define and create standard for defining and creating extendable features. The out-of-the-box built-in features have all been cavernized and include simple guides demonstrating the Cavrnus integration process for an already fully Cavernized and come with straightforward guides that demonstrate how to integrate Cavrnus into an existing application.
Level Setup
All of the core Cavrnus-logic is conveniently located in the AC_CavrnusCVTManager actor. This needs to be in the level along with the CavrnusSpatialConnector.
...
All of the corresponding Cavrnus specific command blueprints live in the following folders.
...
To easily add these Actors to a level, navigate to CavrnusCVT > Setup Level for Cavrnus & CVT
...
Cavernized Commands
Setting up CVT with Cavrnus is intended as seamless as possible. As such, the integration Integration involves editing CVT blueprints as little as possible, opting for Event Dispatchers to hook necessary Cavrnus logic. Aside from the Pawns, the default CVT blueprints do not depend on Cavrnus architecture because of this approach.
Follow the below links to setup each command CVT offers with the power of Cavrnus.