#What do you look for in a 2d20 system implementation on Foundry?

1 messages · Page 1 of 1 (latest)

magic schooner
#

I’m by no means committing to anything, but given the variety of systems for various 2d20 games implemented for Foundry I thought it might be nice to gather some feedback.

Putting aside things that simply aren’t an option due to licensing issues like including compendiums…

What things do you like and dislike about current Foundry implementations for 2d20 System games?

What things (again, excluding compendiums) don’t exist that you would like to see implemented?

What things do exist that you wish were done in another way?

Any other feedback you’d like to give for folks considering implementing other systems? Any particular systems you’d like to see get some love?

icy egret
#

For 2d20 in particular, having a modular system is important to me.

Also, a good ui. But that's kinda unrelated.

magic schooner
#

Can you be more specific about what you mean by modular?

icy egret
#

Think about the bits that are unique to Conan vs. A!C for example. Like the way magic is handled. Being able to pick and choose the various sub-components is what I mean. It's hard to explain, cuz I'm not ultra familiar with the other systems, but once all the building blocks are in, and able to mix and match, then building an individual system goes away, and it becomes a matter of picking the right options and creating a compendium.

Apologies if I'm terrible at explaining this.

magic schooner
#

It’s alright, explaining things is Hard. Are you saying you’d basically like a general-purpose 2d20 system implementation that could theoretically run any of the 2d20 system games?

#

Unfortunately I’m not really sure how viable a general-purpose system might be because there are a bunch of incompatible overlapping bits between the games that would make sheets a nightmare to build & maintain; different treatments of vehicles, magic mechanics, talents & skills, etc. It’d be a bit of a nightmare to work on, and wouldn’t turn out as nice as a bespoke system for a specific 2d20 game

icy egret
#

That's a valid point, too. But yes, a generic base is what I was getting at, somewhere in the vein if swade or mythras. But I guess they don't change many core mechanics.

icy egret
#

Might also be partly selfishness of trying to build hard sci-fi for my own system off the A!C base. Lol.

heavy wind
#

A!C was specifically built for me to try it with my party. So not much thought was given about modularity honestly

#

Now that it is coming officially to roll20 as it seems I am thinking about validity of expanding it with more features

tribal bane
#

I was quite pleased with the most recent update to the Star Trek system, which finally fixed the HTML template used for item rolls such that they now post item IDs in the chat

#

So really the ability for the system to play nice with some of the more common modules out there

#

If there's a common way of doing things on the platform and it's feasible to do them with the ruleset in question, that's the way to go

icy egret
magic schooner
#

I only ever end up specifically targeting three modules; Dice So Nice, Player Pronouns, and Chat Portrait, since those are the ones I use in play. Short of having things that have a "common way of doing things on the platform" (more specifically, those that are actually relevant to common modules) actually being documented, I'm personally more likely to end up going my own direction and then fixing things when people pop into the issue tracker asking for compatibility with some specific module.

#

In my experience with Genesys so far, there're too many random modules that want things to be done in a very specific way in order to maintain compatibility for me to try to catch them ahead of time. 🙃

icy egret
#

Actually, a couple things that would be nice are active effects on talents, or some sort of "Hey, this talent applies to the skill you're about to use" type notification, and a "party" character sheet for moving about on the world and tracking shared items/resources/etc.

magic schooner
#

ActiveEffects and listing possibly applicable talents are both things I definitely have in mind for Infinity

#

Identifying relevant talents is easier for Infinity since Infinity talents are all directly tied to a skill. <.<

warm widget
#

I would recommend checking with modiphius on the inclusion of anything like talents into the core functionality of the system. There is a reason conan doesn't do it 😦

#

(which incidentally - theres a modiphius rep in the 2d20 foundry dev discord instance and if you'd like to join I'd be happy to intro you!)

magic schooner
#

? I don't think anyone's said anything about including talent content (in fact my original post when I created the thread specifically asked not to bring up the subject of including/distributing data in compendiums). I think the talk was more about making sure talents have support for setting up ActiveEffects

#

But I wouldn't mind an invite to the that Discord.