Library Setup
Complete guide to initialising and configuring your server's ScriptVault library.
Initial setup
Run /library setup once to initialise your server's library. This command requires Administrator permission and can only be run once per server.
After setup your library is immediately active on the Free plan. Run /library status to confirm configuration and see your limits.
Configuration options
Use /library config to update any of the options below at any time (Admin only).
| Option | Description & example |
|---|---|
library_name | Display name shown in Example: |
announcement_channel | Channel where new approved scripts are announced automatically. Optional. Example: |
library_manager_role | Role that can manage scripts, approve/reject, resolve reports, view analytics, and run bulk operations. Example: |
upload_manager_role | Role that can upload scripts. Does not grant approval or management powers. Example: |
approval_mode | Who can upload and whether scripts need review before going live. See below. |
Approval modes
The approval mode controls who can upload scripts and whether they need staff review before members can download them.
admin_only
Only Administrators (and Library Managers) can upload scripts. Scripts go live immediately. Best for small, tightly managed servers where only a handful of people ever upload.
/library config approval_mode:admin_only
trusted_role
Upload Managers and Administrators can upload. Scripts go live immediately without requiring review. Good for servers with trusted contributors who don't need their uploads reviewed every time.
/library config approval_mode:trusted_role
pending_review
Any server member can submit a script. Submissions enter the pending queue and are hidden from search until a Library Manager or Admin approves them. Best for open libraries with community submissions you want to vet first.
/library config approval_mode:pending_review
Script access control Pro / Creator
Pro and Creator servers can restrict who can download individual scripts using three access modes. Every script defaults to public — no changes needed unless you want to restrict access.
Setting access
Restrict a script to members with a specific role:
Example
/script-admin manage access-set script_id:SC1A2B3C mode:role_required role:@VIPRestrict a script to staff only:
Example
/script-admin manage access-set script_id:SC1A2B3C mode:staff_onlyMake a script public again:
Example
/script-admin manage access-set script_id:SC1A2B3C mode:publicView current access configuration:
Example
/script-admin manage access-view script_id:SC1A2B3CPlan limits
| Limit | Free | Pro | Creator |
|---|---|---|---|
| Script slots | 250 | 5,000 | 20,000 |
| Storage | 50 MB | 500 MB | 2 GB |
| Max file size | 512 KB | 1 MB | 2 MB |
| Bulk import (files/batch) | 10 | 50 | 100 |
| Bulk approve / reject | 25 | 100 | 250 |
Run /library status at any time to see current usage against your plan limits. See the Pricing page for full plan details and add-ons.