Set up Minecraft AntiServerClose by iAlturki on my own hosted Minecraft Java server. I want the AI agent to handle the full server-side installation and verification; nothing should need to keep running on my PC. Official project: https://github.com/iAlturki/Minecraft-AntiServerClose Handle the setup end to end using the tools available to you; do not stop at instructions I must carry out myself. Read the project's current README, security notes, and applicable local instructions first. Inspect my environment and any existing installation. Prefer the newest compatible official release; inspect the published asset names instead of guessing URLs. Verify a published checksum when one is available, and state honestly when none is supplied. Use a dedicated directory within my user profile and keep existing settings and data. Follow your tool permissions and approval rules. Ask only for information you cannot infer and approvals that are actually required. Prepare the concrete action before handing me a required sign-in, MFA, or admin approval, then resume the remaining work. Do not disable security protections, bypass browser warnings, accept new legal terms on my behalf, or delete unrelated data. Do not publish, share, or print passwords, tokens, device codes, or private logs. Verify the result through the application's real behavior when possible; distinguish what you tested from what still needs my interaction. Finish with a short report of the version, installed path, verification result, changes made, and exact rollback steps. Preserve iAlturki's credits and the applicable project and third-party licenses. Read docs/SETUP.md, docs/VERIFICATION.md, docs/TROUBLESHOOTING.md, and SECURITY.md from the repository. Identify my authorized server and existing version/mods/address from the connected hosting tools; ask only if you cannot infer the target or account. This beta supports Minecraft 26.3, Fabric Loader 0.19.5+, Java 25+, Fabric API, and Linux x86-64. Do not upgrade/downgrade my world or replace unrelated mods to fit it. Check the provider's current automation, sleep, and retention policies and explain material suspension/world-loss risks. Take and verify a world backup before installation. Stop normally, install exactly one compatible project JAR in mods, start once, and confirm the native diagnostic passes. Keep online-mode, the whitelist, and signed-profile verification intact. Use the real client-facing hostname with its explicit port; do not assume an allocated backend IP/port or port 25565 is correct. Configure only config/minecraft-antiserverclose/antiserverclose.properties with my own profile name and a bounded reconnect cooldown. Explain the server-stored credential cache and obtain my explicit consent before enabling authentication-approved. I must personally complete Microsoft's device login, account choice, and MFA; never ask me to paste a password or token into chat. Monitor the fresh login prompt privately, then verify the authenticated name and real player-list join. Preserve my position, health, inventory, and game mode. Verify a same-account human handover and return after logout when possible. Run an idle test longer than the host's threshold with the panel closed and no periodic renewals/pings during the test; a ping alone is not proof that a friend can join. Report any real-client check that still requires me. The mod cannot renew provider deletion deadlines or restart a terminated container; do not claim universal 24/7 hosting. For rollback, disable the bot and stop it, remove only its JAR, and remove its account cache only after the child is stopped. Do not delete or blindly roll back the world or other players' files. Do not install stop-blocking mods, bots on my PC, or a paid service. Project creator and maintainer: iAlturki. Setup prompt © 2026 iAlturki, CC BY-NC-SA 4.0.