What's new with Wandering Bot?

Nasdara now has its own town, city and village catalogue, so valid coordinates resolve to a Nasdara place instead of Location unavailable. Labels use straight-line distance from the mapped settlement centre, with the original coordinates retained. The lookup follows the selected DayZ server and works offline. New messages use the improved labels; existing messages keep their original text.

Where to find itDiscord: Nasdara flag-raised, flag-lowered and supported event feeds. Dashboard: select the Nasdara server profile.

Add exempt usernames and tick exempt Discord roles, then save Stack Watch. Exempt placements do not contribute to its trigger count, post its alerts or receive its bans. Role exemptions use the player's linked identity for that server; exact username exemptions work without a Discord link. Older Stack Watch ban buttons check current exemptions too. When linked role membership cannot be verified, automatic bans are held for staff review. Each DayZ server keeps its own selections.

Where to find itCustomer dashboard: Admin Center → Moderation → choose the DayZ server → Stack Watch → Exempt players and roles → Save Stack Watch.

When the bot returns before the scheduled request window closes, it checks the server's current schedule and protected delivery work before continuing. Duplicate-request protection stays active after an attempt. Restarts whose request window has passed are held for staff review rather than sent unexpectedly late.

Where to find itCustomer dashboard: Admin Center → Server Control → Scheduled restart and restart history.

Billing & subscriptions is available in the customer dashboard, with a Manage or cancel subscription shortcut on Start Here and Upgrade. The same public billing page is available when dashboard access is locked. Use the email from your payment receipt, select the subscription and review its cancellation date before confirming. Opening the portal alone changes nothing. Free plans have no recurring charge to cancel.

Where to find itCustomer dashboard: Billing & subscriptions → Manage or cancel subscription. Website: /billing/manage. Billing recovery: Manage or cancel existing subscription.

New server connections begin with Choose your hosting provider instead of selecting one automatically. General application and whitelist help stays provider-neutral, while your server's guidance names only its selected host and explains which whitelist actions that connection supports. Host-specific fields stay hidden until that host is selected. Existing connected profiles keep their saved host and credentials.

Where to find itCustomer dashboard: Admin Center → DayZ Server Connection and Commands & setup help. Discord: /applications help, /applications server and /whitelist help.

The private form asks for a PSN on PlayStation, an exact gamertag on Xbox, or an in-game name and 44-character DayZ UID on PC. Staff approve once to link the player, update selected servers' supported enabled whitelists with the correct identifier and grant the configured roles. Choose servers on one platform per application. PC uses the DayZ UID from ADM/RPT, not a SteamID or BattlEye GUID. Automatic whitelist availability follows the selected host connection; file-based/Expert Mode writes are not included. Existing PlayStation applications continue to work.

Where to find itDiscord: /applications help, /applications server and /applications panel. Website and dashboard: Commands & setup help.

A visible invitation on Start Here makes it easier to leave an honest review of the bot or dashboard without waiting for a reminder. Maybe later snoozes invitations for seven days in that browser. Communities that have already reviewed are not prompted again; their review can still be updated in Reviews. The review form and the rest of the dashboard remain available normally.

Where to find itCustomer dashboard: Start Here → Write a review, or Reviews in the menu.

Configure your reviewer and Survivor roles, choose the actual host for each supported server profile and add its map role, then publish an application panel. Staff approval links the submitted identity, checks selected servers' whitelist requirements and grants the player roles. Existing identity links and alternate names on other profiles are retained separately. Staff and applicants receive the result, including incomplete steps. A server with whitelist enforcement off keeps that setting.

Where to find itDiscord: /applications help, /applications configure, /applications server and /applications panel. Website and dashboard: Commands & setup help.

Connecting a server gives clearer guidance when the selected host is busy, access is denied or no DayZ service is found. Retry connection reuses the token in your current setup session, and Manual service ID is available for supported API connections when the account's service list cannot find your server.

Where to find itDiscord: /setup → Selected host connection → Retry connection or Manual service ID where supported.

Choose your DayZ server in Leaderboards, set Show global leaderboard to Off and save. The Discord board updates on the next automatic check, usually within a minute. Your player statistics keep updating, other servers keep their own choice, and you can turn the global board back on at any time.

Where to find itCustomer dashboard: Leaderboards → Discord leaderboard display → Show global leaderboard → Save leaderboard display.

Free dashboard access starts when the bot joins your Discord, before connecting the DayZ host. Existing starter records with no saved plan are repaired when the bot reconnects. Your private login and saved server setup are retained, and an existing paid plan or deliberate access lock is respected.

Where to find itWebsite: Add Wandering Bot. Discord: private setup and /dashboardcredentials.

New Discord heatmap images keep the terrain and activity markers visible through the bottom edge of the map.

Where to find itDiscord: Nasdara heatmap feeds.

The public website asks before loading analytics. Rejecting keeps the site available, and Cookie choices at the bottom of the page lets you update your decision. Private dashboard, owner, player and payment pages are excluded.

Where to find itPublic website: analytics notice, Cookie choices and Privacy Policy.

Killfeed, Discord bot and shop pages show a real privacy-safe example and the steps for that service. The shop guide explains the separate companion, existing wallets and catalogue, player access and delivery checks. Loot maps and file guides link to relevant server-owner tools, while the written setup guide includes the existing setup video.

Where to find itWebsite: DayZ killfeed, Discord bot and shop pages; Loot maps; DayZ files explained; Setup guide.

Running /linkgamer from another channel sends its public confirmation to the selected server's gamer-link destination. Server owners can choose that destination in Feed Routes, including when they use a custom channel name. Missing or conflicting destinations show a clear setup message before a link is changed.

Where to find itDiscord: /linkgamer. Dashboard: Admin Center → Feeds → Gamer-link confirmations.

The website shows the main bot's current registered commands with plain-language explanations and search. In your customer dashboard, Help & Guides filters that list for your Discord's configured server platforms. The guide also walks through crafting and illness panels, the Wandering Shop trading board and private player-to-staff tickets, including which bot and permissions each needs. Existing server settings and channels are unchanged.

Where to find itWebsite: Commands & setup help. Customer dashboard: Help & Guides.

There is no extra channel-creation command to find after payment. Existing server layouts and owner-selected routes stay untouched. The private setup still guides the owner through connecting their DayZ server before live feeds can populate.

Where to find itDiscord: add Wandering Bot, activate the subscription for that server, then check the new channel pack and private setup channel.

Existing customer channels are not bulk-renamed, and the bot still recognises plain and stylised names when reconnecting feeds.

Where to find itDiscord: newly created Wandering Bot channels and categories.

Server admins can choose a feed from the list and see whether it is currently on or off. Typing part of a name narrows longer lists; exact feed keys are no longer needed. The command, saved feed settings and channel routes stay the same.

Where to find itDiscord: start /togglefeed, select the feed field, choose a suggestion, then set enabled to true or false.

Players can subscribe to the complete pack as one mod. Server owners request a private, revocable approval for their own DayZ PC server; players do not enter the code. The website shows real in-game screenshots and a playable DayZ showcase video alongside the Workshop download and Discord support ticket. The decorative vest cylinders remain visible when functional charges are removed.

Where to find itWebsite: PC Mods → Suicide Bomber pack. Server owners open a Discord ticket for an approval code and setup instructions.

The public board shows recruiting factions and read-only member lists. A request for a new faction stays private until a Community Admin reviews it and completes the existing setup wizard. Official faction membership and roster changes are controlled by community admins; faction leaders and officers cannot edit the official roster. Existing private chats and player-created groups remain separate.

Where to find itDashboard: Factions → Shared Discord Faction Hub. Publish the board in an existing community-factions channel and choose the approver role. Players use the board's Join or Request a new faction buttons.

The panel uses the same illness and crafting libraries as the website and app. Players can search symptoms, conditions, cures and recipes without spending AI credits. Stable DayZ 1.30 crafting additions and corrections are included with their review dates; older entries keep their earlier review labels. It is in-game DayZ guidance, not real-world medical advice, and modded servers may differ.

Where to find itDiscord: an owner or authorised community admin runs /survivalguide in an existing text channel. Players use the panel buttons; rerunning the same section refreshes its saved message.

A server manager can place one reusable trading board in a shop channel. Players can post an offer, browse listings and mark their own listing sold or withdrawn. Each offer names its DayZ server; pictures appear on the individual listing posts. Exchanges are arranged between players: the bot does not take payment, hold items, verify ownership or deliver a trade. Existing shop balances, catalogue items and settings are unchanged.

Where to find itWandering Shop: server managers use /trade panel to post the board; players use its buttons or /trade list. This is one new command in the separate Shop app, not the main bot.

Check your bank balance, virtual wallet and history, then deposit or withdraw through wallet or physical cash mode. Wanderbucks come in 1, 5, 10, 50, 100 and 500 denominations, with server-issued serials and duplicate protection. Interrupted uncertain transfers are held for review instead of automatically reminted. Bank requires Wandering Ops, verified Steam linking, a supported private file connection and separate owner-issued Bank access. Physical cash needs explicit owner approval for that PC profile. It connects to Wandering Bot banking only. The website includes two in-game ATM photos and a clearly labelled detailed six-note artwork preview.

Where to find itWebsite: PC Mods → Bank & Wanderbucks. Open a Discord ticket for your server code and setup; owner dashboard: PC Mod Keys and the selected PC profile's physical cash setup.

Wandering Collectables includes all 28 creature cards. The Creature Archive Binder stores the complete collection in 28 card-only cells and requires the cards pack. Wandering Eggs adds four Dinosaur and four Dragon storage eggs, each with 50 cargo cells and a switchable battery-free glow. The PC Mods page keeps the download links, dependencies and separate private server-code instructions together. Players subscribe normally; server owners open a Discord ticket for their mod's private, revocable activation code.

Where to find itWebsite: PC Mods → Cards, Binder or Eggs. The homepage links to the full collection; the owner dashboard's PC Mod Keys page manages approvals.

Wandering Ops brings admin tools into DayZ: player and map controls, freecam, persistent object placement and removal, item spawning, presets, bank controls, and an on-screen killfeed. Admin actions remain permission-checked, and the client and server need matching signed mod files. Access codes are issued for a specific server; installing the Workshop item alone does not unlock the panel.

Where to find itWebsite: PC Mods → Wandering Ops, with feature screenshots and setup details. Open a support ticket if you want an access code for your PC server.

Each server profile gets its own next-check time and rate-limit cooldown, while requests through the supported provider API still share protective pacing. The normal target is one check about five minutes after that profile's previous scan finishes; queue and scan timings are logged so we can see when capacity is strained. This is not an instant-feed promise: a kill or death can only reach Discord after the host makes the relevant log available, and provider rate limits can still delay a retry.

Where to find itDiscord: /admstatus shows your selected server's feed status. Dashboard: check the selected server profile and its ADM connection if a feed is late.

An administrator who selects Yes gets a private admin news channel following official Wandering Bot announcements. The most recent earlier published announcement is copied with its original date, so a newly subscribed server can catch up without receiving an undated old offer. No server receives offers just for installing the bot, and an administrator can unsubscribe later.

Where to find itDiscord: /setup → Official news and offers. To change it later, use /server companynews subscribe, status or unsubscribe.

The guide explains the difference between a hosting-account password and the narrower connections a server may actually need. It covers private provider tokens, BattlEye RCon, FTP, FTPS and SFTP, staff permissions, credential rotation, and separate server profiles without treating every community as a single-provider setup. It also explains that available controls depend on the selected platform, provider and connection type.

Where to find itWebsite: Guides → Protect your DayZ server credentials. No existing server connection needs to be reconfigured.

Each request creates a private channel visible only to that player and the Discord server's configured staff. Staff can claim it, resolve or approve it, close it without hiding the conversation from the requester, and reopen it when more information is needed. Ban and unban categories request a staff review; they never apply a ban automatically. The old faction text command remains as a compatibility shortcut. This server-community system does not use the Wandering Bot customer-support inbox: /supportbot remains a separate admin-only route from a server owner to the Wandering Bot owner.

Where to find itDiscord: players use /ticket and choose a category. Administrators use /ticketpanel in the public help or server-tickets channel to post the reusable button.

The PC setup wizard asks for your host directly. Compatible PC profiles can use their own host's BattlEye RCon details for live controls and verified-GUID game bans, with separate FTP, FTPS or SFTP details for server files and ADM/RPT feeds. File-only PC setup is possible, but game bans need BattlEye RCon. Dashboard, moderator and supported automatic safe-zone bans target the selected PC server through BattlEye. Availability depends on the exact host plan and its exposed connections: provider API power controls and automated whitelists are not available on every host. PC bans are not automatically copied to other servers; Ban Network sharing and application remain owner-controlled.

Where to find itDiscord: /setup → choose PC and your host. Dashboard: Server Connection and PC RCon Control. Website: homepage and setup guide. Confirm RCon and file access in your own host panel before using live controls.

Android could close the WebView before its most recent HttpOnly login cookie had finished writing, and an incompletely configured server process could fall back to a temporary signing key. The app now explicitly flushes the protected cookie jar when it is backgrounded. The backend also derives a private, purpose-specific stable fallback from an existing server credential when the dedicated cookie secret is absent. Passwords, Discord OAuth tokens and provider credentials are still never stored by the native app.

Where to find itAndroid app 1.0.7: sign in once, close the app, then reopen it from the launcher. Normal 30-day expiry and an intentional Sign out still apply.

The Sandbox now classifies the requested outcome into Simple, Standard, File work, Complex or Advanced. Longer wording by itself does not increase the price. Any task above the one-credit Simple tier shows its exact credit cost and reason first, then waits for the customer to approve that unchanged signed quote. Failed model answers, protected-file refusals and clarification-only responses remain free. The same model is used regardless of the customer's remaining balance; the bot does not deliberately make mistakes to sell more credits.

Where to find itDashboard: AI Sandbox → enter a request. Review and approve the displayed quote when the work is above the Simple tier.

A long-running worker could continue displaying an older saved figure after another Wandering service changed the wallet. A few map-profile reward paths could also form a separate profile-scoped key. Wallet reads now refresh protected cross-worker data, and every DayZ profile in the same Discord community resolves to one community-and-player wallet. Existing money-history protection remains in place, and differing old records are not silently added together or overwritten.

Where to find itPlayer Hub: Wallet & bank → Refresh balance. Discord economy and Shop actions use the same community wallet automatically.

Android can keep the app activity alive after it has been moved into the background. A fresh launcher tap now recognises that launch separately and returns to Home. Deliberate faction-notification links still open the protected faction route, and normal in-app navigation is unchanged.

Where to find itClose or background the app on any library page, then tap the Wandering Bot launcher icon again.

The Player Hub now merges the latest saved community setup with the running bot's view. If an existing signed app session has no matching community, Wandering Bot performs a narrow live membership check only against configured active communities. The Discord OAuth token is still not stored, unrelated Discords are never enumerated, and membership does not grant server-admin permissions.

Where to find itPlayer Hub: sign in with Discord or reopen the app after joining a Discord that already has Wandering Bot configured.

When a relevant mapgroupproto group contains custom category, tag, usage or value names, Wandering Bot now validates them against that mission's live cfglimitsdefinition.xml. The bundled vanilla list is no longer treated as the complete allow-list for a customised server. If the read-only limits file is temporarily unavailable, unrelated existing custom names are preserved rather than blocking the vehicle transaction; files being changed still pass the normal protected-write and final verification checks.

Where to find itDashboard: Airdrops & Events → create or retry a vehicle/event upload. Existing custom loot taxonomies remain untouched.

Discord sign-in continues to open the player hub, where a recognised Discord role can use a small set of quick staff actions. It does not replace the server's private dashboard login. A new Full admin login button now takes staff to the Dashboard ID and password screen even when they are already signed into the player hub. Once signed in, the mobile command centre includes a Full dashboard link and an All dashboard tools card, so administrators can reach every page their saved server login permits. Existing plan, server and temporary-login permissions still apply.

Where to find itApp welcome: Server admin login. Player Hub header: Full admin login. Mobile command centre: Full dashboard or All dashboard tools.

The Wandering Ban Network is a staff intelligence feed, not an automatic global ban list. Each report shows the DayZ name, platform, source server, date, violation, whether staff or an automatic protection issued it, and the relevant ADM/RPT evidence excerpt when available. Another server must review the report, select its exact server profile and confirm before Wandering Bot queues a permanent local ban. Player identities cannot be copied across different platforms. PC BattlEye GUIDs remain private on the server and are never displayed in the dashboard. Removing or expiring the source ban removes it from the active feed, while the audit history remains intact; it does not silently undo a local ban another owner already chose. The homepage includes a clearly labelled fictional demonstration so owners can see this review flow before signing in.

Where to find itDashboard: Ban Network. Turn on sharing for your community if you want future successful Wandering Bot bans to appear; viewing and applying reports are separate choices. Homepage: Shared safety · owner choice.

Each server profile now has a clear restart authority choice. Where the provider connection supports it, provider mode reads active restart tasks, uses their next reported run for Discord warnings and shop safety, and does not issue a second scheduled restart. Scheduled vehicle resets can prepare for the next suitable provider restart and wait for evidence that it ran before restoring the normal vehicle economy settings. Existing profiles stay on Wandering Bot mode unless an owner changes them.

Where to find itDashboard: Admin Center → Restart & Damage → Restart authority. Keep the schedule enabled so warnings and restart-aware tools can follow the selected source.

The bundle editor now includes starter, BDU patrol, medic, base-building, hunting and vehicle-maintenance recipes. A recipe only becomes selectable when its exact item classnames exist in the selected server catalogue, and it fills the editor for review rather than silently publishing anything. Saved bundles are re-read from the shared shop file so the Shop bot can see them without waiting for a service restart. In /shop open, players can add up to 12 different products, choose quantities, remove items and send the basket to one delivery location at checkout. The server rechecks every item and the combined price before accepting it. DayZ magazine classnames now have their own Magazines category instead of being mixed into Ammunition.

Where to find itDashboard: Shop & Economy → bundle editor and catalogue. Discord: /shop open → Add to basket → Basket → Checkout.

The Reviews section is available throughout the customer dashboard and supports separate feedback for the Discord bot or the dashboard and app. New reviews require the server owner to choose PC, Xbox, PlayStation or Nintendo Switch 2, so public feedback carries a clear platform label. If a community has not reviewed yet, a small non-blocking reminder can appear after 30 seconds of normal dashboard use. It appears at most once per browser session, Maybe later snoozes it for seven days, and submitting a review stops future reminders for that community.

Where to find itDashboard: Reviews. The reminder works across PC and console server profiles; it does not interrupt setup or require players to submit feedback.

The public PC demonstrations are still clearly marked examples with fictional server and survivor names, but their header branding now matches the real bot and app. This is a presentation fix only; it does not change RCon credentials, permissions or live server controls.

Where to find itHomepage: Platforms & PC RCon → open the Dashboard or App demonstration.

PC setup separates the server host from the connection method. Choose your provider, another compatible host or self-hosting. BattlEye RCon supplies the current roster and protected staff actions such as broadcasts and kicks. Optional SFTP, FTPS or FTP access supplies ADM/RPT feeds, mission/mod scans and protected file tools. API power controls require a supported provider connection; they are not universal. Passwords and file credentials stay private. PC Cheat Guard auto-bans are opt-in and fail closed without exact current evidence and a matching RCon player. Mission and mod types.xml scans build verified catalogues for supported PC tools. Map choices include Deer Isle, Namalsk and Esseker alongside official maps. Console communities keep their platform-safe workflows.

Where to find itDiscord: run /setup, choose PC and your provider, then use PC host files and PC RCon / Advanced. Dashboard: Server Connection or PC RCon Control. The app uses the same permission-checked PC controls.

This is the server join whitelist, not a zone exemption or queue priority. It requires a supported provider API connection. Existing players are preserved and the saved result is checked with that provider. Adding a name does not enable restrictions. Enable and disable are separately confirmed actions requiring a stopped server; the bot does not stop or restart it. Use exact console names or a 44-character DayZ UID for PC. If settings cannot be identified reliably, manage them in your host panel instead.

Where to find itIn Discord, use /whitelist help, then /whitelist status, /whitelist list, /whitelist add or /whitelist remove. Requires Manage Server or Administrator. Select the correct server; new players do not have to join first. Dashboard: Admin Center → Restart & Damage → Server whitelist instructions.

A completed handover could still look inactive when the dashboard read a DayZ profile instead of the shared Discord settings. That's fixed. The cards confirm installed companions, show active or saved handovers without asking you to activate again, and explain when installation cannot be verified. Installing a bot alone does not switch handlers; existing permissions and fallback safeguards stay unchanged.

Where to find itStart Here → Wandering Bot Family. Refresh the dashboard; you do not need to repeat a handover you already saved.

Alright, a nice bit of progress on the faction stuff! I've got a real test notification coming through to the Android app now, and I've saved a picture below so you can see it. It keeps the notification itself simple — no base coordinates or private faction messages sitting on someone's lock screen. There's still testing and an updated app release to do before everyone can use phone alerts. Base alerts will follow the server logs, just like the Discord alerts; I won't be calling them instant.

Where to find itPreview only for now. Phone notifications are still switched off on the live bot; I'll update this page when they're ready to use.

Some older wallet records could leave a long number where a member's name should be. New leaderboard posts now check Discord for the member's name. I've also cleaned up name fallbacks in wages, dashboard member and faction lists, channel selections and audit messages. If Discord can't provide a name, you'll see a clear name-unavailable label instead. Balances, permissions and saved destinations stay unchanged.

Where to find itRun /economy leaderboard again for a fresh result, or refresh the dashboard. Messages already posted in Discord are not rewritten.

This is for communities across Wandering Bot, not just my own server. Members sign in with their own Discord account, and the faction owner can choose app-only chat, link a private Discord channel, or leave it off. Linked chat can go both ways between the app and Discord. Faction access and channel permissions still apply, and each community's rooms stay separate. Base alerts need the relevant radar setup and plan — this doesn't unlock paid radar features on a free server.

Where to find itPlayer hub → Faction chat & base alerts, or open /app/factions and sign in with your own Discord account. Owners enable rooms under Community setup and assign the matching faction Discord role. The homepage now has demo screenshots and separate joining instructions for owners and players.

Demo conversations, actual interface. The screenshots below use fictional members and messages. The open hub checks for new messages about every 30 seconds; these are not instant-delivery claims.

01 / Discord-linkedChat across the app and Discord

02 / App-onlyA conversation just for your crew

A drawn zone could still show a spare 250m circle-radius value in the editor and Discord save message. The boundary checks already use the polygon, not that radius. I've hidden the circle controls in drawing mode and changed the zone list and future save confirmations to show the drawn boundary and point count. Your existing outline and zone rules are not changed, and old Discord confirmations are not rewritten.

Where to find itZones & Radar → Draw an area. Circle mode keeps its normal radius controls.

The map zooms towards the point under your cursor, within the existing 100–800% range. Right-click dragging, left-click drawing, the zoom buttons and Reset still work. Zooming changes only your view, not your boundary or zone rules. Scroll outside the map to move down the page; touch scrolling is unchanged.

Where to find itZones & Radar → the interactive zone map. Refresh the dashboard to load the updated controls.

You can now pan the map by holding the right mouse button and dragging, like an editor. Left-click still draws zone points or adds an airdrop location; scrollbars and touch scrolling stay available. Zoom and Reset stay above the map, and moving the view does not alter your drawn boundary or saved locations.

Where to find itZones & Radar, and XML & Loadouts → airdrop map picker.

Want the whole map safe but the airfields open for PvP? You can now link PvP exceptions to your safe zone. Both players must be inside the same exception. Shooting across the boundary either way still follows the parent safe zone's combat rule. If the logs don't give us both positions properly, it goes for staff review instead of a guessed ban.

Where to find itZones & Radar → PvP exception inside a safe zone → choose the parent and draw your area. Existing PvP zones aren't converted automatically.

You asked if you could hide the location without breaking the heatmap — you can now. Turn off death-feed locations for the selected server and new Discord death posts won't include those coordinates or map links. The underlying logs and heatmap data stay intact. It doesn't rewrite old posts or hide locations in unrelated feeds.

Where to find itLive Feeds → Discord death-feed locations → Off → Save death-feed privacy.

I've sorted the case where the last event ended but its territory entry stayed in the files. Cleanup now checks those bot-managed entries even when there are no active events left. Failed cleanup stays queued for another attempt instead of being called finished. This removes future spawn definitions; it isn't an instant delete of creatures already in the running game.

Where to find itExisting event end, disable and restart-count cleanup workflows. Unrelated server territory entries are preserved.

If your community uses Free Bot, your administrators can now sign in with their existing Dashboard ID and password. Paid communities keep their access too. The tools inside still follow your plan and staff permissions — this opens the app login, not every paid feature. Player sign-in with Discord remains separate from admin access.

Where to find itOpen the app and use Server Login. Never share an administrator's dashboard password with players.

I've added the ignored-player and Discord-role controls to the zone editor, so you can change them after setting the zone up. They belong to that particular zone, not every zone on the server. Check the selections and save when you're happy with them.

Where to find itZones & Radar → edit the zone → ignored players / ignored roles.

Some players were getting an old location back even while using the command again. I've improved the refresh path for stale ADM locations. /mylocation still shows the recorded position, including height and age, rather than pretending it's live GPS. Orders still need a suitably recent, verified location when that delivery option is used.

Where to find itUse /mylocation on the main bot; shop delivery previews use the shared location checks.

I've tightened up the shop edit windows so they're easier to use on smaller screens, with compact tabs and save controls you can reach. Wandering Boy has had his movement and layout updated too, including fixes for getting in the way of dashboard navigation.

Where to find itShop & Economy editors, and the Wandering Boy dashboard helper.

I've tightened up how the Sandbox picks its map and source files. Straightforward fresh-player spawn requests use exact reference positions, and a complete file you supply takes priority. It should ask when a request is ambiguous, not quietly swap in the wrong map. Drafts still need checking before you apply them to a live server.

Where to find itAI Sandbox → offline spawn-point drafts for supported maps.

There's been a fair bit of work on console deliveries: the Switch JSON delivery route, linked-player checks shared by the main and shop bots, and private location lookup. Shop JSON batches now have one-shot cleanup tracking so consumed orders can be removed while newer orders are kept. Keep an eye on the delivery and cleanup result — queued doesn't mean completed.

Where to find itShop ordering and delivery status. Platform setup and delivery requirements still apply.

You can now pick the Humvee when building a vehicle spawn event. Its classname is Offroad_02, so you don't have to go hunting for the name. As always, check the selected server, position and event settings before confirming it.

Where to find itAirdrops & Events → Event Builder → vehicle spawn choices.