HajduNet Evony setup guide

For the invited person

New user — your steps

Follow B1–B5 for your own account and phone. Your administrator handles the separate invitation and approval steps above.

Use your own HajduNet website account and your own Tailscale account. Your existing Evony game login stays on Android; you do not create a new game account in this guide.

B1. Create your HajduNet account

1. Open your complete invitation link in a current browser on your own phone or computer. If it says that someone else is already signed in, use the invitation page’s Sign out link first.
2. Check the recipient email and expiry. Choose a username of 3–64 letters/numbers or ._@-, and your display name.
3. Select Create my passkey & account. Follow your phone/computer’s passkey prompt, using its screen lock, fingerprint or face verification. Save the passkey where you normally store passkeys.
4. You are signed into your empty Evony workspace. Add device, Setup guide and Set up my PIN are available. No one else’s game devices appear.
5. For later visits, open HajduNet, enter your username if needed and select Sign in with passkey. Another computer needs access to your passkey provider or the browser’s cross-device passkey flow.

Your passkey signs you into the website. Your separate HajduNet control PIN approves Live changes. Neither is your Android screen-lock PIN or your Evony password. Do not send any of them to your administrator.

B2. Prepare your Android phone

Use a spare/dedicated phone if possible. ADB gives the trusted HajduNet server debugging access to Android, including screenshots and controls beyond Evony; it is not an Evony-only permission on the phone.

1. Install/open Evony, log into your own game account and finish any initial tutorial yourself. Use portrait orientation. Keep the phone charging, on reliable Wi-Fi and with Evony open while the bot runs.
2. For the simplest wireless setup, use Android 11 or newer. Check Settings → About phone → Android version.
3. Find Settings → About phone → Build number. On Samsung this is usually inside Software information. Tap Build number seven times and enter your phone’s screen-lock credential if asked.
4. Return to Settings and open Developer options (sometimes under System). Turn it on. Enable USB debugging if you will use a USB cable/PC; approve only a computer you trust.
5. For Android 11+, enable Wireless debugging on your trusted Wi-Fi network. Its IP address & port is the connection port. Pair device with pairing code shows a separate pairing port and six-digit code. Do not confuse the two.
6. Complete B3 and wait for your administrator’s approval. When you reach B4, reopen the pairing-code popup for a fresh code and leave it open while Debian pairs. Do not email the code or post screenshots containing it.

Developer-option names vary by manufacturer. See Android’s developer-options guide and wireless ADB instructions.

Check the automation profile

Current automation templates are calibrated for 1080 × 1920 portrait. Add device reports the actual capture resolution. A different-size phone can be enrolled for viewing, but Gather/Auto-join need a matching calibrated profile before they work. The website does not silently change your phone’s resolution or assume scaled templates are safe. Ask your administrator to verify the profile before using Live automation.

B3. Connect Tailscale and share your phone

1. Install Tailscale from Google Play. Sign into your own Tailscale account, approve its VPN configuration and leave it connected. No exit node is needed.
2. Open your Tailscale admin console in a browser. Under Machines, find this Android phone and select … → Share → Copy invite link. Send a single-use share link privately to your HajduNet administrator.
3. Keep Tailscale connected. Wait while the administrator accepts your phone share and approves its address for your website account.
4. Continue to B4 once they confirm approval.

Hand back to the administrator: they now complete A2. You share your phone with them; they do not need to share the server back with you.

Install Tailscale on Android · Share a phone. Tailscale access and website device ownership are separate permissions.

B4. Add your phone to HajduNet

1. Sign into your own HajduNet account and select Add device.
2. Select Tailscale → Next. Only your approved phone is offered. If it is missing, ask your administrator to complete A2, then retry the wizard.
3. Enter the approved 100.x.x.x address and the phone’s connection port. For modern Wireless debugging, use the current port shown by Android, not 5555 automatically.
4. Expand Android 11+ pairing, if required. Open the phone’s pairing-code popup, then enter its current pairing port and fresh six-digit code. The website gives the code to Debian’s ADB and does not save it. Pairing your PC does not pair Debian.
5. Select Test & show screen. This checks connectivity, identity and a screenshot. It does not tap the game or start automation. Approve a debugging prompt on the phone if one appears, then test again.
6. Confirm that the preview is your phone and check its native resolution. Give it a useful name, then select Connect & open screen.
7. The device is saved under your ownership in Dry Run. You can configure and control your own device after PIN setup. No other person’s devices are granted to you.

Android’s documented wireless setup uses the same Wi-Fi network. Direct access through the phone’s Tailscale interface depends on the phone/vendor and is a connection test, not a guarantee. If pairing over Tailscale fails, use the USB/PC preparation below with your administrator’s help; do not open ADB to the public Internet. Reboots or Wi-Fi changes can change/disable wireless debugging and require updating the connection.

B5. Set your PIN and choose an operation

1. Open Account settings (or Set up my PIN on your empty workspace).
2. Enter and confirm a personal 8–12 digit PIN. Choose a non-obvious value. Select Verify passkey and save PIN, then verify your own passkey.
3. Return to Evony and select your device. Tap the mode/control button at the top, enter your PIN when prompted and choose Live. Read the separate labels for browser controls and running activity.
4. Gather: choose resource, preferred/minimum level and maximum marches; save the settings, then select Start gathering. A maximum of 0 means all available slots. Full capacity waits for a slot; no marches out is supported.
5. Auto-join: set your monster exclusions and select Start auto-join. Gather and Auto-join do not run at the same time on one phone.
6. Auto-hunt: not yet available for live hunting. Account permissions do not make an unfinished feature work.
7. Manual: the hand button toggles manual control. Taking manual control stops the active task. Use it deliberately, then restart the desired task afterward.

Live includes keep-alive, watchdog and supported popup recovery. Dry Run sends no game input and does not run Live recovery. Closing the browser or letting its control PIN approval expire does not stop an already-authorized background operation. Unlock again to make changes. Another browser has its own approval; ordinary tabs sharing one login share that browser session. Controls lock after five minutes of inactivity, with an eight-hour cap. Changing/revoking the PIN, choosing Dry Run, Emergency Stop or an explicit Stop can stop activity.

Unknown popups can still require help. Use the screenshot button to save a native screenshot on the server for template work; use Save debug snap for an incident. Keep private phone notifications out of captures you share.