Mini Legion: Beast Within Dungeon and Raid Macro Setup Guide

To automate repetitive dungeon and raid farming in Mini Legion: Beast Within, record an emulator macro that loops through stage entry, combat initiation, and reward confirmation. The key to a stable macro is adding deliberate delay buffers between clicks so minor loading delays or combat length variances do not desynchronize your loop.

Emulator Preparation and Display Settings

Most Android emulators—such as LDPlayer, BlueStacks, or MuMu Player—include a built-in macro recorder. Before recording your inputs, configure the emulator environment to prevent click coordinate drift:

• Lock Window Resolution: Set a fixed display resolution, such as 1920x1080 or 1600x900 landscape. Never resize the window or switch between windowed and fullscreen modes after recording, as changing aspect ratios shifts the position of UI buttons.
• Stabilize Frame Rate: Lock your emulator output to a steady 60 FPS and allocate at least 4 CPU cores and 4 GB of RAM in engine settings to avoid frame drops during combat transitions.
• Disable Disruptions: Turn off emulator and OS pop-up notifications, ensure your network connection is stable, and disable any in-game screen dimming or sleep settings.

Recording the Dungeon and Raid Loop

A reliable macro begins and ends on the exact same menu screen. Navigate to your selected dungeon or raid stage preview before activating the macro recorder, then execute each step deliberately:

1. Enter Stage: Click the stage entry button to bring up your party formation screen.
2. Deploy Team: Click the start or battle confirmation button to dispatch your roster into combat.
3. Wait for Auto-Combat: Let the battle resolve completely on its own. Do not click skill icons or empty screen space during the fight.
4. Dismiss Victory or Defeat: Once the encounter ends and the results banner appears, click the reward claim area or continue prompt.
5. Confirm Return: Click the replay or confirm button that returns you to the stage preview menu where you started.

Stop recording immediately once the stage selection interface reloads. Every recorded click must target a specific UI button to avoid opening unwanted side panels.

Recommended Timing and Delay Buffers

Emulators record the exact timing between user clicks. If a script executes too fast, a brief server lag spike will cause the macro to click before the corresponding button loads. Incorporate generous padding after every screen transition:

If your emulator features a script configuration editor, inspect the timestamps directly and lengthen intervals without rerecording the entire sequence.

Configuring Loop Execution Settings

After saving the base recording, open the emulator macro manager to configure how the loop runs:

• Loop Count: Set a fixed repeat count matching your current supply of stamina, raid tickets, or dungeon keys. If you want continuous farming, select manual termination, but monitor your account to prevent unwanted currency usage.
• Interval Between Loops: Add a 3- to 5-second pause between script executions to allow the client to refresh ticket counters and process server responses.
• Playback Speed: Run the script at default 1x speed. Increasing playback speed compresses your delay buffers and causes missed inputs.

Troubleshooting Common Desync Issues

When long farming sessions encounter errors, adjust your settings using these targeted fixes:

• Stuck on Results Screen: If the macro attempts to restart before the loot animation completes, the click is ignored and the script desyncs. Lengthen the pause before the final confirmation click by several seconds.
• Accidental Currency Purchases: If your account runs out of entry tickets or stamina, the game displays a refill prompt. Clicks aimed at the stage entry button can inadvertently confirm premium currency purchases. Prevent this by setting a strict loop count tied to your available resources.
• Network Reconnection Pop-ups: Connection drops generate modal dialogue boxes that intercept macro clicks. Avoid running long unattended scripts during scheduled maintenance or across unstable connections.