Thanks for reaching out.

I originally intended for CDT to be used as a framework for modders to create custom damage types or to backport their existing mods to a new custom damage type. The lack of engagement made it not worth to upkeep the reference guide as I continued to develop the features of CDT for my own mods, so I scrubbed the guide from the mod page.

A few days ago, Norbyte's Script Extender added a way to create new damage types via Stats, which removes many of the workarounds CDT is performing. I'll be integrating this into CDT at some point in the near future and it will change a number of CDT systems in significant ways. It's good you asked me now so that this change isn't dropped on you unexpectedly while trying to decode CDT/Luminary on your own 😅.

As for your editor problems, I'm not sure why you are getting working story errors, but I wouldn't be concerned if you don't get the working story in game. The editor is notoriously out of date. Many of CDTs features are only functional outside of the editor anyway due to differences in how the editor and game handle server-client initialization and communication. I can say that Luminary and CDT don't crash for me, so it may be an issue with the process used to create your own project files for CDT and Luminary. We can get this sorted out though so you can have CDT as a dependency within the editor.

I'd be happy to help you get a project started with CDT and answer any other DOS2 modding questions via a more convenient communication platform, like Discord. Steam forums are a bit clunky and I don't check them too frequently. If you're interested, send me a steam friend request.

Oooh, definitely good to know about those up-coming changes - I'll drop you a request so we can follow up this discussion in a more convenient format!