Skip to main content
Glama

Save Ban settings

save_ban
Destructive

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesNew value for the Ban field.
title_idYesTitleID, для которого сохраняются данные.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.