Skip to content

Latest commit

 

History

History
219 lines (145 loc) · 8.05 KB

README.md

File metadata and controls

219 lines (145 loc) · 8.05 KB
Raw

Monster Super League AutoIT Bot

Join the discord server to get help in setting up: https://discord.gg/UQGRnwf

A free open-sourced bot for Monster Super League using AutoIT programming language. This bot can do the tedious tasks of catching rare astromons, farming golems while selling the unwanted gems, and more.

Features:

  • Capture Legendary, Exotic, Super Rare, Rare, and Variant monsters.
  • Collect trees every hour.
  • Buy items from shady shop.
  • Attack Guardian Dungeons.
  • Farm Golem Dungeons and filter out unwanted gems.
  • Slime farming and gem/gold conversion.
  • And more.

Table of Contents

How to use bot
Manually updating
Common Issues
Setting up multiple emulators
Troubleshooting
Reporting an issue

How to use bot

Requirements:

  • Windows 7/8/8.1/10.
  • Latest updates from your Graphics Drivers.
  • Latest version of Nox. Recommended versions: 5.0.0.1 and above.
  • AutoIT: Download here.
  • The bot app: Download here.

Before you start:

  • When running the bot app through .au3, Run Script (x86) by right clicking on the file.
  • Set your Windows Display Scaling to 100% or set the Display Scaling option in the bot to your Windows Display Scaling Setting.
  • Enable Windows Aero Mode (Windows 7).

Configuring your Nox Settings:

Step 1: Enable Fixed window size in the Interface settings tab.

Interface settings

Step 2: Change the resolution to custom with Width: 800, Height: 552, and DPI: 160

Resolution

Step 3: Save settings.

Monster Super League Game Settings:

Step 1: Change language to English.

Language Setting

Step 2: Turn off all settings.

Game Setting

Step 3: Download game resources.

Changing Bot Config:

Step 1: Change Emulator Title according to the title of the emulator window.

Note: The title of your Nox window should have greater than 3 characters. 'Nox' or 'MSL' will not work. 'NoxPlayer' or 'Nox1' works.

Step 2: Check your settings by performing the Compatibility Test. Focus on the bot and press Ctrl+T

Compatibility Test

Step 3: The compatibility test will check the major controls for the bot. The test will also provide comments on how you may be able to fix any issues that it has detected. If you have any issues, you can copy the compatiblity test information and report the bug in Github or Discord.

Test Result

Step 4: Run desired script. Descriptions of each script is available on the bot app.

  • For any errors, refer to the Common Issues and Troubleshooting.

Manually updating

Step 1: Download the latest version from the same link.

Step 2: Open the ZIP file and extract the contents into the old version.

Drag files

Step 3: When the Replace or Skip Files prompt appear, select the option to replace.

Your existing configs will be saved.

Replace All


Common Issues

Window/Control Handle not found.

  • Check Emulator Title. If Emulator Title is correct, change the Emulator Property accordingly:

    • For Nox Emulator try using one of the following:

    [CLASS:Qt5QWindowIcon; TEXT:ScreenBoardClassWindow]

    [CLASS:subWin; INSTANCE:1]

    [CLASS:AnglePlayer_0; INSTANCE:1]

Window/Control handle error

Nox path does not exist.

  • Locate file location of the Nox.exe and in the same folder lies nox_adb.exe or adb.exe. Use the path to the file and enter it in ADB Path config.

Nox path error

Nox adb path

Nox device does not exist.

  • This error will usually provide a list of all available devices. Chances are one of the device is the Nox emulator. If device is not listed, restart nox.

Nox device

Function for the script does not exist.

  • There are missing or corrupted files detected. Redownload files and extract into a new folder. Then follow the steps to get set up above.

Func err




Setting up multiple emulators

Step 1: Create a new profile by editing the Profile Name setting in _Config.

Step 2: Change the ADB Device field to the device name connected to the second emulator.

  • To find the list of devices, open Debug Input (Ctrl+D) and enter MsgBox(0, "", adbCommand("devices")).

  • If no new device shows up, then restart Nox.

Device List

Step 3: Run a script.


Troubleshooting

  • Most problems can be solved by running the RestartNox() function.

Script looping in airship or doing nothing.

Before troubleshooting for this problem:

  • Open Debug Input Ctrl+D and enter getLocation() in airship and the map.
  • If the locations say 'unknown' on the log, proceed with the following troubleshooting.
  • If the location is village in the airship and map in the map, your problem is different.

Using the RestartNox() function:

  • If you have the Nox emulator, you can open Debug Input Ctrl+D and enter RestartNox().
  • This function will close and open the Nox process with correct resolution, dpi, and language set.
  • After restarting, try running a script.
  • If the issue still occurs, continue with other methods.

Using other Capture Mode:

  • If WinAPI does not work for you, try switching to ADB or None capture mode.
  • If none of the modes work for you, ask help in Discord or create an issue report on Github.

Locations not being recognized or imagesearch not working properly.

Check graphics settings

  • Your graphics settings could change the way the game looks so the pixels will be slightly different.
  • Try restoring your graphics setting to default settings and then restart your Nox.

ADB Path is too long or is not being recognized.

Download ADB files

Checking capture.

Use the CaptureRegion function to save an image

  • Open the Debug Input by pressing Ctrl+D or through the menu.
  • Enter CaptureRegion("test_image")~Run("mspaint.exe " & @ScriptDir & "\test_image.bmp")
  • Analyze the image and make sure it is capturing correctly.
    • There should not be Nox window handle.
    • The entire image should be filled by the MSL game.
    • No empty spots on the right and bottom side of the image.
    • Should not be a black screen.

Changing the Emulator class and instance

  • Issues with the capture could be fixed by entering the correct Emulator class and instance.
  • Refer to Changing Bot Config

Reporting an issue

Issue report can be made on Github or Discord.

Include the following:

  • Nox version. Ex. version 6.0.0.0
  • Bot app version. Ex. version 3.8.0
  • Script that you used. Ex. Farm Rare
  • Description of the problem.
  • A screenshot if possible.

License

This project is licensed under the terms of GPL-3.0 Open Source License.