Tablekeeper v1.2.8 Public Release Update
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 :D
