I’m currently working on a campaign for the Onyx Path system Exalted, and I wanted to build out a Foundry companion for running the game online.
That said, the Exalted 3e instance isn’t actively supported by the publisher, Onyx Path, and only lightly supported by the community at large.
I’m curious to know if anyone else is working in a system with minimal 3rd party support and what their approaches have been to implementation.
Should I just go with a more generic but better supported mechanics engine and try to jury-rig the game from there? Should I stick with what’s out there? Or is doing Foundry for this kind of project s fool’s errand?
Have you seen https://github.com/Aliharu/Foundry-Ex3 ? Someone has built at least some kind of system with a character sheet and some combat tracker support.
In general, for first system baby steps what I see people do is what’s been done here… build a simple system module that focuses on providing PC and NPC sheets with the key trackables, and then using those with the built-in dice-rolling and tabletop features with little automation or system-specific features to play more or less in a similar style to pen and paper. Then if any programmers are involved people may start to work on more sophisticated features.
That’s the one I’ve got installed, but its a being supported by exactly one guy as a hobby, as I understand it. So, not as feature rich as some of the other systems.
That’s kind of the way of it with more niche systems. Unless you’re a software engineer willing to invest substantially yourself, you’d compare it against things like https://foundryvtt.com/packages/worldbuilding or https://foundryvtt.com/packages/grpga and I’d generally expect it to compare favorably unless it’s broken/out-of-date.
But I don’t think there are any shortcuts. If there were a strong storyteller system then maybe you could adapt by running in that, but I don’t see one. And although I don’t know much about Exalted, it doesn’t seem to be super close to any of the “big” systems I know about that are really well-supported in Foundry. I think “not feature rich” is probably to be expected.
Fair enough. I’ve got near zero experience with the generics, so I wanted to check whether this was the more rational way to go.
But in this case, I’ll stick with what I’ve got.