I'm getting script errors for "hpbar" and "hdbar" strings opening the party sheet on 5e ruleset in v3.3.9. Anyone else?
Printable View
I'm getting script errors for "hpbar" and "hdbar" strings opening the party sheet on 5e ruleset in v3.3.9. Anyone else?
Me too and let the dev know (my GM).
Thanks for the report, I'll take a look at this tomorrow.
Extension updated to work with FG 3.3.9 changes to party sheet and the link in the first post updated to point to release 02.00.00 version. Note this version works with *both* the 4E and 5E D&D rulesets. So the load text changed to note that and the name of the extension is now just AltWoundColors instead of 5E AltWoundColors.
Got the new .xml in & old removed but it doesn't seem to be showing up as an available extension when loading my campaign...hopefully I'm not being a moron. I've reloaded, restarted and triple-checked my available extensions list. Yes, I did see the name change note.
Did you zip the folder when you rezipped it? That won't work. Only sip the contents of the folder and then rename to an extension.
No.... Extensions either need to be zipped and renamed to .ext file extension, or a folder needs to be created that the .xml goes in, along with anything else the extension needs to work (such as images, lua files, etc).
If you look at post 1 of this thread, you see that a .ext file is linked. I don't know what's in it as I haven't downloaded and looked, but I assume any changes you made to it would need to be similarly packaged.
More details here; https://www.fantasygrounds.com/wiki/...Files_Overview
The extension in the first post isnt packaged correctly. The zip file contains the parent folder, so FG will not recognize it as a valid extension. I've attached the same extension fixed without the parent folder. So if you download this ext file, restart FG, it should now be available to be selected.
EDIT* OP post was fixed. Removed my attachment
Sorry guys I was busy and missed the packaging problem. I've updated the first post with it packaged correctly now. Thanks for posting a fix, mattekure :)