Minecraft bots that stay online when you are not
QuietWork runs a Minecraft client on our own servers on your behalf. You link your Microsoft account, tell the bot which server to join, and it keeps doing the job you set while your PC is off.
How a bot is set up
You approve a Microsoft device code. We get a token for your account, never a password.
You enter the address the bot should join. It connects there and nowhere else.
The bot joins, runs the tasks you turned on, and rejoins itself if the connection drops.
What the bot does(16)
These are the tasks a hosted bot is built to run — the unattended, repetitive work you would otherwise sit at the keyboard for.
Eats once hunger falls past the threshold you set, so the bot does not starve unattended.
Watches for players coming within a set range and either warns you or logs the bot out.
Holds totems and pearls at the counts you pick while looting, dropping anything over.
Mines at a fixed yaw and pitch, holding the view steady while it works.
Picks the right tool for the block and swaps off one that is close to breaking.
Accepts incoming teleport requests after a delay you set.
Runs the server shop sell command on the interval you set.
Repeats a shop purchase for the amount and delays you configure.
Works through spawner loot a page at a time, in batches you size yourself.
Buys shulker boxes up to the amount you set, spaced out by a delay.
Drops spawners, shulker boxes or junk blocks to keep the inventory workable.
Breaks the spawner and stows it the moment another player turns up nearby.
Clears armor stands and chest minecarts that players use to box a bot in.
Keeps sprint held while the bot moves.
Rejoins the server after a disconnect, with nobody watching.
Reports weather changes back to your dashboard.
How we handle your account
Linking uses the Microsoft device code flow. You approve a short code on microsoft.com/link, in Microsoft’s own page. Nothing you type there reaches us.
The refresh token Microsoft returns is stored encrypted with AES-256-GCM. It is never written to a log, a launch argument, or a config file on the bot host.
The bot receives a Minecraft session over an authenticated socket, minted when it needs one and expiring on its own. Nothing long-lived is baked into how the bot starts.
A bot only ever connects to the address you set on it. Removing the account link from your dashboard stops every bot using it.
Contact
Questions about how the service authenticates, or a report about how it is being used: quiettonez@gmail.com
For everything else, we are on Discord.