Guild Artifact
Artifact for storing guild data
Durable store for all guilds, backed by [AssetManager] (which the MySQL extension transparently redirects to the database when enabled). A single artifact holds every guild keyed by its id. This mirrors the design of the Friend extension's artifact: one bulk blob, a short read-through cache, and full-rewrite persistence on each mutation. Ephemeral state (pending invites) is intentionally not persisted.
Champs
| Champ | Type | Par défaut | Description |
|---|---|---|---|
artifactId | String | btc_guild_data | Unique artifact identifier |
How to use it
Create one Guild Artifact on a static page and publish it. The extension uses the first one it finds. Without it, guilds exist only in memory and are lost at restart.
Guild membership, roles and allies are stored here. The bank balance is stored separately in the database table btc_guild_bank and is the reference when the MySQL extension is enabled. Pending invitations are not saved. With the MySQL bridge enabled the artifact is stored in the shared database.