18 months on : FG vs. Roll20 vs Foundry

[MostTornBrain]

Five hours later, here is my first attempt at a written Quick Start Tutorial. This is one for how the parts of FGU fit together to prepare an adventure to run.

If useful I will make another for GM's for character generation and for running a session.

https://docs.google.com/document/d/1...it?usp=sharing

Cheers, Hywel

Oh wow! That’s exactly what I had in mind! I haven’t looked at it detail but that’s the type of intro document I was sorely missing a month ago.

Thanks so much for taking the time to put that together! It will definitely help others new to FGU in the future.

Cheers,
Brian

[WishX]

Five hours later, here is my first attempt at a written Quick Start Tutorial. This is one for how the parts of FGU fit together to prepare an adventure to run.
If useful I will make another for GM's for character generation and for running a session.
https://docs.google.com/document/d/1...it?usp=sharing
Cheers, Hywel

That is excellent work! I'd very much like to see a GM's version for char gen as well.
I'll see if we might be able to incorporate them into the wiki somehow.

Thanks!

[HywelPhillips]

And here's one for generating a party of Pre-Gen characters to run your first game. It's from the GM's perspective (as is the previous one). Part three will be how to actually run a game (for the GM learning) - combat tracker etc.

Happy to figure out a way to incorporate them into the Wiki once I've slept on them and re-read them a couple of times to catch the most obvious mistakes.

https://docs.google.com/document/d/1...it?usp=sharing

Cheers, Hywel

[Nylanfs]

Also maybe find somebody that is interested in FG, but hasn't started and use them as the proof readers so if they have questions it can be incorporated into the doc. Alternately using the rubber duck method would help, but outside feedback would probably be better.

[WishX]

And here's one for generating a party of Pre-Gen characters to run your first game. It's from the GM's perspective (as is the previous one). Part three will be how to actually run a game (for the GM learning) - combat tracker etc.
Happy to figure out a way to incorporate them into the Wiki once I've slept on them and re-read them a couple of times to catch the most obvious mistakes.l

Excellent work! Looking forward to Part 3!

[HywelPhillips]

Part 3: A dry run of the game

https://docs.google.com/document/d/1...it?usp=sharing

If you have feedback, let me know. Or I can hand these off to someone for inclusion in the wiki and maintenance (he says, hopefully...)

Cheers, Hywel

[WishX]

Part 3: A dry run of the game
https://docs.google.com/document/d/1...it?usp=sharing
Or I can hand these off to someone for inclusion in the wiki and maintenance (he says, hopefully...)

That would be me. I'll be reading through everything today and, unless there are glaring inconsistencies or outright incorrect information, will likely format it and get it added to the wiki in the near future.
What are the odds I could get you to do one as a newb who's never touched FGU before?

Thanks so much for all your work! We here at Smiteworks and the community at large appreciate it!

[HywelPhillips]

Fantastic. Let me know if there is anything I can do to help.

For the newb, do you mean one from a newbie player's point of view playing their first game? Or how to install and run FGU? Or both?

Cheers, Hywel

[WishX]

For the newb, do you mean one from a newbie player's point of view playing their first game? Or how to install and run FGU? Or both?

Either! I'm happy to have a look at whatever you feel like putting together. If you like, you can also contact me directly on our Discord server so we don't monopolize this thread: wishx#9236
Thanks!

[Weissrolf]

I keep using FGU for my original Pathfinder 2 group and use Foundry for a second "beginners" group.

- The barrier to entry for players joining in on the fun is a *lot* smaller in Foundry. If everything else fails you can join a Foundry server via smartphone/tablet, even when it is not fully supported. No need to create an account, no need to download and install the software and get it going through your router/provider as player (though still as GM).

- The Pathfinder 2 system incorporated a lot of functionality that originally was only available through modules (extensions). But for many quality of life things I *personally* still want 100+ modules. That being said, I also use 24 active extensions in FGU and would use more if they were not broken since the switch to Unity or supported 5E only.

- With a large group of developers (+project management) working on the PF2 system, there are quick turnaround times for any new product published by Pathfinder publisher Paizo. Furthermore the system is growing quite quickly and with some tremendously great features that easily rival the FG implementation. They had less of a head-start compared to FGU, but they make that up with the sheer enthusiasm and motivation of "I want to play that myself" and maybe getting a bit of community fame. They do not get licensed material from Paizo, which is an advantage and disadvantage.

For end-users this has some ramifications: End-users are only customers of Foundry, but not customers of the PF2E system. As such the PF2E team owes end-users "nothing", not even politeness and some *few* will let you know. That being said, in practice I don't see much of a difference to being a paying SW Pathfinder customer in that regard and the larger team allows end-users to pick those team members for any dealings that they get along with best.

Using Foundry for Pathfinder 2 sure is less expensive than using Fantasy Grounds. Something like the Core Rulebook costs as much in FG as buying a hardcover print ($60 currently), while with Foundry I am happy using my PDF version ($10). Adventures also cost less, because again I only have to pay the PDF from Paizo and then can import that into Foundry via the free PdfToFoundry module. The latter is exclusive to the Pathfinder 2E system, though, so other systems like 5E don't have that advantage.

- Some automation that is available for D&D 5E in Foundry is not available for PF2E, though. For one, because some of the largest modules (Midi QoL) are not available outside of 5E. For another, because the PF2E system developers strictly adhere to Foundry's basic philosophy that only "owners" of characters can apply any changes to them.

The latter means that a player is only able to roll attack against a NPC, but the player is not able to apply damage to the NPC, as the GM is owner of the NPC. The idea is that at the table only the owner of a paper sheet makes changes to said sheet. So the player does a damage roll, but the GM then presses a button to apply the damage (applying whatever modifications necessary on the way). And a player healing another player again only gets to roll the healing result, but the target player has to press a button to apply the rolled healing.

Since the PF2 system on Foundry does not offer resistance automation yet, this approach even is kind of necessary (so the GM/player can apply resistances/weaknesses manually). But once this system is automated I quite strongly disagree with the approach to not solve VTT related problems by VTT related means. One example of this "philosophy" failing is D20 bards' "Inspire Courage" that applies bonuses to their allies. In PF2 the bard sometimes has to reapply that every single round, which means that every single player of a group has to reapply that to their character every single round. This is a VTT produced problem, because you need to tell the computer all modifiers for proper calculation (telling you hit or miss). This is different from the table and as such should be solved by VTT/computer means.

That being said, there are modules that break the philosophy and allow players to apply their results to others. I gave our bard's player a macro that combined with a module applies Inspire Courage to the whole group, so only the bard has to push a button. He also has another button to prolong the duration via "Lingering Composition" roll and then automatically apply that longer duration to the whole group. But, this is fighting against the system/philosophy of Foundry via Javascript "sockets" instead of expanding the system. So it may easily break with future updates.

- Foundry is marketed as "developer-friendly" platform, not as player-friendly! Players are only ever mentioned as being able to connect to "you" via browser and for free, written in third person as some kind of inevitable attachment to developer customers. And for being "developer-friendly" it sure could use more thorough API documentation. The current form is more of a quick reference than a full fledged manual and the assumption seems to be that knowing your way around object oriented programming will lead developers to the correct answers themselves.

Some developers seem to prefer studying the Foundry client source-code instead of relying on the API (docs).

- "Create a module" is something too often read on the Foundry Discord. One reason very likely being that the regulars there all seem to be developers in one another capacity. The advantage of that is that users are dealing with many capable individuals on the Foundry Discord, who know more than to click some buttons. When I created a module for easier token elevation changes it literally got thrown code snippets at me to make it happen. I still had to learn some Javascript, coding tools and Foundry API in about a week, but I was able to find someone holding my hand throughout the process (Git was the worst part of it).

Could I have done the same in Fantasy Grounds? Maybe. Surely not with the ongoing support of ever-online developers easily accessible. And then I would have to learn Lua, which mostly seems only useful for games related stuff, while Javascript is more universally useful to learn and much more modern than the Lua 5.1 engine used in FGU.

And one thing needs to be underlined: Modules can extend/change/improve Foundry to such an extend that there even was a module that fundamentally changed/improved the whole lighting system of Foundry, which then lead to the next Foundry version incorporating much of its design in cooperation with the module's author. Such fundamentally creative solutions are not possible in FGU where end-users have to rely on a rather understaffed Smiteworks to make things happen (or not). When a new major versions breaks module compatibility, though, then only those modules get updated along with it which still have someone to maintain them on a voluntary/self exploitative basis.