Project settings control how your project behaves: security, validation, webhooks, and checkpoint theming. Access them from Project → Settings in the dashboard.
| Setting | Description |
|---|
| Project Name | Display name (can be changed anytime) |
| Description | Optional notes for your team |
| Project ID | Read-only; used in API and loader URLs |
| Setting | Type | Description |
|---|
| allow_hwid_reset | boolean | Allow users to reset their hardware ID via Discord |
| max_hwid_resets | 1–100 | Maximum number of HWID resets allowed per key |
| hwid_cooldown_hours | 1–168 | Hours between HWID resets (cooldown) |
| max_hwids_per_key | number | Maximum hardware IDs that can be associated with a single key |
| Setting | Type | Description |
|---|
| require_discord_link | boolean | Users must have a Discord ID linked to their key to execute |
| prevent_identity_change | boolean | Prevent users from changing the Discord identity linked to a key |
| Setting | Description |
|---|
| webhook_url | URL for event webhooks (executions, key validations) |
| alert_webhook_url | URL for security and alert notifications |
| Toggle | Description |
|---|
| alert_on_new_key | Send webhook when a new key is created |
| alert_on_hwid_lock | Send webhook when a key is HWID-locked |
| alert_on_execution | Send webhook on each execution |
| alert_on_anti_tamper | Send webhook when anti-tamper is triggered |
Control whether users on VPNs can use your keys.
| Setting | Type | Description |
|---|
| vpn_check_enabled | boolean | Enable VPN detection |
| vpn_block_action | 'block' | 'flag' | 'none' | Action when VPN is detected |
| vpn_provider_key | string | Optional custom API key for the VPN detection service |
| Action | Behavior |
|---|
| block | Keys fail validation when VPN is detected |
| flag | Log VPN usage but allow access |
| none | No action; VPN users allowed |
| Setting | Description |
|---|
| validation_rules_enabled | Enable custom validation rules for key acceptance |
When enabled, validation rules define custom logic (e.g., HWID required, Discord linked, IP whitelist). Rules run in order; if any rule fails, the key is rejected.
Customize the checkpoint page shown during the keysystem flow:
| Setting | Description |
|---|
| accent_color | Primary accent color (e.g., #D4AF37) |
| logo_url | Direct URL to your logo image |
| heading | Custom heading text |
| description | Custom description text |
These settings customize the appearance of your keysystem checkpoint page.
The system tracks security-related events that may indicate abuse:
| Flag Type | Description |
|---|
| rapid_execution | Unusually high execution rate |
| unusual_hour | Execution at atypical times |
| ip_country_change | IP country changed between requests |
| multi_key_attempt | Multiple key attempts from same source |
| hwid_anomaly | Unusual HWID patterns |
| brute_force | Brute-force key attempts |
Security flags can trigger alerts via alert_webhook_url when configured.
Click Save at the bottom of each settings section to apply changes. Some settings (e.g., webhooks) take effect immediately; others may require a short propagation delay.