Integration

Languages

The game interface language is chosen per launch with the lang field of /playGame.do.

Codes#

lang is a standard BCP 47 code: en, de, pt-BR, zh-Hans, zh-Hant, es-419, … The platform normalises it before use:

• case does not matter (PT-br → pt-BR), and _ is accepted instead of - (pt_BR);
• a few common variants are mapped to the code the games use:

The code is a 2–3 letter language followed by optional subtags separated by - or _ (letters and digits), at most 16 characters in total.

Which languages a game supports#

Each game accepts exactly the languages its client offers. The list is the languages array of the game in GET /games/health and the Languages column on the games list. Across the whole catalog there are 43 languages:

Default language and errors#

• If lang is omitted, the project default language is used (admin panel → Projects → Technical settings; the panel offers Russian, English and Ukrainian).
• If the code is malformed or the game does not offer it, the launch is answered with HTTP 400 UNSUPPORTED_LANGUAGE. Choose another language or omit lang.

Switching language#

Launch again with another lang. If the player has an unfinished round, the same session continues in the new language; otherwise a new session is created. The session stores the standard code and the game receives the code its own client expects.

The session language is returned in meta.language of the launch response.