FAQ

About 764 wordsAbout 3 min

Installation & Download

What do the filenames mean?

Desktop builds are named as:

MaaKEDR-<os>-<arch>-<version>-<frontend>.<ext>

For example, MaaKEDR-win-x86_64-v1.0.2-MFAA.zip:

OS: win (Windows)
Arch: x86_64 (64-bit Intel/AMD)
Version: v1.0.2
Frontend: MFAA (GUI, requires .NET)
Extension: zip

Android builds use a separate naming scheme and have no frontend (there is only one UI):

MaaKEDR-android-<ABI>-<version>.apk

ABI in filename	Target devices	Size
`universal`	Any Android device (contains both ABIs — the safe pick)	Largest
`arm64-v8a`	Most phones and tablets (64-bit ARM)	About half
`x86_64`	Android emulators on a PC, rare x86 tablets	About half

Not sure which to pick? Take universal. Want to save space on an ordinary phone? Take arm64-v8a.

Slow download speed?

GitHub download speeds vary. Try:

Using a mirror proxy like ghproxy
Check the MaaKEDR community group for backup links (see CONTACT file)

Crashes

Missing DLL error (e.g. `VCRUNTIME140.dll`)

VCRedist is not installed. Download and install vc_redist.x64.exe.

MFAA does not start or shows .NET errors

.NET Desktop Runtime is not installed. Download from the .NET download page.

App crashes without an error message

Check maafw.log for details. Common causes:

Path contains non-ASCII characters or spaces → move to a plain English path
Incomplete extraction → re-extract
Antivirus deleted files → add an exclusion

MXU is slow or shows a black screen

Update your GPU drivers. Try switching the rendering mode in MXU settings.

Connection

Emulator not auto-detected

Make sure ADB debugging is enabled in your emulator
Ensure only one emulator instance is running
Try clicking "Refresh"
Confirm the resolution is set to 1280x720 (landscape)

How to configure manually?

Click "Customize" in the connection panel. Default ADB ports:

Emulator	Default ADB Address
MuMu 12	`127.0.0.1:16384`
BlueStacks 5	`127.0.0.1:5555`
LDPlayer 9	`127.0.0.1:5555`
NoxPlayer	`127.0.0.1:62001`

Connected but tasks don't run

Verify the game is installed and updated
Confirm the correct resource type (Official/Bilibili/TapTap) is selected
Check screenshots in debug/ for recognition accuracy

Task Execution

Agent startup timeout

First launch requires downloading Python dependencies, which may take a while. Do not click "Stop". If it times out repeatedly:

Check your network connection
Verify the mirror in config/pip_config.json is accessible

Tasks not running as expected

Confirm the task is enabled (checkbox checked)
Read each task's description and configure options accordingly
Ensure the game is on the correct screen (main menu or target feature)
Review maafw.log for details

Farm resources stage list is incomplete

Only preset stages are included. To add more stages, refer to the Pipeline guide in the developer documentation.

Miscellaneous

Where are the logs?

Logs: maafw.log (project root). Screenshots: debug/ directory. Include these files when reporting issues.

MXU: An Update section appears in Settings when mirrorchyan_rid is set in interface.json.
Check for updates will try MirrorChyan first; without a CDK or if the resource is not registered on Mirror, it usually falls back to GitHub Releases (network access required; optional GitHub Token helps with rate limits).

MFAAvalonia: Configure the update source in settings, then check for updates.

For manual updates: download the latest release, extract to a new directory, then copy your old config/ folder to the new directory to keep your settings.

MFAA Tips

Remembered Connection & Fingerprint Matching

If a remembered connection gets overwritten when you launch MFAA with an unremembered emulator running, go to Settings → Connection Settings and disable "Use fingerprint to match device" to prevent auto-switching.

Multi-Instance Setup & Batch Launch

Only one MFAA instance can run per directory. To run multiple emulators simultaneously, create additional configurations from the main config panel. Each config can connect to a different emulator with its own task set. The second icon in the left sidebar shows real-time status for all configs.

Tips

To auto-launch multiple configs on startup, enable "Batch launch on startup" in startup settings and select the configs to run.

Auto-Launch Game

MFAA can launch the game automatically when a task starts, with two methods:

Custom Program: Click "Add Task" in the task list, scroll to find "Custom Program", add it to the top of the list, and enter the game path in its settings.
Connection Settings: Enable "Launch game on connection failure", then set the game path in startup settings.

When using multiple emulator instances, ensure the multi-instance ID is correctly set in the additional commands field.

Tips

Quick setup is available next to the additional commands field in startup settings.