@Commands

Logs @commands executed by staff members to Discord

The AtCommandScript handles logging of @commands (GM commands) executed in-game to Discord for audit purposes.

Action

at_command

When It's Used

This script is triggered when:

  • A player executes any @command (e.g., @warp, @item, @ban)

  • The player's group ID meets or exceeds the configured minimum

  • @command logging is enabled in the server configuration

Why Use It

  • Audit GM activity to ensure staff members are following guidelines

  • Track abuse by logging all privileged commands

  • Maintain accountability with permanent Discord logs

  • Monitor server administration in real-time

Server Configuration

In conf/channels.conf:

Setting
Description
Default

enabled

Enable/disable @command logging

false

group_min

Minimum group ID to log (99 = Admin only, 1 = all staff)

99

channel_id

Discord channel ID for command logs

-

Message Format

The script sends formatted messages to Discord:

Format: Account ID | Char ID | Character Name | Command | Time

Data Fields

Field
Type
Description

name

string

Name of the character executing the command

command

string

The full @command with arguments

account_id

int

Player's account ID

char_id

int

Player's character ID

channel

string

Discord channel ID

Example Use Cases

Log All Staff Commands

Set a low group threshold to log all staff activity:

Admin-Only Logging

Only log commands from administrators:

Private Audit Channel

Send logs to a restricted channel only visible to senior staff:

Custom Templates

Customize your command log messages with templates. Add a [template: ...] field to create your own format.

Example:

Result: ⚠️ AdminName used @warp prontera at 14:30:25

See Message Templates for all available placeholders and examples.

Notes

  • Commands are logged with full arguments for complete audit trails

  • Logs include timestamps for tracking when commands were executed

  • Use with @request logging for comprehensive staff monitoring

Last updated