@TorgaardWith Foundry, I have to underline the poor documentation and minimal support, a problem compounded by all the modules. It is easy to install modules to expand the core functionality, but perhaps too easy. You can quickly run into issues with conflicting modules, modules that are not kept up to date when the core program updates. Luckily it is easy to remove modules, but it does add to the complexity of troubleshooting systems.
Heh, there ya go - my experience is a
mirror image (pun totally intended!) of yours.
Encounter Library's videos were a godsend, and the
Foundry Knowledge Base is definitely helpful, but I kept wanting to jump to a wiki (or something) for answers to specific "situational" questions and - maybe more importantly - examples. Frequently I just couldn't quite get the answers I was looking for. So every question required alot of searching in multiple areas (web, Discord, reddit, find the part in that Encounter Library video where he talks about it, etc) and more often than not I just couldn't find it. That being said - I did make it, I am there - I've pretty much figured it all out, and Foundry is pretty dang amazing! I get the impression it's already where roll20 is at, and perhaps beyond - and flags behind Fantasy Grounds only in the Combat Tracker automation.
I initially played around with the core Foundry build, and after 'x' number of hours of experimentation with it, I ended up with a list (in my coconut) of things it didn't do that I really hoped I could find as community developed Modules. Found a bunch of modules that helped, found a bunch of others that were just cool-as-hell and I "had to have!", and back into Foundry I went. Oof! Ya, that was a struggle. Couldn't tell what was a core feature, module added functionality, a conflict between modules, or just a bug. Our first session was a bit of a debacle, as a module config I messed with caused targeting to go off the rails, and frequently players ended up attacking and doing damage to themselves instead of the enemy.
Pro Amateur Tip for new Foundry users: Resist the "Kid in a Candy Store" syndrome when exploring Foundry's wondrous array of community developed add-on modules. Kinda knew I shouldn't have taken on so many at once - so totally my fault, not Foundry's - but I just couldn't stop myself. Download a module, setup an array of tests, learn the module's functionality back-and-forth, and THEN download that next module. Then go back and do ALL the same tests (you're checking for conflicts with a previous module install). Rinse, repeat. If something breaks, simply turn that module off (and submit a bug/fix to the dev on github). Test. Rinse, repeat. Yes the testing adds time, but you're also learning Foundry as you go, training your brain how to "do stuff" with Foundry with repetition.
Also, self-hosting is more of a hassle than many users will want to deal with. I ended up going with The Forge after playing around with hosting it on my own AWS environment. Not only does The Forge take care of hosting, but it provides a layer of support that you don't get by just buying The Foundry.
Ditto. I too went with The Forge for the same reasons: Didn't want to go through the potential hours of frustration helping my less-than-tech-savy players on how to open ports, troubleshoot, etc. The Forge made it all so simple. "Players - go to this link, join game, play virtual tabletop D&D". Done.
I've never really used automation in any VTT because they all seem to require too much data entry.
We diverge a little there. While an oft muttered mantra to my players over the years on Fantasy Grounds has been, "Don't get tunnel vision. We don't have to automate
everything" - there is a level of automation I
gotta have: Tracked and automated conditions and effects. Pen and paper DM's manage to keep track of all that stuff, but Cod knows how. I just don't have the head for it. I need all my (limited) brain-power to focus on painting word-pictures during combat, making smart tactical decisions for my mobs, adjudicating rules questions, etc. I just about strip a gear, and immersion breaking screw-ups (on my part) abound, when I have to focus on when this or that condition expires, who is supposed to roll what and when, etc. I am eager to learn and do the data work to learn whatever functionality comes with Foundry to enable that level of automation, but learning how to be a programmer is a bridge too far.