---
id: plugin.auto-vc
title: Auto VC
scope: plugins
status: active
priority: 10
visibility: user
category: Plugin
tags: plugin, auto-vc
generated: true
editable: false
updated_at: "2026-06-25T12:06:11.231Z"
---
# Auto VC
Auto-create managed voice channels from lobby rooms.
## Metadata
Plugin ID: auto-vc
Version: 0.1.5
Default state: enabled
## Web Routes
- /plugins/auto-vc
- GET /plugins/auto-vc
- POST /plugins/auto-vc/settings
- POST /plugins/auto-vc/bans
- POST /plugins/auto-vc/unban
## Route Reference
### MOUNT /plugins/auto-vc

- Purpose: Mounts the plugin router at this base WebUI path.
- Inputs: No request parameters detected by static analysis.
- Response format: Plugin router mount point.
- Access: Access is controlled by the mount options and individual plugin routes.
- Side effects: No direct route action; child routes handle requests.
- Limits/notes: Mount metadata is inferred from static source scanning.

### GET /plugins/auto-vc

- Purpose: Renders or serves the auto-vc plugin page.
- Inputs: No request parameters detected by static analysis.
- Response format: plain or HTML response
- Access: admin access expected; moderator access may be required; logged-in session required or used
- Side effects: Usually read-only.
- Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations.

### POST /plugins/auto-vc/settings

- Purpose: Processes the auto-vc plugin action for settings.
- Inputs: body: full submitted body is passed to a helper; exact fields are defined by the matching form/service
- Response format: HTTP redirect after handling the request
- Access: admin access expected; logged-in session required or used
- Side effects: writes or mutates server-side state
- Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion.

### POST /plugins/auto-vc/bans

- Purpose: Processes the auto-vc plugin action for bans.
- Inputs: body: `ban_input`, `ban_reason`
- Response format: HTTP redirect after handling the request
- Access: admin access expected; moderator access may be required; logged-in session required or used
- Side effects: Consumes submitted data; state mutation happens in called helpers if present.
- Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion.

### POST /plugins/auto-vc/unban

- Purpose: Processes the auto-vc plugin action for unban.
- Inputs: body: `unban_ids`
- Response format: HTTP redirect after handling the request
- Access: admin access expected; moderator access may be required; logged-in session required or used
- Side effects: Consumes submitted data; state mutation happens in called helpers if present.
- Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion.
## Commands
- No plugin command triggers detected.
## Source
Plugin folder: plugins/auto-vc