viverse-i18n

Detect user language preferences in VIVERSE iframe environments via cookies and browser metadata.

2|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/viverseofficial/viverse-sdk-skills --skill viverse-i18n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: viverse-i18n
Source: https://github.com/viverseofficial/viverse-sdk-skills/tree/main/skills/viverse-i18n
Command: npx skills add https://github.com/viverseofficial/viverse-sdk-skills --skill viverse-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of maintaining consistent language settings and localized UI text across VIVERSE-hosted browser games by leveraging platform-native cookies and a structured translation system.

Core Features & Use Cases

  • Language Detection: Automatically identifies user language preferences via VIVERSE cookies, URL parameters, or browser settings.
  • Translation Management: Provides a centralized t() function for managing localized strings and dynamic variable substitution.
  • Use Case: A developer can use this to ensure that game UI elements, weapon descriptions, and wave banners automatically display in the user's preferred language, such as Traditional Chinese or Japanese, without manual configuration.

Quick Start

Use the viverse-i18n skill to initialize the locale detection and translate the UI label for the continue button.

Frequently Asked Questions about viverse-i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement localization in VIVERSE web games?

Implement localization by detecting user language preferences through VIVERSE cookies and browser metadata, then managing UI translations through a centralized helper function with dynamic variable substitution.

How does browser language detection work for iframe environments?

Browser language detection for iframe environments works by parsing VIVERSE-hosted cookies, URL parameters, and browser settings to automatically identify user language preferences without manual configuration.

What is the best way to manage UI translation fallbacks for missing locale keys?

The best way to manage UI translation fallbacks is using a centralized translation helper that implements robust fallback logic, ensuring English defaults are applied when specific locale keys are missing.

Can I use a centralized translation function for dynamic text in web games?

You can use the centralized t() translation function to manage localized strings and dynamic variable substitution for game UI elements, weapon descriptions, and wave banners.

Does this localization approach support languages like Traditional Chinese and Japanese?

Yes, the localization system supports languages like Traditional Chinese and Japanese by detecting browser preferences and mapping them to structured translations for game UI elements and dynamic text.

Why are my game UI labels not displaying the correct language in VIVERSE?

Game UI labels may fail to display the correct language if VIVERSE cookies are not properly parsed, or if specific locale keys are missing and the system falls back to English defaults.