EN Feature Packs

Messaging, social and gaming feature packs

English · Türkçe · Languages / Diller

Scope: JSON API Forge 0.5.1 · Source review: 17 September 2026 · Language: English

Feature packs expand reusable domain models into ordinary Forge resource definitions. They are not independently running microservices or complete application interfaces.

{
  "features": {
    "messaging": {"enabled": true, "database": "primary", "table_prefix": "msg_"},
    "social": {"enabled": true, "database": "primary", "table_prefix": "social_"},
    "gaming": {"enabled": true, "database": "primary", "table_prefix": "game_"}
  }
}

Each pack supports enabled, database, table_prefix and optional tenant_field. Inspect expanded tables/resources through forge routes, schemas and the pack implementation. Avoid path/table conflicts between packs and custom resources.

After enabling a pack:

1. Run forge validate and forge doctor.
2. Grant the generated permissions with minimum necessary scope.
3. Prepare production migrations and indexes.
4. Test at least two tenants if tenancy is enabled.
5. Design domain rules such as chat delivery guarantees, anti-cheat, moderation, payments and game-economy invariants separately.

Successful expansion is not proof that domain rules are complete. For durable messaging, read realtime limits. For controlled economies, combine RPC with the GuildLedger example.

Sources and verification

This page describes the behavior at the pinned commits below. Recheck these contracts when upgrading.

• main/framework/domain/packs.py
• main/framework/config.py
• main/docs/06-Messaging-Social-Gaming.md

---

English home · All English pages · Version maintenance