Changelog

Changes

Takaro 2.2 adds Player Progression. Games that report levels now show them on the player profile, and your modules can react when a level goes up or down. The player profile shows IP and name history again, and free domains can upgrade without leaving their domain.

🚀 Features

• Player Progression Open a player and look at Progression on the Overview tab. It shows every level track the game reports, such as a character level or a skill, for each server the player is on. The game defines the tracks, so you see what your game tracks. It works on games whose connector reports progression.

• Level-changed event When a level goes up or down, Takaro fires a player-level-changed event. Use it in a module hook to reward a level-up, post it to Discord or flag a strange jump. See Hooks in the module docs.

• Level history Takaro keeps a history of each player’s levels. Modules and tools can read it through the Tracking API.

• IP and name history The player profile shows IP history and Known aliases again: every IP address and name a player has used. Handy to spot alt accounts and players who come back under a new name.

• Linked User ID and Discord ID The Identity section of the player profile shows the linked User ID and Discord ID, for staff who can read users.

• Bans page A new Bans page lists every ban. Recent bans shows who was banned, on which server and until when.

• Upgrade from inside Takaro Free domains get an Upgrade button. It opens your own subscription, so your servers, players and modules stay on the same domain.

✨ Improvements

• The item picker in module settings is wider, searches by item code and puts exact matches first.
• Installing a module on another game server points its item settings to the same items on that server. If an item is missing there, Takaro says so instead of saving a broken setting. Existing installs were repaired.
• Item and entity names no longer show raw 7 Days to Die colour tags like [FF0000].
• The inventory on the player profile now shows what the Map shows.
• Codex (0.166.0 or newer) can sign in to the Takaro MCP server. Add the client id, scopes and feature flag from Settings → General → AI assistants → Codex to ~/.codex/config.toml, then run codex mcp login takaro.
• Module authors can unit-test modules outside Takaro with the @takaro/module-test package.

🐛 Bug Fixes

• The players-by-country map draws Russia correctly, fills its card and opens by default.
• Map and Tracker popups fit their content.
• The Getting started checklist and other popovers no longer get cut off on short screens.
• The Events page highlights the active time window in Live mode.
• Module run logs no longer cut off small values.
• An unknown 7 Days to Die console command returns a clear failure instead of an error.
• Accounts whose only domains are disabled get a clear page with a Log out button.
• A Helpers add-on no longer breaks the billing check for people who also pay for a plan.

⚠️ Changes for existing users

• Tracking API changes (module and API users only) Tracking now reads from one store. The old endpoints /tracking/location, /tracking/location/box, /tracking/location/radius, /tracking/inventory/player and /tracking/inventory/item are gone, and inventory was removed from the player-on-gameserver data. Use POST /tracking/inventory/at and the other Tracking endpoints instead. No built-in module used the removed endpoints.

Changes

Takaro 2.1 adds the Tracker to every server’s Map. Pick a time range and see where players were, who entered an area and who picked up which items. The live map also gets layers, deaths and offline players.

🚀 Features

• Tracker Switch the Map from Live to Tracker, pick a time range and drag the timeline. The map shows where every player was at that moment. The view is saved in the page address, so you can share it with your team.

• Trails and playback See each player’s trail over the chosen range and play it back at the speed you pick. In Live mode, the Recent trails layer shows which way players are heading.

• Area search Draw a circle, rectangle or shape on the map. Takaro lists every player who was inside it, with when they first and last were there. Export the list as CSV.

• Theft tab Draw an area around a base and open Theft. It lists every item a player gained while inside that area: who, when, what, how many and from which container when the game reports it. Treat it as strong evidence, not proof.

• Item search Search an item by name and see who held it and when, with every gain and loss on the timeline.

• Inventory at a moment Select a player in the Tracker to see their inventory at that moment and how it changed.

• Kills, deaths and connects on the timeline Deaths, kills, connects and disconnects show on the timeline and the map.

• Live map layers The live map groups crowded markers, has a layer menu, shows player details on click, and can show recent deaths and offline players.

• Search players by name Find players by name, and search tables across the dashboard.

• Enable or disable installed modules The installed-modules list shows whether each module is on, and you can switch it from there. Each installation also shows the health of its parts.

• Portal players can link Steam and Discord Players can connect Steam and Discord to their account from the player portal.

• Resizable side panels Panels that open on the right can be resized on desktop.

✨ Improvements

• Takaro AI can read the text of chat messages.
• Takaro AI settings moved into their own section.
• Module install and uninstall events record the module version.
• Module code can check another module’s permission by name.
• 7 Days to Die log noise is filtered out.
• Module runs wait in line when the sandbox is busy, instead of failing.

🐛 Bug Fixes

• Player and User role permissions can be edited again.
• Maps with bounds but no image display correctly.
• Trails no longer jump on teleports in games with large coordinates.
• The dashboard reloads once instead of breaking after an update.

⚠️ Changes for existing users

• New permissions: Read Map and Read Tracking The Map and the Tracker each have their own permission now. Every role that could read players got both, so nobody loses access. Remove them from a role to hide the Map or the Tracker.

Changes

Takaro 2.0 replaces the dashboard, adds login with Discord or Steam next to email, and builds Takaro AI into the product. Existing users: you’ll be logged out once — see the login steps below.

🚀 Features

• New dashboard The new dashboard replaces the old one. Everything sits in one sidebar, and the overview shows online players, servers, recent events and recent bans.

• Search (Ctrl+K) Press Ctrl+K to find players and servers or ask Takaro AI.

• 15 dashboard languages English, Dutch, French, German, Spanish, Russian, Portuguese (Brazil), Polish, Ukrainian, Simplified Chinese, Japanese, Italian, Turkish, Arabic and Hebrew. Arabic and Hebrew read right to left. The login pages follow the same language.

• Server setup guide Creating a server now opens a setup guide: find the mod for your game, add your registration token (a code Takaro gives you), start the server.

• Log in with Discord or Steam New users can sign up with Discord, Steam or email. Existing users can link Discord or Steam under Account settings.

• Steam sign-in links players automatically Players who sign in with Steam are linked to their player profile and can use the community’s web shop without a link code.

• Takaro AI Takaro AI is built into the dashboard. It writes and edits modules (add-ons that add commands and features to your server) from a description, explains failed commands and hooks, summarizes players, suggests role permissions and helps migrate from CSMM, the older server manager. It acts with your permissions, every change waits for your approval, and anything that runs on your game server’s console always asks first. On the free plan, connect a server first.

• Invite links Invites are now shareable links.

• Item sets Save several items as one set.

• Player storefront at its own address The player shop runs as a storefront at its own address for each community.

• Settings with search Settings are rebuilt and searchable.

• Module sandboxes Module executions run in disposable sandboxes.

• API keys Personal, domain and distributor API keys, with IP allowlists.

• Protocol v1 with map upload Generic Game Protocol v1 adds capability manifests and map upload.

⚠️ Changes for existing users and module authors

• Your first login after the update

  1. You’ll be logged out once when the update goes live.
  2. Sign in with your current email and password.
  3. Open the user menu → Account settings and link Discord or Steam.
  4. From then on, log in with any of them.

  Don’t log in with Discord or Steam before you’ve linked them. That creates a separate, empty account without your servers.

• Module network access Module functions can only reach the Takaro API by default.

• Hook patterns run on RE2 Hook patterns now run on RE2, so unsafe text-matching patterns are rejected.

• x-takaro-token retired The x-takaro-token header is retired.

• docker-compose self-hosting removed The old docker-compose setup is removed. Takaro runs from the Helm chart.

Changes

Groundwork for the new dashboard, and a Discord fix.

✨ Improvements

• First building blocks of the new dashboard that shipped in Takaro 2.0.

🐛 Bug Fixes

• Fixed Discord sync saving server lists under the wrong user for people in several communities.

Changes

Two fixes.

🐛 Bug Fixes

• Fixed a blank black screen when opening pages with a lot of data.
• Fixed Discord linking sending people who belong to several communities to the wrong one.

Changes

Quick follow-up to v0.7.0.

✨ Improvements

• The log rate limit is looser, so busy servers no longer lose log lines.

Changes

v0.7.0 rebuilds analytics and protects servers from event floods.

🚀 Features

• New analytics Analytics is rebuilt with Overview, Modules and Players tabs, and loads faster on busy communities.

• Event rate limits Takaro now limits how many events one source can send at once, so a misbehaving server can’t slow down everyone else.

🐛 Bug Fixes

• Fixed rate limits counting logs the server had already rejected.
• Fixed missing connected events for 7 Days to Die console players.

Changes

v0.6.0 tightens up audit visibility, shop management, and error tracking. It also cleans up a few backend edges that were causing noisy or wrong behavior.

🚀 Features

• Role audit events Permission changes in role updates are now recorded in audit events, so you can see what changed and who changed it.

• Manual shop ordering Shop listings can now be ordered manually. That gives you control over how items appear instead of relying on default sorting.

• Better table filters and column visibility Table filter options now cover more cases, and column visibility is stored. That makes the UI less fiddly when you keep coming back to the same views.

• Generic connector flow for Rust servers The Rust game server form now uses the Generic Connector flow.

• Unified Sentry tracking Frontend and backend errors now feed into the same Sentry setup, which should make debugging easier when something breaks across the stack.

🐛 Fixes

• Subscription billing for multi-product plans Subscriptions with multiple products now bill correctly.

• Wrong Socket.IO events for multi-domain users Users tied to more than one domain no longer get the wrong Socket.IO events.

• Noisy module install/uninstall events Component updates no longer trigger excessive module-installed and module-uninstalled events.

• Inventory history on the wrong server Player inventory history now stays tied to the right game server.

• Link command feedback The link command no longer triggers unknown command feedback.

🧰 Maintenance

• Styled-components SWC cleanup
• Share duplicated code between SelectField and SelectQueryField
• Bump Vite to v8
• Remove React.FC in favor of explicit function declarations

🤖 Dependency updates

• vitest to v4.1.4 and v4.1.3
• vite to v8.0.8, v8.0.7, and v8.0.5
• node.js to v24.14.1
• esbuild to v0.28.0

Changes

Quick follow-up release.

This one fixes the shop visibility regression and adds a small but useful improvement for currency operations.

✨ Improvements

• Shop listings are visible again We fixed the regression that made shop listings disappear for players. If your shop looked off after 0.5.1, this is the fix.

• Reason field for currency operations Currency operations can now store a reason. That gives you better context when you’re checking why currency was added, removed, or changed.

Notes

No breaking changes in this release.

If something still feels off after updating, let us know in Discord.

🚀 Features

• Shop Actions - add a new module component type for shop-driven automation. A purchase can now grant a role, send a message, execute a command, give an item, or run custom logic.
• Inventory change events - player-inventory-changed events now fire when items are added, removed, or changed, so hooks can react right away instead of relying on cron polling.
• ClickHouse event storage - events are now dual-written to ClickHouse alongside PostgreSQL, giving larger deployments a better base for faster event queries.
• Role member views - view players and users assigned to a role directly from the frontend.
• CSMM shop import support - import CSMM shop data with better compatibility.
• Tracker and module links - navigate to related tools more easily from the frontend.

🐛 Fixes

• Prevent midnight database connection pool exhaustion
• Improve cronjob reliability under high load
• Fix CSMM shop imports that stored item quality as zero
• Return proper 400 errors for invalid shop listing imports
• Return a clear error when referencing non-existent records
• Show the full version string in the frontend instead of 0.0.0
• Restore the shop item quantity tooltip on hover