Something not working? Start here.

If this happens: The command is absent, says the app did not respond, or works in one Discord but not another.

Check first: Check /status, then confirm the correct Wandering bot is installed in this Discord and try its current help command. Ask an admin to check the bot's channel permissions and your role access.

Try safely: Refresh Discord and try again once. If only one command fails, record its exact name and error; if every command fails, report the Discord server and time.

What will not fix it: Reinstalling the bot or repeatedly changing permissions without identifying the failing command can hide the real cause.

If it persists: Send the command name, Discord server, channel, timestamp and screenshot without any token.

If this happens: A command described for a companion bot is not present on the main bot.

Check first: Confirm which Wandering bot owns the feature and that companion is installed and enabled for this Discord.

Try safely: Use /helpme for the main bot, or the relevant companion's help command. Ask your server owner which bot family is active.

What will not fix it: Inviting another copy of the main bot will not add a command owned by a different companion.

If it persists: Include the command name, installed bot names and a screenshot of the Discord app-command picker.

If this happens: Kills, rewards, restarts or another feed appear in general chat or a different server's channel.

Check first: In Admin Center → Feeds, select the affected DayZ server profile and inspect the route for that exact feed. Confirm the bot can view and post in the destination channel.

Try safely: Save the intended route, then trigger one new matching event and check where that new message lands.

What will not fix it: Moving old Discord messages or changing an unrelated feed route does not repair future routing.

If it persists: Send the feed type, selected profile, expected and actual channels, and one message timestamp.

If this happens: The server is online, but new kill, connect or activity messages do not arrive.

Check first: Check the selected server profile, connection health and /admstatus. Confirm the server is still writing new ADM/RPT data and that the bot's feed route is configured.

Try safely: Wait for one fresh, relevant game event and compare its time with the most recent processed log time. Allow normal reconnect/retry before changing files.

What will not fix it: A successful Discord connection alone does not prove the game host has produced a new log file.

If it persists: Provide the last good feed time, a new redacted ADM/RPT excerpt and the selected profile/map.

If this happens: The setup message asks for a Nitrado token or service ID that the owner does not have.

Check first: Confirm the DayZ platform is PC and the selected host/provider for that server profile is correct.

Try safely: Use the PC host connection setup. BattlEye RCon and optional SFTP/FTP log access have separate credentials; enter them only in the private setup/dashboard fields.

What will not fix it: Do not create a Nitrado token for a GTXGaming server or paste credentials in a public Discord channel.

If it persists: Share the host name, platform, profile and exact error, but never the password.

If this happens: The PC control room cannot read players or run a protected broadcast/kick.

Check first: Check the selected PC profile, BattlEye RCon host, RCon port and password privately. The game port and query port are not substitutes for the RCon port; also check the host's RCon service/firewall.

Try safely: Test connection health and refresh the roster after the server is fully online. An empty roster can also mean no players are connected.

What will not fix it: RCon alone does not supply historical ADM/RPT feeds or file access.

If it persists: Send the host/provider, ports with password removed, connection result and timestamp.

If this happens: RCon works, but file browsing, catalogue imports or log feeds cannot read the host.

Check first: Confirm the file-access host, username and password were saved together for the same PC profile, and that the account can reach the mission/log directory.

Try safely: Use the provider's file-access details, not the BattlEye RCon password. Test with a read-only file/list operation first.

What will not fix it: Changing the RCon port cannot repair missing SFTP/FTP credentials.

If it persists: Send a redacted path, host type, protocol and exact error; keep credentials private.

If this happens: You signed in with Discord but no expected Wandering community appears.

Check first: Confirm you used the same Discord account that belongs to the server, and ask the owner whether that Discord and your role have dashboard/app access.

Try safely: Sign out and sign back in once with the intended Discord account, then reopen the community picker.

What will not fix it: Creating another account or reinstalling repeatedly will not grant a missing server membership or permission.

If it persists: Send your Discord user ID privately, the community name and the screen shown after login. Never send login codes.

If this happens: A previously available dashboard becomes a sign-in or public-guides screen.

Check first: Confirm network access and whether the dashboard website still recognises the same account. Public crafting guides can appear even without private server access.

Try safely: Reopen the app, sign in once if prompted, and note whether it fails only after closing/reopening or every time.

What will not fix it: Do not clear app data before capturing the app version and reproduction steps; that can erase useful evidence.

If it persists: Send app version, phone model, approximate time and a screen recording with personal information hidden.

If this happens: The dashboard or app opens, yet control, feeds or other staff sections are missing.

Check first: Ask the owner to inspect dashboard access, the member's current Discord roles, the selected community and the exact server profile. Access to public guides does not grant staff controls.

Try safely: After the owner saves the correct access, sign out/in and select the right profile again.

What will not fix it: Sharing the owner's login or RCon password is not an access fix.

If it persists: Send the Discord user ID privately and list the exact missing sections; do not send credentials.

If this happens: The account is signed in, but a DayZ player name, feed activity or eligible server is missing.

Check first: Confirm the correct Discord identity, DayZ platform, community and server profile. Check the current /linkgamer status and whether there has been fresh supported server-log activity.

Try safely: Ask the owner to compare the submitted player name/ID with the game's exact identity and wait for a new relevant log event.

What will not fix it: Changing the display name repeatedly or linking to the wrong platform will not create missing log evidence.

If it persists: Send Discord user ID privately, expected player name/platform and the last in-game event time.

If this happens: A setting looks changed but reverts on refresh or shows an error after Save.

Check first: Look for the confirmation/error banner, make sure the selected Discord and server profile are correct, and check required fields and current access level.

Try safely: Make one small change, save, wait for confirmation and refresh to verify it persisted. Copy any error before retrying.

What will not fix it: Clicking Save repeatedly can create duplicate jobs or make it harder to identify which attempt worked.

If it persists: Send the page/section, field name, timestamp and exact error; redact tokens and passwords.

If this happens: High ping, rubber-banding or connection loss affects some or all players.

Check first: Record the affected times, player count and whether every player was affected. Check provider status/restarts and the RPT for repeated errors, search overtime or connection messages.

Try safely: Compare before/after a normal provider restart and a quiet period. If host-level problems persist, give the provider precise timestamps and redacted RPT lines.

What will not fix it: A bot restart, blanket economy wipe or more frequent game restarts is not proof of a host fix.

If it persists: Send platform, host/service ID privately, UTC times, player count and relevant redacted logs.

If this happens: The provider has restart tasks, but the bot countdown is blank or waiting.

Check first: In Admin Center → Restart & Damage, check whether restart authority is Wandering Bot or Server provider for the selected profile. Nitrado provider mode reads its Automated Tasks; other hosts may not expose a readable schedule.

Try safely: For Nitrado, confirm the restart task exists and allow the provider schedule to refresh. Check time zone and warnings separately from the actual restart action.

What will not fix it: Do not enable bot-owned restarts while the provider also owns them unless you intentionally want two restart schedules.

If it persists: Send the selected mode, task screenshot with identifiers hidden, profile and expected next restart time/time zone.

If this happens: A scheduled reset did not complete near a provider restart.

Check first: Check the reset method, selected server profile, linked provider restart time and whether that restart was actually observed.

Try safely: Use the dashboard status and audit to see whether the temporary economy change was restored. Ask support to review the exact reset before scheduling another one.

What will not fix it: Do not delete persistence or repeat the reset blindly; a missed restart is intentionally not treated as a completed reset.

If it persists: Send reset ID, method, planned time/time zone, host task time and status screenshot.

If this happens: The item exists in the editor but buyers cannot see it.

Check first: Check the selected community, active Shop bot, item enabled state, category, role restrictions, stock/limits and whether the save actually completed.

Try safely: Test with one eligible buyer and the current shop command. Compare the editor's saved item ID with the displayed catalogue.

What will not fix it: Recreating the item before checking restrictions can produce duplicates.

If it persists: Send item/bundle ID, buyer role, expected category, screenshot and save time.

If this happens: The app, dashboard and Discord show different amounts, or a balance changes without an obvious purchase.

Check first: Check the same Discord identity and community on every screen, then compare recent transaction history and pending/failed orders.

Try safely: Stop retrying purchases, capture each displayed balance and the time, and ask support for a ledger review.

What will not fix it: Do not manually credit/debit a player or delete a wallet file until transactions and account mapping are reconciled.

If it persists: Send user ID privately, community, three balance screenshots, transaction/order IDs and approximate times; no payment details.

If this happens: A player appears in Wandering Ban Network, but can still join another participating server.

Check first: Shared reports are for staff review, not automatic global bans. Confirm the selected destination profile, compatible platform/ID, report evidence and whether an authorised admin applied it.

Try safely: Review the violation and proof before choosing to protect this specific server. Check the action status afterwards.

What will not fix it: Seeing a report or switching on sharing does not automatically ban the player everywhere.

If it persists: Send report ID, destination profile and action status; avoid reposting private proof publicly.

If this happens: Staff see a suspicious kill-chain alert while the player remains connected or unbanned.

Check first: Check whether this PC profile has auto-ban enabled. An alert alone is not proof of cheating; compare the ADM/RPT evidence, timing and player identity.

Try safely: Review the evidence and use the server's normal moderation process. For automatic actions, confirm the live RCon identity and audit status.

What will not fix it: Turning on auto-ban without reviewing thresholds or identity mapping can ban the wrong person.

If it persists: Send a redacted alert, relevant log excerpt, profile and action status to authorised staff.

If this happens: The dashboard reports an invalid category, unknown classname, broken XML or missing linked group.

Check first: Open the technical details and note the exact filename, map, event ID and invalid name. Compare against the selected map's live cfglimitsdefinition.xml and related CE files.

Try safely: Keep the failed job paused, repair only the named dependency on a copy, validate the complete set, then retry once. Preserve a backup of every live file.

What will not fix it: An error on one event does not justify wiping the economy or replacing unrelated XML files.

If it persists: Send the exact error text, event ID, map/build and redacted current linked files.

If this happens: The dashboard says uploaded, but no new object is visible in game.

Check first: Uploaded means files reached the host, not that DayZ spawned the event. Check whether a restart is required, the next RPT, the exact CE event name, available positions and collision/saferadius limits.

Try safely: Test one known-clear position and compare a new spawn cycle. Review the event's active/min/nominal settings and linked group/prototype.

What will not fix it: An exact map coordinate is not a guarantee the engine can place an object there.

If it persists: Send the event ID, intended coordinate, relevant RPT lines and a screenshot of upload/audit status.

If this happens: A removed bridge, bunker or JSON scene leaves a few objects or loot in the air.

Check first: Search every active ObjectSpawner JSON and CE event/group file for the exact class and coordinates. Check cfgGameplay.json for active JSON references and distinguish persistent old entities from new spawns.

Try safely: Remove only confirmed stale entries from a backed-up copy, restart if required and check a fresh spawn cycle/RPT.

What will not fix it: Deleting the main structure alone does not remove separate decoration, wreck or loot definitions.

If it persists: Send the location, screenshot, current referenced JSON and linked event/group/prototype files.

If this happens: Its answer conflicts with the current server map, mods, RPT or actual mission files.

Check first: Confirm the question names the correct PC/console platform, map, host, version and installed mods. Check whether the AI had the current files and exact error, not only a screenshot.

Try safely: Ask it to identify assumptions and validate a proposed minimal diff before applying anything live. Use support for high-risk or ambiguous changes.

What will not fix it: An AI answer, green syntax check or paid credit is not proof that a live DayZ change will work.

If it persists: Send the conversation link/ID, question, response and redacted evidence; do not share private credentials.

If this happens: A location picker or guide displays a different DayZ terrain or says its real map image is unavailable.

Check first: Confirm the selected server profile and map first. A missing map image is different from a broken server connection or incorrect coordinates.

Try safely: Switch to the intended profile and refresh. If the profile is correct, report the map name and exact page so support can check its map asset.

What will not fix it: Changing CE coordinates or uploading a random web map does not repair a dashboard display asset.

If it persists: Send the profile, map name, page URL and screenshot of the map area.

If this happens: A user expects a review reminder on the dashboard or app but does not see one.

Check first: Confirm they are signed into the right community, eligible to review and have not already submitted or dismissed a recent prompt.

Try safely: Use the Reviews section directly if available; a timed reminder is optional and should not block normal use.

What will not fix it: Repeated logins or clearing app data should not be required just to force a review prompt.

If it persists: Send account/community privately, app or web version, and when the prompt was expected.

If this happens: The dashboard and purchase receipt disagree about plan access or credit balance.

Check first: Confirm the same account/Discord and community used for the purchase. Check current plan status and whether the purchase is still pending.

Try safely: Sign out/in once and avoid repeating the purchase. Contact billing with the receipt/order ID if access remains wrong.

What will not fix it: Buying a second plan or sharing payment details in Discord is not a safe troubleshooting step.

If it persists: Send order ID, account email privately, community and screenshot; never send card numbers.