3E D&D / Pathfinder - Community Extensions

The Encounters Extension appears to be incompatible with 3.2.0.

It loads fine, but it does cause errors and strange behavior when editing encounters in 3.5e

Quote:

---

Originally Posted by Jwguy

The Encounters Extension appears to be incompatible with 3.2.0.

It loads fine, but it does cause errors and strange behavior when editing encounters in 3.5e

---

Please report in the actual extension thread so the dev and anyone reading the thread is aware of it: https://www.fantasygrounds.com/forum...or-(Extension) Thanks.

Hi Everyone,

I've placed new FGv3.2.1-compatable versions of all of the DOEs in their respective Threads.

The first post in this thread has also been updated

Enjoy!

Cheers

Quote:

---

Originally Posted by graphil

3.5E and PFRPG ruleset version update: FG 3.2.1 has been pushed via the FG update mechanism.

There are some changes to the 3.5E/PFRPG rulesets in this update, so some of the following extensions will need updating to work with FG 3.2.1.

Note: With the release of FG 3.0 some of these extensions might not work properly or be visible for selection in PFRPG campaigns - please comment in the specific extension thread if you experience issues.

Some generic FG 3.0 extensions that can be used with 3.5e and Pathfinder are available here: https://www.fantasygrounds.com/forum...RPG-Extensions

These are the ones I have so far.

• Player Effect Removal Allows players to remove effects that have applied Update to v1.1.4 required for FG v3.2.0 compatibility.
• ....
• Pathfinder Statblock import (in game) Update for FG v3.2.0 compatibility.
• ....

....

---

A couple of questions on the comments:
On the first one, that means you have to update to the indicated version for it to work.
On the second one, does that mean it is incompatible until someone updates the extension?

Quote:

---

Originally Posted by Bidmaron

On the first one, that means you have to update to the indicated version for it to work.

---

For the extension to have full compatibility, you have to update to the version specific to the most recent version of Fantasy Grounds. Older extensions may *appear* to work on the surface, but may not be using the most recent FG code and so may be breaking new features or causing strange behaviour.

Quote:

---

Originally Posted by Bidmaron

On the second one, does that mean it is incompatible until someone updates the extension?

---

Assume extensions are incompatible until reviewed and either updated or indicated as compatible. See my previous comment.

See the "Extensions" section here: https://www.fantasygrounds.com/forum...ipt-errors-etc

On the Statblock Import, the specific extension thread shows that it has been updated for 3.2 compatibility. I guess the reason the syntax used there is goofy compared to the other extensions is because the extension author in this case has not provided the extension as a download, so if you go the GitHub site to download, you get the most compatible version, and he doesn't track versions very well on his thread.

Quote:

---

Originally Posted by Bidmaron

On the Statblock Import, the specific extension thread shows that it has been updated for 3.2 compatibility. I guess the reason the syntax used there is goofy compared to the other extensions is because the extension author in this case has not provided the extension as a download, so if you go the GitHub site to download, you get the most compatible version, and he doesn't track versions very well on his thread.

---

Yep, if developers don't use the "standard" that most community developers use then there will always be issues keeping on top of information/getting the right version. If you need more info on a specific extension then you should always check the individual extension thread. It takes a lot of work to monitor many extension threads and update the main extension index - so go to the "horses mouth" for specific questions and up-to-date extension information.

Hi Everyone,

I've placed new FGv3.2.2-compatable versions of all of the DOEs in their respective Threads.

The first post in this thread has also been updated

Enjoy!

Cheers

Quote:

---

Originally Posted by Trenloe

Yep, if developers don't use the "standard" that most community developers use then there will always be issues keeping on top of information/getting the right version. If you need more info on a specific extension then you should always check the individual extension thread. It takes a lot of work to monitor many extension threads and update the main extension index - so go to the "horses mouth" for specific questions and up-to-date extension information.

---

There is no standard if I recall outside what a loose collection of authors decided to use with several variations. I use Github, and the 'traditional' method is through forum posts with a download attached.

I'm not submitting to NPM or a package manager of any kind, This is simply some fast and loose lua I wrote while squeezing my stress ball between other endeavors. I find the title that you mentioned, 'community developer' to be an odd honorific that assumes that everyone who shared an extension freely is suddenly bound as a crowd sourced 'developer' and must adhere to an 'expected' protocol or become a pariah. I'd consider yourself a 'community developer' as you're more vested, I however am only a fan of good software should it remain so; but I will always advocate and defend FOSS.

Suffice to say that it works on 3.2 if you wish to update that main posting or not. The versioning I use is directly related to the version of the extension itself as opposed to the version of Fantasy Grounds.

What's the signification of " DOE " ?!?