01 · Product overview
Local desktop automation
MapleStory Classic World Bot
okya for MapleStory uses on-screen image recognition and local keyboard control to automate repetitive grinding, farming, and leveling. Configure your own character and monster templates, then choose a strategy that fits the map.
- Platforms
- Windows 10/11 · Apple silicon Mac
- Game view
- 1366 × 768
- Processing
- Local screen recognition
A configurable MapleStory bot for repetitive play#
The desktop client reads the visible game window instead of asking for account credentials. It detects the character, selected monsters, minimap position, and HP/MP areas, then runs the strategy and key bindings you saved. Templates and ordinary settings remain on the device.
What the desktop client can automate#
Start with the smallest working configuration, confirm recognition in the runtime log, and enable optional actions one at a time.
Character and monster recognition
Create left- and right-facing image templates for your character and target monsters. The client uses them to locate visible targets.
Grinding and farming routes
Choose stationary attack, two-point patrol, or a custom route built in the map editor for multi-platform maps.
Automatic potions and buffs
Set HP/MP thresholds, potion keys, cooldowns, and up to five timed buff slots to match your in-game shortcuts.
Pickup and combat controls
Configure attack, jump, pickup, directional behavior, and strategy-specific timing from one desktop control panel.
Runtime logs and startup checks
Review window, minimap, character, monster, and vital-stat detection before leaving a strategy running.
Local profiles and routes
Save configuration, custom templates, and map-route files locally so each setup can be tested and adjusted.
Before you start#
- 64-bit Windows 10/11, or a Mac with Apple silicon (M-series)
- MapleStory running at 1366 × 768 with the minimap visible
- Accessibility and Screen & System Audio Recording permissions on macOS
- A valid license and a network connection for first activation
- Templates captured on the operating system and game setup you will actually use
MapleStory Classic World bot FAQ#
Does it support Windows and macOS?+
Yes. The current client supports 64-bit Windows 10/11 and Apple silicon Macs. The current Mac package is not intended for Intel Macs.
Why is 1366 × 768 required?+
Recognition regions for the game window, minimap, and HP/MP interface are calibrated for the 1366 × 768 client view. Other resolutions can prevent startup checks from succeeding.
Does the client need my MapleStory account password?+
No. It works from the visible game screen and configured local key controls. Never send your account password or license file to support.
Which strategy should I test first?+
Use Stationary Attack with one monster template and optional actions disabled. Add potions, buffs, pickup, or route movement only after recognition is stable.
Can I copy templates between Windows and Mac?+
You can back up configuration and route files, but image rendering can differ between operating systems. Re-capturing character and monster templates on the target system is recommended.
Can I create my own route for the bot?+
Yes. Use the browser map editor to mark platforms, nodes, and movement actions, export the JSON route, and import it into the desktop client. Build and test each route for the matching map and resolution.
02
User guide
Gameplay screenshots#
Installation, permissions, and activation#
Install the package for your operating system, then complete the platform-specific checks before configuring a strategy.
Windows installation
Extract the entire 64-bit Windows ZIP to a permanent folder. Do not launch it from inside the ZIP preview. Run the program as administrator.
Apple silicon Mac installation
Move the app to Applications before opening it. Grant both Accessibility and Screen & System Audio Recording in Privacy & Security, then quit the app completely and reopen it. The current Mac package is not intended for Intel Macs.
Verify macOS permissions
Accessibility lets the app send movement, combat, and recovery keys. Screen & System Audio Recording lets it read the game window, character, minimap, and HP/MP. Add the installed app—not Terminal, Python, an old build, or a folder—to both lists, enable both switches, then quit with Command-Q and reopen it.
Activate the license
Enter the complete license without leading or trailing spaces, activate it while connected to the Internet, and wait for the success state before returning to the main screen. If macOS asks for Keychain access, use the current Mac login password, not the license code.
Local data and backups
Windows data is stored under %LOCALAPPDATA%\Okya\; macOS data is under ~/Library/Application Support/Okya/. Back up config.json, templates, and maps only. Never copy license.dat to another computer; activate the new device separately.
Build reliable recognition templates#
Templates tell the client what to find on screen. Capture both facing directions on the same operating system and game setup you will actually use.
Character templates (20 × 20 px)
Create a named character profile, face left, and capture the stable area near the top of the head. Face right and select exactly the same body region. Confirm that both previews contain only the character, then save and select the profile.
Monster templates (10 × 10 px)
Choose a monster with limited animation and few distinct frames so its appearance changes very little while moving. Capture the same stable, distinctive area—such as the top of the head, a horn, or near the eyes—while it faces left and right. Start with one selected monster; daily use is usually most stable with one to three.
Good and bad samples
A good pair uses the same position in both directions and contains only the target. Recapture samples containing ground, platform edges, background, names, damage numbers, chat text, pets, skill effects, or another monster.
When to capture again
Recreate every template after changing the game resolution, display scaling, outfits, visual effects, game clients, or operating systems. The templates must match the resolution used during operation, and Windows and macOS may render pixels differently.
First-use setup#
The following flow is based on the actual desktop client and its first-use guide.
- 1
Install the correct package for 64-bit Windows or an Apple silicon Mac. On macOS, move the app to Applications before granting permissions.
- 2
Set the game to 1366 × 768 in windowed or borderless-window mode. Keep the minimap and HP/MP areas fully visible on the primary display.
- 3
Activate the license and select the correct game server so the client can use the matching minimap and HP/MP recognition regions.
- 4
Capture matching left- and right-facing templates for your character and target monster. Re-capture them after major visual or platform changes.
- 5
For the first test, choose Stationary Attack and configure only the character, one monster, attack key, and jump key.
- 6
Start the strategy and read the runtime log. Enable potions, buffs, and pickup only after both character and minimap recognition succeed.
Configure modes, combat, and optional actions#
Change one setting at a time, save it, and observe the runtime log before enabling the next feature.
Game window and basic settings
Use a 1366 × 768 window or borderless window on the primary display. Keep the minimap fully expanded and the default HP/MP area visible. Select the real server because it affects minimap colors and HP/MP regions, select the saved character, and begin with one monster. Keep the lie-detector alert enabled and test its sound.
Use diagnostic modes first
Recognition-only verifies the game window, character, monsters, minimap, and HP/MP without sending combat input. Movement-only validates a patrol or preset route. Full execution should be enabled only after both checks pass.
Combat and movement
Match attack and jump keys to the game shortcuts. Begin with conservative horizontal and vertical detection ranges; ranges that are too large can make the client react to targets on another platform.
HP and MP recovery
Enable HP and MP separately. A 50% threshold and about a one-second cooldown are practical test values; cooldowns must not be below 0.1 seconds. If the log shows HP or MP as 0.0%, disable recovery and first verify the server, resolution, window position, UI, and screen-recording permission.
Buffs and item pickup
Up to five timed buff slots are available. Test one slot first; every enabled slot needs a key and a period greater than zero. For pickup, 0.45 seconds is a stable starting interval and the minimum is 0.05 seconds. Very frequent pickup can interrupt combat and queue inputs.
First complete run
Enter the target map, expand the minimap, confirm HP/MP, save the server, resolution, character, monster, strategy, and keys, then start from a safe position. Wait for the app to return focus to the game and do not switch applications. The strategy is running only after the log confirms the game window, character, minimap, and startup checks.
30-second preflight check
Confirm the correct map and safe position, 1366 × 768 on the primary display, expanded minimap, correct server/profile/monster/strategy, matching attack/jump/potion/buff/pickup keys, sufficient supplies and inventory space, and an audible lie-detector alert.
Three map strategies#
Each strategy is designed for a different map shape. Test movement without optional actions before using a new configuration.
Stationary Attack
Recommended for the first test and fixed platforms. The client records the starting minimap position and can attempt to return after knockback or drift.
Two-Point Patrol
Moves between horizontal A and B coordinates on the minimap, with configurable pauses and optional attacks at the endpoints.
Custom Route Patrol
Follows a route file you build in the map editor with nodes, platforms, and actions. Routes must match the current map.
Create and use a custom bot route#
The map editor lets you describe how the bot should move through a specific map. Build the route against the same map and game view you will use in the desktop client.
Build a route in three steps
- 1Import the map you actually use
Take a screenshot from the game while it is running with the same map, resolution, window mode, and minimap layout you will use with the desktop client. Open the map editor and choose Import map. Avoid guide-site images, resized pictures, or screenshots from another setup because their coordinates may not match.
- 2Crop the minimap in the upper-left
Choose Crop, click the upper-left corner of the visible minimap, then its lower-right corner, and save the crop. Keep the complete traversable minimap inside the selection while excluding the game world, chat, quests, and other UI. Confirm that the cropped area matches the minimap the desktop client will recognize.
- 3Place nodes and build the route
Choose Node and place points at turns, landing positions, ropes, ladders, and portals. Mark platforms when they help describe the terrain, connect neighboring nodes, and assign the correct walk, jump, climb, drop, or teleport action. Export the route, import it for the matching map in the desktop client, and test movement before enabling combat or pickup.
Troubleshooting in the right order#
The runtime log is the first source of truth. Fix the earliest failed startup check before changing strategy parameters.
Game window not found
Confirm the game is open on the primary display in 1366 × 768 windowed or borderless mode. On macOS, recheck Screen & System Audio Recording and restart the app after changing permission.
Character, monster, or minimap not recognized
Remove visual obstructions, verify the selected server and template, expand the minimap, and recapture both directions in the current environment. Test with only one monster selected.
HP and MP both read 0.0%
Turn off automatic recovery first. Verify the selected server, 1366 × 768 resolution, default game UI, window position, and screen-recording permission before testing again.
Monsters are missed or misidentified
Select only one monster, capture both directions on a stable animation frame, and use a distinctive target-only region. Delete and recreate templates that include background or were copied from another operating system.
Recognized but no keys are sent
Return focus to the game, confirm configured shortcuts, and check Accessibility on macOS. On Windows, run the program as administrator.
macOS still asks for permission
Remove entries for an old build, test build, Python, Terminal, or a same-named folder. Add the current app from Applications to both privacy lists, enable both switches, quit with Command-Q, and reopen it.
Patrol crosses an edge
Move the A and B endpoints farther inside the safe platform and validate them in movement-only mode. Detection intervals and character inertia can cause a brief overshoot.
Updates, backups, and support#
Preserve your tested setup when updating, but do not move device-bound license data or sensitive information.
Before an update
Stop the strategy, quit the app, and back up config.json, templates, and maps. Install the new version separately, then verify the version, selected templates, server, shortcuts, and strategy settings.
Moving to another computer
Regular configuration and route files can be reviewed and migrated. Do not migrate license.dat. Activate the new device, grant its permissions, and recapture character and monster templates on the target system.
When contacting support
Include the app version, operating system and chip, server, resolution, window mode, strategy, relevant parameters, and the complete log from startup parameters to the first failure. Remove license keys, device identifiers, account names, and other secrets.