FAQ

#Allay doesn't answer. What now?

Ask as an operator: the hint under the error says what to fix. Then:

Run /allay status. It shows whether a key, a subscription, or a self-hosted backend serves the server.
With your own key, check that the model can call tools. Allay looks into the game through tools, so a model without them won't work.
With a subscription, check that it's paid and under its limit. /allay link pays again with the same license.
With your own backend, check server.url, that the backend runs with SELFHOSTED=1, and that server.token matches its PLUGIN_TOKEN. Allay Server 6.0 refuses a plugin without it.

When the backend restarts or is busy, a question goes again up to 3 times, 15 seconds apart, and the asker sees “Allay is restarting or busy; trying again…”.

#Players get “Allay is set up wrong on this server”

The quota config is wrong: a weight in quota.tiers isn't a number above 0. Admins see what's wrong when they join. See Paying for the model.

#Can a regular player get items through Allay?

No. Tools that give items or change the world go to operators only, and the plugin checks three times. Automation agents only move a player's own things between containers they could open, and craft only from real ingredients. The one exception is [Take the book]: the written book with Allay's own long answer, once per book.

#What does Allay know about other players?

Only what the asker's locator bar shows: a name, a distance, and a direction. Never their coordinates or inventories. Whoever hides from the bar by crouching, a pumpkin, or invisibility is hidden from Allay too, and vanished players stay hidden. See Integrations.

#Is my key or license safe?

Neither ever goes to the log or into chat, and /allay status shows a key masked. license.key stays out of config.yml, so you can share your config when asking for help. Don't share license.key itself: whoever has it uses your subscription. server.token is a secret too: blank it before you share the config. The key and the token go only to the backend's own address, never along a redirect to another one.

#What does Allay keep about players?

On the backend, per server: each player's conversation for a day after their last question, the facts it remembers until they forget them or a year after their last question, and the numbers of their questions for 400 days, with their name and UUID for the backend's admin panel unless they turn on full privacy (/allay privacy full on), which leaves only a pseudonym. Other servers never see any of it. /allay privacy tells a player the same, and /allay privacy erase erases it; an admin exports or erases a player's data on request with /allay privacy export|erase <player>. The backend's Security and privacy page has the details.

#Can players say no?

Yes. Before a player's first question, Allay shows what it sends and keeps, and where, and asks them to agree. Until they do, nothing about them reaches the backend and Allay doesn't answer them. The backend keeps the agreement per server (Allay Server 6.1 and newer), so each player is asked once; /allay privacy withdraw takes it back. On allay.chat, the notice names the GDPR and Spain's LOPDGDD and links the privacy policy. With your own backend it says that you keep the data; link your policy in privacy.policy_url. privacy.consent: false turns the notice off, for servers that ask their players another way.

#A player gets the wrong language

Run /allay locale <player> to see why. Players behind a proxy or a relay get the relay's country. The player can pick their own with /allay language. See Languages.

#Why doesn't the agent use my furnace?

It must be within automation.radius (32 blocks), in plain sight from where you stand, and in a place you could open. When something doesn't fit, the agent says why. See Automation agents.

#Does Allay run on Spigot?

Yes. It builds against the Spigot API, so it runs on Spigot, Paper, and their forks. Furnace experience goes to the player only on Paper. On Spigot it stays in the furnace.

#Where does Allay keep its data?

In plugins/Allay/: config.yml, lang/, license.key, players.json (each player's settings), quota.json, notes/, goals/, timezones.json, geoip/, and exports/ once an admin exports a player's data.