@Sparks said in Hosting and codebase recs:
last I checked, if you pulled out FS3.3 to replace it with a custom dice system, you lose a lot of the web integration (web-based character creation, web-based combat management, etc.).
Not a lot, no. I've worked very hard to not make Ares tied to FS3, so that people who want to use other skills systems will be able to easily.
If you don't use FS3 then it's true you don't get the FS3-specific web components, but that's a very small piece of the web portal functionality. You still get scenes, wiki pages, character profiles, web chat, help, etc. etc. You can even do part of chargen - just not setting skills unless your game has custom web code for their skills module. (But you'd need that anyway even if you used another codebase.)
@Sparks said in Hosting and codebase recs:
However, the tradeoff is that Ares is a fully-coded game, and while it's not terribly difficult to add to it, it is—with a few exceptions—far, far harder to rip out and replace chunks of it.
This part I agree with, but just to clarify...
There are several plugins that are designed to be optional in Ares -- FS3, weather, ranks, etc. These can be turned on or off with a mouse-click in the web config. Ares is also designed with a ton of config options to tweak how the systems behave.
It is certainly more difficult to replace core plugins, because many of them depend on each other. The plugin system will let you replace anything, but it does require custom code and I wouldn't say it's easy.
If you don't like the way Ares does things and are going to want to make extensive changes to core plugins, then yeah - starting from scratch might be the better option.