Skip to main content
This page explains what each feature does once enabled. Toggle them in the configuration.

​
Bidirectional sync

Moderation flows in both directions.
When you ban or mute someone in the dashboard, they are checked on their next join. Banned players are kicked, muted players have an Adonis mute applied, and the action shows in the Adonis :bans and :mutes lists.
The plugin prevents infinite loops: actions that came from the API are marked so they are not synced back, and Adonis actions only sync once.

​
Permission sync

When a staff member joins, the plugin looks up their Technified permissions, maps the level to an Adonis level, and sets it. Permissions are cached for 5 minutes to reduce API calls, and :tsync forces a refresh. API permissions add to your existing Adonis config rather than replacing it.

​
Ban sync

On server start, the plugin fetches all active bans and adds them to the Adonis Settings.Banned list. When a player joins, their ban status is checked and they are kicked if banned, with a message like this: 
===== BANNED FROM THIS GAME =====

Reason: Exploiting

Expires: 2024-03-20 15:00:00 UTC

Banned by: AdminName

Appeal at: https://technified.xyz
=================================
Using Adonis :ban Player1 1h Griefing parses the duration and reason, then syncs the ban to the dashboard.

​
Mute sync

On server start, active mutes are fetched and added to the Adonis Settings.Muted list. Joining players are muted if needed. Using Adonis :mute Player1 30m Spamming parses the duration and reason and syncs the mute to the dashboard.

​
Shield sync

Opt-in protection using the global Technified Shield list. When SYNC_SHIELD is on, each joining player is checked against the Shield list and kicked with the Shield reason if flagged. Shield checks run independently of per-guild ban sync. 
SYNC_SHIELD = true,

​
Session tracking

When a staff member at or above SESSION_MIN_LEVEL joins, a session starts and is logged to Roblox > Staff Activity. When they leave, the session ends and the duration is calculated. Each session records the staff Roblox username and ID, the game and Place ID, and start and end times.

​
Action logging

With LOG_ACTIONS on, moderation and admin commands are logged to Technified.
CategoryCommands
Moderationkick, ban, unban, mute, unmute, warn, jail, shutdown
Adminfly, tp, god, speed, heal, kill, freeze, invisible, noclip, and more
Each log entry records who ran it, the command, the target, the reason, the raw command text, the Place and Universe IDs, and a timestamp. Logs appear under Logs > Audit Logs with a filter for Roblox actions.

​
Game registration

On startup the plugin registers your game with Technified, sending its Place ID, Universe ID, name, creator ID, plugin version, and server job ID. The dashboard then shows which games are connected and can filter moderation by game.

​
Reliability

When a player leaves, their session is ended and logged, the permission cache is cleared, and state is freed, so there are no memory leaks during long uptimes.
If the API is unavailable, operations continue and errors are logged and counted. Players leaving mid-operation are handled safely, and malformed responses fall back to defaults.