Technical Specification

Vectra Mod utilizes a custom-engineered JSON flat-file storage pipeline to provide lightning-fast, zero-latency moderation logging without the overhead of external database clusters. The system now features the V2 Embed Standard for all user-facing responses.

01

Deployment Lifecycle

1Environment Configuration

Populate the .env file in the root directory. This version of the template requiresDISCORD_TOKEN, BOT_NAME, COMMAND_PREFIX, and the EMOJI_configuration suite. The MongoDB requirement has been deprecated in favor of local persistence.

2Dependency Synchronization

Execute npm install. The bot core is optimized for minimal dependencies, relying primarily on discord.js and dotenv.

02

Core Command Suite

COMMANDPARAMETERSEXECUTION PATH
!helpNoneDynamic command matrix
!pingNoneConnectivity & latency metrics
!warnID/User + ReasonWrites to warns.json
!muteID/User + ReasonWrites to mutes.json
!banID/User + ReasonWrites to bans.json
!kickID/User + ReasonWrites to kicks.json
!modlogsID/UserAggregates user JSON logs
03

Logging Infrastructure

Atomic JSON Storage

Instead of a monolithic database, Vectra Mod utilizes an atomic file-system approach. Each user has a dedicated directory within the Logs/ folder, ensuring that read/write operations are isolated and extremely fast.

Logs/
└── user_123456789/
├── warns.json
├── mutes.json
└── kicks.json

Action Log Pipeline

Vectra Mod supports real-time logging to designated Discord channels for staff visibility and audit trails. Configure these via environment variables:

  • LOG_CHANNEL_KICK_BAN: High-priority logs (includes @here @everyone pings).
  • LOG_CHANNEL_MOD: Standard moderation logs (warns, mutes).
04

Branding & Iconography

Vectra Mod is fully white-label ready. You can replace the standard V2 iconography with your own Discord custom emojis by providing their unique Snowflake IDs in the environment configuration.

EMOJI_SUCCESS=<a:success:123456789>
EMOJI_ERROR=<a:error:123456789>
EMOJI_INFRA=⚖️
05

Advanced Permission Grid

STAFF_LEVEL_01

Permissions: ModerateMembers

Actions: Warning, Muting, Kicking, View Logs

STAFF_LEVEL_02

Permissions: BanMembers

Actions: Banning, Unbanning