Skip to main content

Frequently Asked Questions

These are a few commonly asked questions and their answers. You can use the bar on the right to skip to your question.

How do I set up a queue?​

You do not need to set up each server for a queue, queues are automatically created for a server. All you have to do is set player to join them using the queue command (/queue <server>, /joinqueue <server>, or /joinq <server>).

ajQueue should work fine out of the box. You can look through the config and change things if you want to, but it is not required for a basic queue.
However, I would recommend either disabling the /server command for players (usually by denying the permission in your proxy permissions plugin) or replacing the /server command with the queue command. If you don't do either of these, players will be able to bypass the queue by using the /server command.

Why does the queue not work? I just get sent to the server instantly!​

If you join a queue, its empty, and nobody was just sent to the server, then you will get sent instantly. It will not do this when there is more than one person in the queue (or if the server is offline/full/restarting/paused/restricted etc)

I set my server selector or npc to execute the queue command as the player, but it says unknown command!​

If the queue command says unknown command when executing on a server selector, npc, or something similar, this is probably because its trying to execute the queue command on spigot, when the queue command is on the proxy. If you install ajQueue on the spigot server too (its the same jar), then ajQueue will forward the command to the proxy for you.

How can I temporarily not get auto queued to a queue-server​

If you need to stay in a server that is set up as a queue-server in the config, you can use the /ajQueue pausequeueserver command to temporarily disable queue servers for yourself.

You can repeat the command to re-enable normal queue-server behaviour for yourself.

Players can do queue commands before logging in with an auth plugin!​

This issue is the responsibility of the auth plugin to solve. Usually you just need to install an extension on the proxy. Check the documentation and/or contact the support of the auth plugin to find the solution for the auth plugin you use.

This issue would not only affect ajQueue. It would affect any proxy command (including the normal /server)

Do I need to install ajQueue on all of my backend servers?​

You only need to install ajQueue on the backend server(s) if you want to use one of the following features on that server:

  • Whitelist detection (Only needs to be installed on the whitelisted server)
  • PlaceholderAPI (only needs to be installed on the server you want to use the placeholders on)
  • Command forwarding (only needs to be installed on the server you want to forward commands from)

If you do not need any of these features on a specific server, you do not need to install ajQueue on that server. Even if you do need them on another server. You only need to install ajQueue on the backend server that you want to use one of the above features on.

How do I set a per-permission player cap?​

ajQueue does not provide this feature.

The closest you can get is to give some players the ajqueue.joinfull permission, which along with another plugin on the backend server (such as Essentials and its essentials.joinfullserver permission) will allow that player to join the server even if its full, but there is no cap on these extra players.

ajQueue says that my server is offline, but its not.​

If ajQueue is saying that your server is offline, but you can join by going around ajQueue, then usually the server just cannot be pinged for some reason.

The most common cause of this for minecraft servers 1.16 and above is enable-status being disabled in server.properties of the target server. For ajQueue to be able to detect the server, enable-status must be enabled.

If your server is on an older minecraft version or enable-status is already enabled, then most often it is a plugin on the backend server that is blocking pings.
Try running the backend server without any plugins and see if ajQueue can detect it then. If it can, it is one of the plugins on the backend server. Usually this is done by "security" plugins.

Here are some known plugins that block pings:

  • SafeNET. Can be fixed by disabling block-ping in SafeNET's config.
  • CoffeeProtect
  • better-compatibility-checker (forge mod)

If you have one of the above plugins, try without it. If trying without it fixes the issue, you should go to that plugin's support. (other than SafeNET. First try disabling block-ping in its config)