iDos Games

Get the @idosgames runtime npm packages and their exact versions (core, wallet, module-sdk, react, app-shell). Install these so the base and the modules resolve their imports. Read-only; takes no title_id.

GET ONLY the 'Marketplace' field of TitlePublicConfigurationModel. Player-to-player marketplace (v2) — fixed-price listings (price = ResourceBundle), auctions (single-axis bids), buy orders (escrowed payment), and direct trades/gifts. Configures the audience gate, open-window schedule, price composition policy (reusing the same EntryResourceRule whitelist as Match), commission policy (percent/min, burn or ledger sink, per-goods-catalog overrides), item tradability lists, and per-mechanic settings/limits. Distinct from Store (title-sold SKUs) and DealOffer (promotions): here players trade with each other. Everything offered is escrowed at creation; commission is taken at settlement.

GET ONLY the 'Match' field of TitlePublicConfigurationModel. PvP / match system configuration, grouped by battle mode under InstantBattle. Holds the instant-battle rule catalogue (keyed by RuleID) plus title-wide defaults. Each rule defines wager economy (prize-pool burn) and battle settings: a combat-role → StatID mapping (which Character stat drives HP/Damage/Armor/AttackSpeed/CritChance/CritDamage/Dodge/AllMight), combat params (max rounds, block effect, crit/dodge clamps) and optional per-stat custom formulas. Stat/formula fields reference Character.Stats StatIDs; equipment bonuses (Item) key off the same StatIDs.

Get one module's source (files) plus install instructions: write each file under src/modules/{id}/, install its dependencies, and register it in src/modules.ts. The project needs the base first (get_host_scaffold). Large modules come in PAGES: the answer has nextCursor while files remain — call again with the same id and cursor=nextCursor until nextCursor is absent. Read-only; takes no title_id.

GET ONLY the 'Multiplayer' field of TitlePublicConfigurationModel. Realtime multiplayer (WebRTC peer-to-peer) - the engine is only the signaling server: it creates rooms, relays WebRTC offer/answer/ICE between room members and optionally relays lobby chat; game traffic then flows directly between players' browsers and never touches the server. The section is ABSENT by default, which means multiplayer is DISABLED: add it (SystemState.Enabled = true) to turn the Multiplayer module on. DefaultTopology: Mesh (everyone connects to everyone, 2-4 players) or Host (star: every player connects to the host, which runs the authoritative game simulation - required by host-authoritative games such as VoxelCraft). MaxPlayersPerRoom is a hard cap (default 8). MemberTimeoutMs is also how long a silent host keeps the host role before another member may take it over. IceServers are PUBLIC: list only STUN servers there; short-lived TURN credentials are issued by the engine to room members on create/join.

Cards assigned to a person across all boards, soonest deadline first. Defaults to the publisher who owns this connection — pass assignee_id for a teammate.

GET ONLY the 'PlatformBridge' field of TitlePublicConfigurationModel. Platform bridge - what the game takes from the player's idosgames.com account and what it lets players show on their public profile. Profile: Off / Default (unset: the platform name and avatar until the player renames themselves in the game) / Always (every platform login overwrites them). Friends: TitleOnly (unset) / TitleAndPlatform (plus mutual follows on idosgames.com whose both sides play this game) / PlatformOnly (only those; in-game friend requests are refused) - applies to EVERY friends-based system: friends list and leaderboard, gifts, attack targets, friends-only Workshop items, recommendations. Notifications: which in-game notifications (Attack, Raid, FriendAdded, WorkshopSale) also reach the idosgames.com notification bell; empty = none. Guests never get platform data; the economy never crosses the bridge; turning the bridge off deletes nothing.

GET ONLY the 'Premium' field of TitlePublicConfigurationModel. Premium offerings catalogue — paid subscriptions, premium passes, real-money bundle skus, supporter tiers. Distinct from Store (regular in-game shop with virtual-currency prices) and from DealOffer (limited-time promotional offers). Use this specifically for monetization tiers / IAP that grant ongoing benefits.

GET ONLY the 'Purchase' field of TitlePublicConfigurationModel. Real-money in-app purchases (IAP) for Google Play and the Apple App Store. Product catalogue with per-store SKUs (StoreProductIDs), what each purchase grants (Rewards), subscription products that activate a Premium entitlement, audience gates and purchase limits, plus per-store receipt-verification settings. Distinct from Store (in-game shop paid with virtual currency) and from Premium (which describes the entitlement itself, while this describes how it is sold in the stores). Contains NO secrets: the Google service-account JSON and the App Store Server API key are referenced by TitleSecrets entry name only; the Play licensing public key and Apple root certificates are public by nature and live here.

GET ONLY the 'Push' field of TitlePublicConfigurationModel. Push notifications - the title's settings for messages delivered to a player who is NOT in the game right now (Web Push in the browser, FCM/APNs on mobile). IsEnabled is the master switch and defaults to DISABLED: notifications spend a real person's attention and require their browser permission, so a title opts in explicitly. MaxSendsPerUserPerDay caps how many a single player receives; MaxSendsPerTitlePerDay caps the title as a whole and is the ONLY ceiling on a broadcast that exists anywhere - the publisher API quota does not see sends at all, because they run in a queue worker rather than in a request pipeline. QuietHoursStart/End suppress sends during the night in the SUBSCRIPTION's locale (the window may cross midnight); waking a person at 3am is the fastest way to lose the browser permission permanently. Mobile holds only the NAMES of TitleSecrets entries for the publisher's Firebase service account and APNs .p8 key, never the credentials. VAPID keys are NOT here and never will be - they are platform-wide environment variables shared by both backends. Subscriptions themselves are not config either: they live in the shared PushEndpoints/PushBindings collections, one row per browser or device plus one row per topic it follows.

GET ONLY the 'Quest' field of TitlePublicConfigurationModel. Quest / mission / objective definitions — single tasks the player completes for a reward. Includes trigger conditions, progress counters, completion criteria, reward references (use Reward). For grouped quest chains use Season or TimedEvent.

GET ONLY the 'Referral' field of TitlePublicConfigurationModel. Referral / invite system configuration — invite codes, attribution rules, milestones (e.g. invite N friends → reward), per-side rewards (inviter + invitee). Reward bundles reference Reward.

GET ONLY the 'Reward' field of TitlePublicConfigurationModel. Reward templates — reusable bundles of currency + items + buffs that can be granted to a player. Referenced by Quest, TimedEvent, CoopEvent, Season, DailyLogin, Referral, etc. Define a reward once here, then reference it everywhere instead of inlining payouts.

GET ONLY the 'Season' field of TitlePublicConfigurationModel. Long-form seasonal progression — battle passes, chapters, ladders. Defines a season's start/end window, XP/progress curve, tier rewards (free + premium tracks), and the Premium pass that unlocks paid rewards. For short events use TimedEvent.

Get one SDK skill's full content (SKILL.md) and its reference files. Read-only; takes no title_id.

GET ONLY the 'Social' field of TitlePublicConfigurationModel. In-game social layer - comments, following other players and reports, on top of the engine's shared social core (the same collections the platform's own social network uses, scoped to this title). Comments are OFF by default (CommentsEnabled): they are public text written by players, so turn them on only once you are ready to moderate them; CommentableTypes limits which objects accept comments (today only Workshop items). CommentMaxLength / CommentMaxLinks / CommentsPerDay, MaxFollowing / FollowsPerDay and ReportsPerDay are anti-spam ceilings; unset fields mean the platform defaults. Friends and the player's notification inbox (attacks, raids, new friend, Workshop sales and likes) need no configuration and are not here. Likes, favorites, follows, comments and reports themselves are NOT here - they are operational data in the shared Social* collections; reviewing reports and hiding comments are admin actions, not config.

GET ONLY the 'Store' field of TitlePublicConfigurationModel. In-game shop, built as a tree: Stores -> Layout.Sections -> Slots, plus a flat StoreOffers catalogue. A SLOT is the only address a product can be bought through, and it decides what stands in it: Rotation.Mode is Fixed (a pinned product - an ordinary shelf), Title (everyone sees the same roll) or Player (a personal roll), with a weighted Pool and an optional per-window purchase cap. The refresh window is a ScheduleSpec on the slot. A product not placed in any slot cannot be bought at all. Price is always a PriceOptions dictionary and can be virtual currency, crypto, a store product (real money), an ad credit, or FREE - an unset Cost means free, and a free product must be limited on some axis. Pricing.CompareAt is a struck-through price for display only and never reaches the charge. Identity.Tags and Identity.CustomParams are badges and ribbons the server never interprets. Distinct from Premium (real-money tiered offers) and DealOffer (limited-time promotions with progression).

Poll a 3D job by id. When it is done the model CDN URL is in Assets.

GET ONLY the 'TimedBoost' field of TitlePublicConfigurationModel. Buff / boost definitions with a time component — temporary XP multipliers, drop-rate boosts, energy-cap boosts. Granted via Reward, Store, DealOffer, or events. Define the buff's effect and duration here; granting is done elsewhere.

GET ONLY the 'TimedEvent' field of TitlePublicConfigurationModel. Solo time-limited events — daily challenges, weekly missions, holiday events, login streaks. Defines event IDs, schedules (start/end/recurrence), objectives, progress tracking, milestone rewards. For multi-player team events use CoopEvent; for long-form battle-pass-style progression use Season.

GET ONLY the 'TitleCustomData' field of TitlePublicConfigurationModel. SCHEMA + limits for the title-wide key-value store (feature flags, project-wide globals, event state, balancing knobs that don't fit any typed definition below). This section holds ONLY the key schema — the VALUES live in the TitleCustomData store, one document per title, managed with the dedicated title-data tools (get_title_data / save_title_data). Each key declares a Scope (Static = authored config; Runtime = mutable state written only by CloudCode scripts) and a Bucket (Public = readable by game clients; Private = server/CloudCode only).

Read the TITLE's key-value data store — values shared by ALL players (event state, global counters, server-side thresholds, feature toggles). Returns two scopes: "Static" (authored configuration, written with save_title_data) and "Runtime" (live state that only CloudCode scripts write), each split into "Public" (readable by game clients) and "Private" (server/CloudCode only). Values are always strings. Per-player data is NOT here — it lives in each player's UserCustomData.

GET ONLY the 'Tutorial' field of TitlePublicConfigurationModel. Tutorial / onboarding definitions — flows (ordered scenarios) built from steps that teach the player a mechanic. A step completes either by client acknowledgement or by a real game event (the same TriggerSource vocabulary as Quest), so "make a roll", "buy something", "open a chest" need no client-side bookkeeping. A step may also PREDETERMINE the outcome of another module (TutorialScriptedOutcome — e.g. force the board dice to land on a Raid tile), which is the only way to demonstrate a mechanic instead of randomness. Flows carry an audience gate (SegmentGate) and a schedule (ScheduleSpec); putting an Experiment condition in that gate is how two tutorial versions are A/B-tested. Gating other content on tutorial progress is done via SegmentGate.Tutorial per entity, or via Settings.Blocking to close whole modules until onboarding is finished.

GET ONLY the 'Usage' field of TitlePublicConfigurationModel. Retention policy for the player's activity history (Usage). The engine keeps a rolling window of per-day records and folds everything older into monthly totals, then months of finished years into yearly totals — otherwise the per-day map grows forever inside the hottest document on the platform. WARNING: the fold is IRREVERSIBLE, per-day detail outside the window is gone for good. Do not lower DailyWindowDays below 400 without also lowering the analytics range cap: publisher analytics (DAU/WAU/MAU, retention cohorts, funnels) is computed lazily from those very per-day records, accepts ranges of up to 366 days, and needs 30 extra preceding days per requested day for MAU. Also holds SessionIdleTimeoutMinutes: how many minutes of silence end a session (default 30, the same rule Firebase/GA4 use, so the two reports stay comparable). The session boundary is decided by the SERVER from the player's last activity — the client's IsNewSession flag is not trusted for counting. Leave every field null unless you have a specific reason — the defaults (enabled, 400-day window, 30-minute session gap) are what the analytics horizon was sized against.

GET ONLY the 'UserCustomData' field of TitlePublicConfigurationModel. Schema for per-player custom data fields — name, type, default value, visibility, whether the client can write it. This is the SCHEMA only; actual per-user values live on the User document. Use this to declare new player-specific stats, flags, or progress counters.

Poll a video job by id. While it runs the status says so; when it is done the CDN URL is in Assets.

GET ONLY the 'Workshop' field of TitlePublicConfigurationModel. Workshop - the catalog of content made by PLAYERS (maps, levels, skins, models, any file the game defines) and by the publisher (official content), and the LICENSES to it. Nothing is transferred: acquiring grants a license to a digital copy, so one publication is acquired by many and the author keeps it (unlike Marketplace, which escrows and moves goods). ContentTypes is the game-specific part: each type id (e.g. 'voxelcraft.world') declares its file roles (AllowedMimeTypes, MaxBytes, MaxCount, Required; the engine checks the uploaded file's signature against the declared type), whether a thumbnail is required, which AccessModes authors may use, an optional per-type PricePolicy, a PublishGate (SegmentGate: who may publish), PublishFeeOptions (PriceOption, Standard part only, never store-paid), a TagVocabulary and per-player limits. An author gives access by ANY of several options: Free, Price (a ResourceBundle validated by PricePolicy; the buyer pays, the author receives it minus Commission, which is burned or credited to the MarketplaceLedger) or Holding (hold N of a currency/item - nothing is charged; Mode WhileHeld re-checks on every download, UnlockOnce checks once and grants a permanent license; HoldingPolicy whitelists usable resources). Moderation: BlockedTerms for titles/descriptions/tags, AutoHideReportThreshold (reports that hide a publication until reviewed), RequireApproval (pre-moderation). Featured lists publisher-curated collections with their own ScheduleSpec and SegmentGate. Publications, licenses, reactions and reports are NOT here - they are operational data in their own collections; files live in a private bucket configured by the engine's WORKSHOP_BUCKET_NAME env var.

List the quality/price tiers available on this publisher's plan for every kind of media, and — for each tier — the settings its model accepts: field keys, allowed values, defaults and what they do. That list is the reference for the `params` argument of the generate_* tools. Read-only and free.

Recent versions of the Title's game, newest first — uploaded ones and ones built by the AI Coder — with which one players get now.

Who can be assigned a card, watch it or be mentioned: the publisher and the teammates with kanban access. Returns ids and emails — use the id for set_kanban_assignee.

List the publisher's task boards (projects) with their names and progress. Start here: every other kanban tool needs a project_id.

List the composable iDos Games game modules in the catalog — the same registry the local @idosgames/mcp server serves. Each entry has id, name, type (template = a complete ready-to-run game to start FROM, e.g. voxelcraft; feature = a system to add on top, e.g. store, quests, leaderboard), engine, genre, a short summary, what it 'provides' (its features), tags, preview media, a live demo url, 'inBase' (installed with the base in every new project), 'uses' (modules a game needs) and 'events' (topics it emits and listens to). Read 'provides' to reuse a ready module instead of building the feature from scratch, then get_module to pull its source. Read-only; takes no title_id.

List the games (Titles) this connection may work with: TitleID, name, publication status and the permissions granted on each — call it first when the user names a game or says "my game", then pass its TitleID as title_id to the other tools. A game's sandbox copy is a separate Title (DevTitleID) with its own permissions (DevAccess); an empty Access means the live game itself is not granted. Filter by name or id with "search"; long lists are paged (skip/limit, HasMore). Read-only; takes no title_id.

List the SDK skills (name + description): instructions for coding against @idosgames/core services (currencies, store, quests, blockchain…), the module contract and composition, plus checklists such as idosgames-title-bootstrap (configuring a fresh Title so a game can run). Load one with get_skill before writing code against that part of the SDK. Read-only; takes no title_id.

List the NAMES of the title's integration variables and secrets, plus the outbound-HTTP allow list. Secret VALUES are never returned by any tool — reference a secret inside a CloudCode script as {{secret:NAME}} in a server.HttpRequest call and the platform substitutes it server-side. Use this to discover which credentials a title already has before writing an integration.

Move a card to another column (or to another position in the same one). Moving it into a done column also completes the task and awards its XP; moving it back out clears the completion mark. The reply says which happened.

Publish server-side game logic (CloudCode) and make it live. This is the only way to run custom code on the server, and the only way to write protected data: the ReadOnly/Internal buckets of a player's UserCustomData and the Runtime scope of the title's data store. The script is plain JavaScript filling a global 'handlers' object, e.g. handlers.claimDailyBonus = function (args, context) { … }. Inside a handler: log.Info/Warning/Error, context.UserID, and server.* (ReadUserData, GetTitleConfig, GetUserCustomData, SetUserCustomData, DeleteUserCustomData, BatchSetUserCustomData, BatchDeleteUserCustomData, GetPublicUserCustomDataOf, GetTitleCustomData, SetTitleCustomData, IncrementTitleCustomData, DeleteTitleCustomData, BatchSetTitleCustomData, BatchDeleteTitleCustomData, GetIntegrationVariable, HttpRequest) — each returns { Success, Error, Data }. No async/await, no imports; 10 seconds wall-clock per call and a per-execution cap on server.* calls. The only way out to the network is server.HttpRequest({ Method, Url, Headers, Body }) — there is no fetch and no XMLHttpRequest; it reaches only publisher-allow-listed hosts over https, and credentials go in as {{secret:NAME}} placeholders (see list_title_secrets), never as literal values. The code REPLACES the previous revision entirely — read get_cloud_code first and send back the full script. Games call handlers through the SDK's client.cloudCode.execute(name, args).

Remix an existing video job with new instructions. Starts a new job — poll get_video. ASYNC: returns a job with an id and status — poll get_video for the result.

Set the left-to-right order of the columns. Pass every column id of the board.

PARTIAL SAVE: writes ONLY the 'Advertising' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Advertising — logical ad Placements (rewarded video, interstitial, banner, app-open), the mediation Providers that serve them (AppLovin MAX, LevelPlay, ...) with per-platform app IDs and ad unit IDs, per-format settings, frequency capping, premium ad-removal perks, GDPR/ATT consent policy, rewarded-video server-side verification (SSV) and the daily revenue import from the provider's Reporting API. Shared secrets (SSV keys, report keys) are NOT stored here — only the NAME of the TitleSecrets entry that holds them.

PARTIAL SAVE: writes ONLY the 'AI' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. InApp AI generation features of the title - what a PLAYER can generate at runtime through the engine (text/NPC chat, images, video, speech, music, 3D). Enabled is the master switch; Features maps a stable FeatureKey (no '.' or '$') to one feature: its Modality, a Model = the id of a MODE (Text: an AI Coder mode such as "standard") or a TIER (media: an asset generation tier such as "image-balanced") - list the usable ones, with what the publisher's plan allows, with the dashboard action GetInAppAIModels (Text features that AllowImages need a mode that AcceptsImages), Behavior defaults per modality (no platform caps: MaxTokens is bounded only by what the mode's model can produce), Safety prompt checks, an audience Gate (SegmentGate), a Schedule (ScheduleSpec), per-player Limits (LimitSpec) and the in-game PriceOptions the PLAYER pays (in-game resources and/or ONE store purchase per generation - a Purchase entry in the option's base price; never inside PremiumTiers, never two per option). Each generation is charged to the PUBLISHER's credits by the engine at the model's price; per-title spend caps (in credits) live in the PRIVATE config (InAppAIBudget), not here. Server-only section: never sent to the game client or the CDN.

PARTIAL SAVE: writes ONLY the 'Analytics' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Custom events - Firebase Analytics parity. The game sends its own events (logEvent(name, params, value)); the engine stores them per player per UTC day and the dashboard reports counts, unique players, value sums and breakdowns by platform, app version, OS, device, language, country, new/returning and acquisition source; A/B experiment goals and custom funnel steps can use these events. Enabled is the master switch and defaults to OFF. EventNaming: "Open" (any valid name is accepted and joins the title's event catalog up to the PLAN limit) or "Declared" (only names listed in Events). Events maps an event name (^[A-Za-z][A-Za-z0-9_]{0,39}$; prefixes idos_/firebase_/google_/ga_ are reserved, except the automatic idos_* events) to a display name, description and a Blocked flag. Dimensions registers event parameters as reporting dimensions (like GA4 custom dimensions) - the count is capped by the plan; unregistered parameters are accepted but not stored. RetentionDays is how long per-player event data is kept (default 90, capped by the plan); daily title summaries are kept forever. AutomaticEvents (default on) accepts the SDK's automatic events: idos_first_open, idos_session_start, idos_app_update, idos_os_update, idos_screen_view.

PARTIAL SAVE: writes ONLY the 'AssetBundle' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Dictionary<string,string> of named bundle/manifest URLs (Unity AssetBundles, Addressables manifests, etc.). Key is a logical bundle slug, value is its CDN URL. Use this for binary game content; for images alone use ImageData.

PARTIAL SAVE: writes ONLY the 'Attribution' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Acquisition attribution — how the engine records WHERE a player came from. The signal (utm_source/medium/campaign/term/content, the ad network's click id, the referrer, the invite code) arrives with the login request and is stored as a chain of touch points on the player: the first touch is immutable, the last touch tracks win-backs, and the chain in between feeds multi-touch models. This section only tunes that recording: how many touches to keep, how long after a touch an identical signal is still considered the same click rather than a new one, and optional aliases that normalise messy source/medium values into canonical ones for analytics. Referral invites are recorded through this same mechanism as a channel, so they show up in the acquisition reports alongside paid traffic.

PARTIAL SAVE: writes ONLY the 'Authentication' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Authentication — which third-party sign-in methods the title offers and the public OAuth client IDs each platform build needs (currently Google: Web / Android / iOS / Desktop client IDs). Contains NO secrets: OAuth client IDs are public by protocol design, and none of the sign-in flows uses a client secret. Device / e-mail / Telegram / SSO logins need no configuration and are absent from this section. The ID-token audience differs per platform (web and Android tokens carry the Web client ID, iOS tokens the iOS client ID), so several IDs are filled at once and the server accepts any of them.

PARTIAL SAVE: writes ONLY the 'Ban' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Ban levels and the level ban gates apply to a player. The publisher defines any number of named levels (e.g. "low"/"medium"/"hard") — each with capability checkboxes (BanCapability: block withdrawals, deposits, leaderboards, trading, PvP, chat, social, coop, referral, push, community marketing, crypto convert, purchases) plus an optional BlockLogin flag that shuts the player out of the game entirely and overrides everything else on that level. DefaultLevelID is the level a manual ban applies when the caller does not pick one. Two built-in ids always work even when not listed here: "hard" (blocks login) and "soft" (synthesized from the legacy Soft section below). Use PLAYER-facing tools (SetPlayerBanStatus) to actually ban a player with a level ID from here — this section only defines what each level MEANS.

PARTIAL SAVE: writes ONLY the 'Blockchain' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. On-chain integration config — chain selectors, smart contract addresses, RPC overrides, gas policy, supported networks for Crypto currencies. Built largely from Currency.CryptoCurrencies[].Networks; this is the title-level companion config.

PARTIAL SAVE: writes ONLY the 'Character' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Character/hero catalogue — playable units, NPCs, summons. Defines stats, abilities, evolution/level-up paths, art/asset references. Distinct from Item (generic inventory) — characters typically have progression and abilities. Skins (alternative looks) live per character in Skins.Definitions, and each skin IS a non-stackable, non-expiring Item from the Item section (Skins.Definitions.<id>.Item) — create that item first; any system that grants items (Store offers, lootboxes, season, quests, rewards) then grants the skin, and Item.Stats, if set, count toward Power like gear.

PARTIAL SAVE: writes ONLY the 'Chat' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Player chat - the catalog of persistent CHANNELS the title offers (world / announcement / group), plus direct-message settings, moderation rules and polling economics. A channel declares who SEES it (SegmentGate + ScheduleSpec) and who may WRITE to it (a second gate plus LimitSpec anti-spam: slow mode, daily cap); an announcement channel is simply one nobody passes the write gate of. A channel may be PARTITIONED by the player's language or country and sharded by capacity - the partition key is computed by the SERVER (language is validated against this title's Localization locales, country comes from IP), so the set of rooms is bounded by config and never by client input. Type=Group is the extension point for clans: membership comes from an external provider named in GroupSource, and no provider exists yet, so such a channel is currently hidden rather than shown empty. Messages themselves are NOT here - they live in the ChatMessages collection and expire by Retention.HistoryHours; only the hot tail is cached in Redis. Muting a player and reviewing reports are admin actions, not config.

PARTIAL SAVE: writes ONLY the 'CloudCode' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Server-side scripting (CloudCode): the active JavaScript revision the title runs, plus execution policy — engine limits, rate limits, per-handler metadata, whether logs/stack traces are revealed to clients. Scripts are the ONLY way to write protected player data (UserCustomData ReadOnly/Internal buckets) and mutable title data (TitleCustomData Runtime scope). Prefer the dedicated cloud-code tools over editing this section by hand: they compute the code hash, bump the revision number and archive the previous one.