Alluria Extensions

[Rhydion]

Hi all

I’m going to start slowly releasing some of my Alluria extensions for Fantasy Grounds Unity.

These are extensions I originally built for my own PF1e / FFd20 campaign, but I’ll be releasing them publicly once they reach a standard I’m happy with. I’ll only post extensions here once they have been cleaned up for public use, documented, and packaged properly.

You can find the released extensions here:

https://forge.fantasygrounds.com/cra...2/view-profile

Unless stated otherwise, these extensions are built and tested for the 3.5E / PFRPG ruleset family. Some support tools may be more ruleset-agnostic in design, but I will only claim official compatibility for rulesets I have actually tested.

Current releases will be added below as they become available.

If you find any bugs, errors, unclear documentation, compatibility issues, or anything that could be improved, please feel free to respond in this thread.

When reporting an issue, it helps a lot if you can include:

* the extension name and version;
* your Fantasy Grounds ruleset;
* any other major extensions loaded;
* what you were doing when the issue happened;
* screenshots or console logs, if relevant.

These are unofficial community extensions and are not affiliated with SmiteWorks or Fantasy Grounds. As always, I recommend backing up campaigns before adding or updating extensions.

Thanks, and I hope some of these are useful to other tables.

[Rhydion]

Release dates and last updated notes!

Resource Ledger
https://forge.fantasygrounds.com/shop/items/3414/view - Released 26/06/2026

Last Updated: 26/06/2026

Tablekeeper
https://forge.fantasygrounds.com/shop/items/3415/view - Released 26/06/2026

Last Updated: 29/06/2026
Latest Version: v1.2.8 Public Release
Update Notes: Tablekeeper v1.2.8 Public Release Notes

Damage DR Patch
https://forge.fantasygrounds.com/shop/items/3419/view - Released 26/06/2026
Updated Forge Page as was missing description of important function"(m)" for weapon properties.
Last Updated: 26/06/2026

[dllewell]

New PF1E extensions. Exciting. Can't wait.

[Rhydion]

New PF1E extensions. Exciting. Can't wait.

Hopefully they will see some use. I have two extensions public ready as well as a support extension but its more for extention authors more than anything.

I'll keep working to get more public ready.

Currently waiting for approval on the 3 of them now

[Rhydion]

First Wave Extensions Released! MWAHAHAHAHA

[Rhydion]

Tablekeeper v1.2.8 Public Release Update

Tablekeeper has been updated to v1.2.8 Public Release.

This update is mostly a foundation and stability update for other Alluria extensions. Tablekeeper is intended to act as a shared campaign storage helper, allowing Alluria extensions to safely store settings, presets, notes, records, and other table-owned data without each extension needing to invent its own save system.


What Changed

Tablekeeper now supports namespace-based storage.

• Each extension or feature can store its own data under its own namespace.
• Namespace files are stored inside the campaign’s "Alluria_Tablekeeper" folder.
• The older single-file settings approach is still supported for compatibility, but the newer namespace approach is cleaner and better for future extensions.
• Existing Tablekeeper consumers should continue working through the existing API.
• A new warning window appears if the required `Alluria_Tablekeeper` folder is missing.
• The warning window can open the campaign folder, copy the folder name, and recheck whether the folder is ready.

Required Campaign Folder

Tablekeeper now expects this folder inside the current campaign folder:

"Alluria_Tablekeeper"

Fantasy Grounds extensions cannot reliably create subfolders automatically, so this folder will need to be created manually once per campaign.

If Tablekeeper cannot find or write to the folder, it will show a warning window with three buttons:

• Open Folder Location — opens the campaign folder.
• Recheck for Folder — checks again after you create the folder.
• Copy to Clipboard — copies "Alluria_Tablekeeper" to the clipboard for you.

Once the folder is found, the status message will show:

"Storage Folder found! Storage is ready. You may close this window."

For most users, this should be a one-time setup step.


API Updates

The main reason for this update is to make Tablekeeper more useful as a shared storage layer for other Alluria extensions.

Extensions can now register and use their own storage namespace. For example, future extensions can store their data separately without crowding one giant settings file.

Newer API support includes:

• Namespace registration
  Extensions can register a namespace such as `resourceledger`, `hct`, or `masteratarms`.
  
• Campaign documents
  Useful for plain text or longer editable content.
  
• Opaque campaign strings
  Useful when an extension wants to store its own encoded data without Tablekeeper needing to understand the format.
  
• Campaign records and collections
  Useful for structured data such as presets, saved entries, briefing records, or extension-owned campaign data.

The intended idea is:

Extension → Tablekeeper API → namespace storage file

This means other extensions do not need to know exactly where the data is stored. They ask Tablekeeper to save or load values, and Tablekeeper handles the file location, namespace routing, backup behaviour, and compatibility path.


Why This Matters

This update prepares Tablekeeper for larger Alluria systems that need reliable campaign-owned data, including future tools and other table-side features.

The goal is to avoid editing Fantasy Grounds module source records directly when the data really belongs to the current table or campaign.


TLDR:

• module records stay as source/reference data;
• campaign data stays campaign-owned;
• Alluria extensions can share one storage broker;
• each extension keeps its data cleanly separated by namespace.

Instructions and APIs are included in the documentation inside the extension file.

This is not a flashy combat feature update, but it is an important infrastructure release for future Alluria extension work and for creators who need a similar solution, or wish to avoid DB clutter or possible corruption as we have seen in the last massive update. Hopefully