Skip to main content

Glossary

This glossary keeps the terms used in the user guide, API reference, and developer documentation consistent.

Accounts and roles​

Team​

The owner workspace. A team contains projects, balance, plan, panel users, and access settings.

Administrator​

A staff member or owner who signs in to the MMO-DEV WEB SaaS panel and manages projects, servers, users, payments, plugins, and settings.

User​

A player or customer of a project. In the API documentation, a user is usually connected to a master account, sessions, contacts, balances, and game accounts.

Master account​

The user's primary account in the project cabinet. It is used for sign-in, email, Telegram, social profiles, PIN, 2FA, and linked game accounts.

Game account​

An account inside a game server. It may have its own login, password, characters, warehouse, restrictions, and maintenance operations.

Linked account​

A confirmed two-way relationship between accounts in one project. It allows quick switching without merging balances, warehouses, or game accounts.

Projects and servers​

Project​

A separate website or game project inside a team. A project stores client-site settings, languages, payment methods, servers, templates, plugins, and public configuration.

Server​

A generic server entity in a project. Depending on context, it may mean a game server, login server, or the user's selected server.

Game server​

A specific game world, shard, or realm. It stores platform, database connection, statistics, ratings, characters, shop, cases, and gameplay settings.

Login server​

The game authentication server. It is used for game-account verification, password changes, and operations related to game-server logins.

Selected server​

The server attached to the user session and used by authenticated operations when an operation does not receive an explicit gameServerId.

Platform​

The game integration type, for example Lineage 2 or another supported platform.

API​

GraphQL endpoint​

The project HTTP endpoint, usually /graphql, where all API requests are sent.

documentId​

The identifier of an allowed GraphQL document. Instead of sending arbitrary GraphQL text, the client sends a documentId, for example me, login, servers, or preparePlayerWalletTopUp.

variables​

The operation variables object. If an operation does not need input, send an empty object {}.

Context token​

The public project context token from identity.contextToken. It is sent in the X-Project-Context header and binds an API request to a project.

X-Project-Context​

A required API HTTP header. It receives the context token from the current project configuration. Do not build it manually from project or server IDs.

Authorization​

An HTTP header in the form Authorization: Bearer <sessionId>. It is used by operations that require an authenticated user.

sessionId​

The user session token returned by sign-in operations. It is passed in Authorization for subsequent requests.

Input type​

The input structure of a GraphQL operation. API input types are documented in the API schema reference.

Result type​

The response structure of a GraphQL operation. It explains which fields the operation returns and which nested objects the client can use.

Enum​

A list of allowed field values, such as status, provider type, action method, or entity category.

API error​

A standard GraphQL response with an errors array. The error category is usually available in errors[].extensions.category.

Game and user data​

Warehouse​

Storage for user items, rewards, and purchases. From the warehouse, the user can choose a recipient and deliver an item to a character.

Character​

A game entity inside a game account. It is used by inventory, item delivery, statistics, and gameplay operations.

Payment​

A top-up or purchase operation. In the API, a payment contains a method, amount, result, and processing state.

Purchase calculation​

A short-lived server result created before purchase. It contains the verified offer, recipient, adjustments, total, and expiration. The client displays it and sends its identifier to the next operation; it does not calculate the total itself.

Plugin​

A connected platform extension: shop, cases, lucky wheel, support, in-game market, promo games, and other modules.

Module​

A functional platform or plugin area. In the API, this often means product areas such as shop, rewards, support, voting, and notifications.

Development​

Template​

A Twig file for the client website or cabinet. Templates are responsible for HTML markup and use data prepared by the platform.

Twig namespace​

A template directory alias, for example @site, @cabinet, @admin, or @common.

Asset​

A static resource: CSS, JavaScript, image, or font. In Twig, assets are usually included through the asset() function.

Webhook​

An HTTP call to an external system when an event occurs. If an integration uses a webhook, the endpoint must validate signature, source, and repeated delivery.