mwBot
bot panel
Get test api key
Payment
English zone
sección española
MW Bot Usage Calculator
To download the program, please complete the authorization, after which you will see the download links here.

 

How to Report a Bug: Script & Bot Support Guide

Started by Nikolaj, 05 January 2026, 11:44

Previous topic - Next topic

Nikolaj

Technical Support Submission Guidelines

To ensure we can resolve your issue as quickly as possible, please follow our submission protocol. Messages like "the script isn't working" are uninformative and significantly delay the process, as we have to spend time asking follow-up questions.
Describing the Problem Correcty

If a script is malfunctioning, provide a detailed report including:
Context: What exactly were you trying to do?
Error Localization: At what exact moment does the failure occur? Which function do you believe is performing incorrectly?
Nature of the Issue: Is the bot failing to launch entirely, working partially, or performing actions other than those expected?
Technical Information (Logs)

Diagnosis is impossible without log analysis. Please attach the following to your request:
The last 5–10 lines from your error.log file.
Ideal Scenario: Time-stamped data cross-referenced from mw.log, map.cmd.log, and error.log. This provides us with the full picture of the event.
Common User Errors (99% of cases)

Before contacting support, please verify the following:
Script Version: You may have downloaded an outdated script. Ensure that the command attribute is not used in the code—it has been removed. You must use execute instead.
Language Barrier: Scripts written for the English game interface will not work on Spanish (or any other) interfaces. The game language and the script language must match.
Empty Config Values: If you define a parameter in the configuration (e.g., pet_name=), you must provide a value. Even if the enable_pet function is disabled, empty parameters can cause code reading errors.
Premium Accounts and Maps: When using premium maps, keep in mind there is a "wall" 1 coordinate thick around the entire perimeter of the location.
Example: If you previously moved south at coordinates 150 100 by setting goposition=150|105, on premium maps, the character will hit a wall. You must change the value to goposition=150|99. Carefully study your movement logs.
noregen_data Error: If the game constantly reboots and this error appears in the logs, you have not followed the recommendations in the "First Run" article. Please review it and configure the game correctly.
Our Interaction Policy

We strive to make our documentation as clear as possible, but we cannot repeat information to every user that is already detailed in our articles.
If the solution to your problem is already on the website, we will direct you to the relevant article.
If the information on the site does not help, we will investigate the situation with you and update the documentation with new details.
Remember: We cannot read minds. The more specific data (material for analysis) you provide, the faster we can find a solution. Please respect both your time and ours.
About server menu
First run article