Log in

View Full Version : My extension isn't working



Aracnan
November 19th, 2025, 08:39
Hello everybody, and first, i'm sorry for my bad English.

I use Fantasy Grounds Steam version, Windows 11. I used Core RPG rules, as it will be another new system - mine exactly. Maybe that's the problem ^ ^"

I tried to make a character sheet for my own system, rather complicated. Not sure if it even works because FG don't load it properly it seems. Extension is shown on the extension list, ok, but only in "all", character sheet is still the default one, everything is like FG just ignore my extension. And well, i am not good at programming, so maybe i do something wrong. I tried to check .xml for errors, i tried clearing cache, Steam cache, run as administator, remove "read only" on files, reinstall, even asked Gemini and Claude for help, to no avail. Woe upon me. I tried to contact the support, but they just told me to ask in the forum. So i am here.

I will be very grateful for any help or advice.

Nylanfs
November 19th, 2025, 13:08
Welcome to the forums and FG Community!

Note: The Steam and the version you get here are the same. Steam is just a wrapper for the main program. You can run FG directly without steam, and there might be a performance boost by not having the steam overlay on.

You may want to take a look at these rulesets Morecore (https://www.fantasygrounds.com/forums/showthread.php?34860-MoreCore-Ruleset) and XCore (https://www.fantasygrounds.com/forums/showthread.php?76360-Introducing-the-new-XCore-Ruleset). They are both explicitly created to support game systems that aren't developed yet.

Trenloe
November 19th, 2025, 13:51
Weclome to the forums @Aracnan!

For coding, your first step should be looking at other examples - start with the CoreRPG ruleset, or similar extensions.

This is your code, which isn't an valid way of loading charsheet.xml:

<base>
<sheetdata name="charsheet" file="charsheet.xml" />
</base>

This is how to load charsheet.xml:

<base>
<includefile source="charsheet.xml" />
</base>

But, as @Nylanfs mentions - you may want to look at rulesets like MoreCore or XCore that allow creating of custom character sheet data - it won't allow you to make the layout exactly what you're looking for, but it may save you hours of coding to get a working character sheet.

LordEntrails
November 19th, 2025, 14:24
MOD: Moved to the Workshop sub-forum.

Other thing to note, though AI can help write portions of FG extensions, it doesn't work to fully create extensions. It will make basic errors in formatting and calls that just won't work.
The advice to alter or reference an existing extension is excellent. As well, you can look into www.rulesetwizard.com as a tool to help as well.

jharp
November 20th, 2025, 02:21
Rulesetwizard is the way to go.

Jason

Moon Wizard
November 21st, 2025, 01:14
I actually disagree, though I am biased.

The templating for the CoreRPG layer has gotten much better since RSW was released. You can see how much simpler many of the windows are to customize in the various built-in rulesets; and this bypasses the need for RSW.

Regards,
JPG

LordEntrails
November 21st, 2025, 01:37
The work you all have done on the templates is awesome, but one reason I keep using RSW is for the visualization. I imagine you and some others can visual the windows just by reading the code, but I can't. the GUI RSW presents if invaluable for me. But, maybe with some more coding experience I'll get closer to what you can do :)

Moon Wizard
November 21st, 2025, 05:37
The problem is that using RSW for the visualization unwinds all the templating; so you lose the ability to inherit the changes from CoreRPG to keep things standardized.
While I understand the visualization piece, it's a double-edged sword.

JPG

LordEntrails
November 22nd, 2025, 15:02
Agreed. Though if I understand, there are ways to use RSW without overwriting or unwinding the templates. I'm not sure about that as I'm not proficient with either, but it does have ways to reference templates instead of brute force copying and replacing (like was the original approach). When I get to a more stable feature level on my ruleset I'll be going back and looking more into this.