
One chat across all maps
FreeMessages flow between every approved map and the panel, live. Map labels, who is online where, admin messages straight from the panel.
For ARK cluster admins
A plugin for ARK: Survival Ascended and Survival Evolved plus a hosted panel. Up and running in ten minutes — no shared MySQL, no open ports, no RCON.

The problem
Players on The Island don’t see Ragnarok. Every map is an island — literally.
Tribe chat stays on one map: tribemates on other maps never see it.
A typical crosschat plugin needs a MySQL you host and a config synced to each box by hand.
Discord bots, RCON tools and spreadsheets, just to know who is online and where.
How it works
The plugin goes on every map. The panel, chat history, bots and API run in our cloud.
Download the ASA or ASE build in the panel and unpack it into the AsaApi or ArkApi plugins folder.
Paste the config.json from the panel: project key and SatayaLib address. One key serves every map.
Restart the map. It shows up in the panel as “awaiting approval” — approve it and pick a cluster.
config.json on every map{
"key": "YOUR_PROJECT_KEY",
"url": "wss://satayalib.com/plugin/connect"
}The panel shows the key once and gives you this file ready to copy. Restart game servers one by one, as with any plugin.
Features
The badge shows the plan a feature needs; where part of it is on Free, the card says so. Cross-map chat, tribe chat and bridges are on Free.

Messages flow between every approved map and the panel, live. Map labels, who is online where, admin messages straight from the panel.

A tribe on The Island links with its tribe on Scorched Earth by a one-time code typed in game: /st link. Or link them by hand in the panel.

A tribe owner or admin connects tribe chat and logs to Discord or Telegram from the game. Chat works both ways; logs go to a separate channel. Each channel receives only its tribe’s messages.

Add our bot to the channel, create a bridge and type /connect <code> there — that’s the setup. Chat both ways, joins and leaves, map status. We host the bots.

Player registry by SteamID / EOS ID with survivors per map, on Free. Pro adds the “who is where” map, refreshed every 30 seconds, and offline data.

Player groups with a term, from five minutes to forever. Members get a [VIP] label and colour their nickname and text with /st color, seen on other maps.
A banned-word filter and player mutes by platform ID. Mutes apply across all maps in the project; the panel keeps the reason, duration and moderation history. You can also choose your own command prefix.
Owner, admins and viewers sign in by email code, no passwords. Revoke a key and its maps drop at once.
REST for chat, game servers and players, plus a WebSocket event stream. Tokens with scopes.
Bridges run under your bot’s name and avatar. You give us the token; we still host the bot.
Add the date, time, platform and tribe to messages from the game. Choose a time zone and highlight key details in bold — the same syntax works in Discord and Telegram. The panel includes examples and a preview.
Set up a message templateTemplate
[{date:Europe/Moscow} {time:Europe/Moscow}] {platform} **[{map}] {character} [{tribe}]**: {text}Result
[2026-10-17 16:30:49] Steam [Ragnarok] Alex [Northern Wolves]: On my way to The Island.
Example using demo data
A live board in Discord or Telegram shows player counts and connection status for each map. The bot updates the existing message. Choose the maps and whether to show player names.
Availability depends on your plan settings. Ask in Discord for details.
How the live board worksServer frame times, player counts, disconnections and alerts on one timeline. Review the history and compare map status in the panel.
About map healthPlanned SatayaLib features. They are not available yet; release dates have not been announced.
Planned alerts for possible raids based on tribe log events, delivered to Discord and Telegram with sensitivity controls and limits on repeated notifications.
Status: Not available yet
View a snapshot of a survivor, inventory, dinos and structures in the panel. The inspector is designed to review data without changing the game world.
Status: Not available yet
Compare
What a typical crosschat plugin asks you to run, and what SatayaLib asks instead.
| Typical crosschat plugin | SatayaLib | |
|---|---|---|
| Database | A shared MySQL you host and maintain | None on your side: history lives in our cloud |
| Configs | The same config copied to every map by hand | Key and address in config.json; the rest in the panel |
| Ports and RCON | Usually a database port reachable from every machine | One outbound WebSocket per map; no ports to open, no RCON |
| New maps | Depends on the plugin | Wait in the panel until you approve them |
| Hosted panel and chat history | Usually none, or you host it yourself | Panel included; 7 to 365 days of history by plan |
| Tribe chat and bridges | Depends on the plugin | Tribe chat across maps, Discord and Telegram bots on Free |
Already running another crosschat? Put SatayaLib next to it on one map.
Plans
Free asks for no payment and never expires. Pay yearly and get two months free.
What you get:
Recommended
For clusters that sell VIP and moderate chat
$5/mo
$50/yr
$50/yr
≈ $4.17/mo
Everything in Free, plus:
For networks of up to 200 maps with their own bot
$12/mo
$120/yr
$120/yr
≈ $10/mo
Everything in Pro, plus:
Extended features, including a custom bot: 1 project, up to 25 maps and 30 days of chat history. Activated manually for 3 months on request in Discord. Ask separately about live board availability.
FAQ
Yes to both. The panel has a plugin build for ARK: Survival Ascended (AsaApi) and for ARK: Survival Evolved (ArkApi). ASA and ASE maps can sit in one cluster and share one chat. On ASE the nickname is not coloured separately: the whole line takes the text colour, or the nickname colour if no text colour is set.
No. Chat history, the player registry and settings live in our cloud. On each map you only edit config.json: the project key and the SatayaLib address, both from the panel.
No. The plugin opens one outbound WebSocket from the game server to the panel. There is nothing to open or forward, and no RCON.
Yes. Put SatayaLib next to it on one map and approve that map in the panel: you see its chat and players without breaking what already works. Move the other maps when you are ready.
Free gives 1 project, up to 25 maps and 7 days of chat history. It includes cross-map chat, tribe chat and tribe links, our Discord and Telegram bots with tribe channels, the player registry, team and keys.
“Forever” means it is not a trial: no card, no end date.
Features freeze, data stays: colours, groups, filter words and API tokens work again when you return to Pro. Chat history older than 7 days is hidden and deleted after a 30-day grace period. Approved maps are not switched off.
Every new game server that connects with your key waits for your approval. A key still opens your cluster, so replace a leaked one at once: revoke it in the panel (its maps drop immediately), issue a new key, put it into config.json on each map and approve the maps again.
Not yet. The panel, chat history and bots run in our cloud; only the plugin runs on your maps.
The panel is in English and Russian. Texts players see in game — the command hint, tribe link codes, colour replies — come in English and Russian, and you can rewrite each one in any language, along with map and platform names.
In our Discord: questions, tickets and feature requests all go there. Setup steps for the plugin, the panel and the bots are in the documentation.
Free needs no card and has no end date. All you need is AsaApi or ArkApi and access to the plugins folder on each map.
config.json