3 ms·
Currently the core is planned to remain closed source, although if I decide to put the project on ice at any point in the future I'll definitely put the source
by mikkelpaulson 5y ago
Currently the core is planned to remain closed source, although if I decide to put the project on ice at any point in the future I'll definitely put the source out there, that being a general pet peeve of mine.
I do have plans to build out integrations, starting with webhooks triggered on events like creating characters, advancing time, or moving between places. I've also heard some requests for a bona fide command-line binary, which I might do if the demand is there. The maintenance overhead is not insignificant, though.
- klik99 5y agoSounds like a good plan - hooks for datastores or even data types along with event hooks would also be good, but not as key. Being able to place arbitrary notes on characters/items/objects would be good (For example - I'd like to say this NPC is a ranger, and someday you may add classes, but arbitrary notes would be also just as good) This is where my mind goes - If this acted like a very thin layer that integrated with the plentiful amount of DM tools that already existed, and brought the context info with it, it would be a very powerful tool to centralize all this info. For example, I create a dungeon, the name generated either by your tool or by an API call to an existing service that parses and passes data into your system, then another hook generates a map and saves the persistent url/hash/some identifier into a custom field on that object. If done right, there could be a minimal but flexible API with purely client side hooks that the community could leverage to bring more features - off loading a lot of work without needing to opensource it. Of course, having said all that, even just as it is right now is super useful and exciting and I likely will use it even without any of those things!