-
-
Notifications
You must be signed in to change notification settings - Fork 20
Error messages like:
Main Server "main" not set up!!!Queue Server "queue" not set up!!!Auth Server "auth" not set up!!!
Cause: Your proxy config is missing the servers that PistonQueue expects.
Solution: Add the required servers to your proxy configuration.
BungeeCord Example
servers:
main:
motd: '&1Main Server'
address: 127.0.0.1:25566
restricted: false
queue:
motd: '&1Queue Server'
address: 127.0.0.1:25567
restricted: falseVelocity Example
[servers]
main = "127.0.0.1:25566"
queue = "127.0.0.1:25567"Make sure the server names in PistonQueue's config match exactly (case-sensitive).
Possible causes:
-
Target server is down - Check
pauseQueueIfTargetDownsetting - Target server is full - Check reserved slots configuration
-
No players in queue - Use
/pq statsto verify -
Queue move delay too high - Check
queueMoveDelaysetting
Debugging steps:
- Run
/pq statsto see queue sizes - Run
/pq slotstatsto see slot usage - Check proxy console for errors
- Verify target server is running and accessible
Check these settings:
positionMessageChat: true # Shows in chat
positionMessageHotBar: false # Shows above hotbar
positionPlayerList: true # Shows in tab listAt least one should be true.
Possible causes:
-
Player has bypass permission - Check for
queue.bypass - Player is OP on proxy - OPs may have all permissions
-
alwaysQueueis false - Players skip queue when server isn't full -
Wrong source server - If using lobbies, check
enableSourceServer
Check:
- Player name is spelled correctly (case-sensitive for some auth systems)
- Ban duration format is correct (e.g.,
2d,12h,30m) -
shadowBanTypeis set to your preferred mode
Test with:
/pq shadowban TestPlayer 1m
Yes! Use queue groups to route different queues to different servers:
queueGroups:
survival:
targetServers:
- "survival"
queueTypes:
- "REGULAR"
- "PRIORITY"
creative:
targetServers:
- "creative"
queueTypes:
- "CREATIVE_QUEUE"PistonQueue is designed for a linear flow (queue -> target). For complex hub networks, you'll need to configure it carefully:
- Set
enableSourceServer: true - Set
sourceServer: "lobby" - Configure your lobby to send players to the queue server when they want to join the target
Reserved slots ensure each queue type has guaranteed space on the target server.
Example:
- Server max: 100 players
- VETERAN slots: 20
- PRIORITY slots: 30
- REGULAR slots: 50
This means:
- 20 slots are guaranteed for veterans
- 30 slots are guaranteed for priority players
- 50 slots are for regular players
If there are no veterans online, their slots can be used by others, but veterans will always have priority when joining.
Technically possible but not recommended. PistonQueue is designed for minimal resource usage with players locked in place. Making a "playable queue" causes:
- Increased server load
- Potential exploits
- More complex configuration
- No official support
- Download the latest version
- Stop your proxy and queue server
- Replace the old JAR with the new one
- Start your servers
- Check for config migration messages
The plugin handles config migrations automatically when possible.
Yes, PistonQueue works with Bedrock players through Geyser. No special configuration is needed.
Use PistonMOTD with these placeholders:
-
%pistonqueue_regular%- Regular queue size -
%pistonqueue_priority%- Priority queue size -
%pistonqueue_veteran%- Veteran queue size
(Queue type names are lowercase in placeholders)
Yes, edit queuePosition in the config:
queuePosition: "&6Position in queue: &l%position%"Available placeholders:
-
%position%- Queue position -
%wait%- Estimated wait time -
%server_name%- Server name
If you can't find an answer here:
- Check the GitHub Issues
- Join our Discord Server
- Include these details when asking for help:
- PistonQueue version (
/pq version) - Proxy type and version (BungeeCord/Velocity)
- Relevant config sections
- Error messages from console
- Steps to reproduce the issue
- PistonQueue version (