Comments on: Official Foundry Hub Recommended Module List

By: DMGuild2017

DMGuild2017 — Fri, 27 Aug 2021 16:41:26 +0000

In reply to zzzz. The Forge does something like this. I'd suggest checking it out.

By: zzzz

zzzz — Fri, 20 Aug 2021 01:54:24 +0000

Hope there will be a Add-on Modules Shop.Like chrome web store, people can vote and give comment

By: kenpoh

kenpoh — Thu, 15 Apr 2021 16:19:26 +0000

That being said, here’s my list: https://youtu.be/FUQSwq2ul5w

By: Sir Raiu Koren

Sir Raiu Koren — Sun, 04 Apr 2021 12:38:00 +0000

You’re right, this is indeed a clickbait title with a flippant answer. Since it is my first introduction to Foundry Hub, I will now advise my players to stay away from here if they want useful information.

By: Mushie

Mushie — Mon, 22 Feb 2021 05:00:00 +0000

My comment above is actually about to become more relevant as we are about to see an influx of people from Roll20 as they have announced the removal of the Legacy lighting, which is pushing alot of people to Foundry.
I think a “Here is an example of modules that will make your transition from Roll20 to Foundry smoother for your players”

By: Sébastien

Sébastien — Thu, 18 Feb 2021 14:50:48 +0000

In reply to mjmcmahon67. I completely agree with you here. I know that if we point what we think are the best, peoples may miss something that could have been great because they didn't search, but it's at least a point to start. That way, if you are astonished by this "best" list, you will likely give more chance or more time to get accustomed by Foundry.

By: TJ

TJ — Wed, 17 Feb 2021 20:38:25 +0000

In reply to Mushie.

I’m not sure how anybody can realistically think that’s anything unique to Foundry. Roll20 has a scripted macro engine. Fantasy Grounds has scripted effects. Foundry is plenty functional without them, but so are R20 or FG.

…they’re just better if you’re willing to learn a little coding. Foundry has the added benefit that JS is useful in other ways that just for the VTT.

By: Mushie

Mushie — Tue, 16 Feb 2021 03:08:52 +0000

In reply to mjmcmahon67. My previous comment was in reply to mjmcmahon67. (sorry no way to edit the comments)

By: Mushie

Mushie — Tue, 16 Feb 2021 03:01:00 +0000

In reply to mjmcmahon67.

I agree with you. One of the concerns I see in a bunch of forums for people thinking of moving to Foundry is that “you need to be a programmer to use it”, and this includes references to macros as well.
I did install a bunch of modules, because coming from another VTT my players and I were used to doing things and they were not possible in the core product. But I had to sift through multiple forums (Discord, Reddit and FB) over many weeks to get the answers.
(and it gets worse when you start to look into the macros)

My thoughts for the Foundry Hub was that it was going to have nice documentation and some recommendations for new comers – somewhere where we could point people to who dont like the discord format.
I realize it is new, but at the moment the module recommendation is to go to lots of other places to search for stuff and the macro recommendation is to goto github which is set up for programmers and is very daunting and doesnt really tell you anything about how to write a macro, or key components of it- so what is currently the point of the hub?? Is it just for “how to use core”?

By: mjmcmahon67

mjmcmahon67 — Fri, 12 Feb 2021 03:41:52 +0000

Here’s where I’m likely to stand apart from the crowd: I DO NOT agree that providing a list of recommended modules, particularly if they’re curated for a particular game system, is “bad”. I only started working with Foundry towards the end of 2020 and needed SOME PLACE to start in order to provide functionality I considered a requirement in order to make the platform usable – I needed a reliable method by which I could import characters, monsters, and game content. I needed things like the ability to have my players’ tokens transport from points on one scene to another. I wasn’t needing Foundry to do ALL the work, but some functionality within the ruleset to allow the DM to DM and not spend all their time looking up spell effects and manually importing monsters IS (in my opinion) a pre-requisite. Unfortunately, I’m increasingly finding this attitude among some players and developers using Foundry that “you have to start with the basics”. While I understand part of what they’re saying – that the coding used can be complex and understanding what modules interact with each other is helpful with troubleshooting – I do find the “you have to start with just the basics before you’re allowed to use the modules that will help you do what you want” to have the scent of elitism…especially when you’ve reached out to someone for help and had the audacity to misunderstand which module might have been to blame.

Unfortunately, this seems to be a common drawback with community developed products – there seems to be this sense that you must be a coder in order to use the product. Respectfully, that’s not what we (the consumers) paid for. Yes, I understood going in the community development was going to mean that one module may not be compatible with another and that developers that do this work on their own time cannot be expected to crank out bug fixes on the same schedule as someone that’s doing the development full time. I hope that, in time, Foundry may recognize that their competitors are offering a certain level of functionality out of the box and that, if they want to remain competitive in the marketplace, providing a “known compatible” list for the more popular game system helps them to do that.

My two cents…