Development Approach

M9A is based on MaaFramework v5.1+ and adopts the JSON + Custom Logic Extension approach, registering custom modules through AgentServer.

Custom Module Types

M9A's custom modules are divided into three categories:

1. Custom Action

Location: agent/custom/action/

Purpose: Implement complex game operation logic, such as recognition result processing, multi-step operations, data analysis, etc.

Basic Structure:

from maa.agent.agent_server import AgentServer
from maa.custom_action import CustomAction
from maa.context import Context

@AgentServer.custom_action("YourActionName")
class YourAction(CustomAction):
    def run(
        self,
        context: Context,
        argv: CustomAction.RunArg,
    ) -> CustomAction.RunResult:
        # Read passed parameters (optional)
        # param = json.loads(argv.custom_action_param)
        
        # Implement your logic
        return CustomAction.RunResult(success=True)

The method to call the above action in the pipeline is as follows. The passed parameters can be any JSON object, which will be loaded as a dict type in the code above. If you need to change the input parameters based on user input, you can use the pipeline_override operation of the interface (see Interface V2 Protocol for details).

{
    "YourNodeName":{
        "action":"Custom",
        "custom_action":"YourActionName",
        "custom_action_param": {
            // Pass parameters (optional)
            // object
        }
        // ...
    },
    // or
    "YourNodeName":{
        "action": {
            "type": "Custom",
            "param": {
                "custom_action": "YourActionName",
                "custom_action_param": {
                    // Pass parameters (optional)
                    // object
                }
            }
        },
        // ...
    },
    // ...
}

Project Examples:

• DisableNode - Set specific node to disabled state
• NodeOverride - Dynamically override Pipeline configuration in node
• ResetCount - Reset counter state

2. Custom Recognition

Location: agent/custom/reco/

Purpose: Implement complex recognition logic that cannot be accomplished with Pipeline JSON alone, such as dynamic OCR, color matching, multi-step recognition, etc.

Basic Structure:

from maa.agent.agent_server import AgentServer
from maa.custom_recognition import CustomRecognition
from maa.context import Context
from typing import Union, Optional
from maa.define import RectType

@AgentServer.custom_recognition("YourRecognitionName")
class YourRecognition(CustomRecognition):
    def analyze(
        self,
        context: Context,
        argv: CustomRecognition.AnalyzeArg,
    ) -> Union[CustomRecognition.AnalyzeResult, Optional[RectType]]:
        # Read passed parameters (optional)
        # param = json.loads(argv.custom_recognition_param)

        # Implement recognition logic
        return CustomRecognition.AnalyzeResult(box=[x, y, w, h], detail={})

The method to call the above recognition process in the pipeline is as follows. The passed parameters can be any JSON object, which will be loaded as a dict type in the code above. If you need to change the input parameters based on user input, you can use the pipeline_override operation of the interface (see Interface V2 Protocol for details).

{
    "YourNodeName":{
        "recognition": "Custom",
        "custom_recognition": "YourRecognitionName",
        "custom_recognition_param": {
            // Pass parameters (optional)
            // object
        }
        // ...
    },
    // or
    "YourNodeName":{
        "recognition": {
            "type": "Custom",
            "param": {
                "custom_recognition": "YourRecognitionName",
                    "custom_recognition_param": {
                    // Pass parameters (optional)
                    // object
                }
            }
        },
        // ...
    },
    // ...
}

Project Examples:

• MultiRecognition - Multi-algorithm combined recognition, supports AND/OR/custom logic
• CheckStopping - Check if task is about to stop

3. Sink (Event Listener)

Location: agent/custom/sink/

Purpose: Listen to MaaFramework runtime events for pre-task checks, logging, performance monitoring, etc.

Basic Structure:

from maa.agent.agent_server import AgentServer
from maa.tasker import Tasker, TaskerEventSink
from maa.event_sink import NotificationType

@AgentServer.tasker_sink()
class MyTaskerSink(TaskerEventSink):
    def on_tasker_task(
        self,
        tasker: Tasker,
        noti_type: NotificationType,
        detail: TaskerEventSink.TaskerTaskDetail,
    ):
        # Execute logic on task start/success/failure
        if noti_type == NotificationType.Starting:
            # Pre-task checks
            pass

Project Examples:

• AspectRatioChecker - Checks if emulator resolution is 16:9 before task starts

Common APIs

Context Common Methods

# Execute recognition
reco_detail = context.run_recognition("NodeName", image)

# Execute task
context.run_task("NodeName")

# Override pipeline configuration
context.override_pipeline({"NodeName": {"next": ["NewNode"]}})

# Override image
context.override_image("image_name", image_array)

# Get screenshot
img = context.tasker.controller.post_screencap().wait().get()

Info

MaaFramework uses OpenCV to process images, so the captured image data is of numpy.ndarray type and in BGR format. No additional processing is required for interaction with MaaFramework, but if you need to save the image, you must convert it to RGB format first.

Recognition Result Processing

from maa.define import OCRResult, TemplateMatchResult

if reco_detail and reco_detail.hit:
    # OCR result
    ocr_result = reco_detail.best_result
    text = ocr_result.text
    box = reco_detail.box  # [x, y, w, h]
    
    # All recognition results
    all_results = reco_detail.all_results

Development Resources

• Integration Interface: Integration Interface
• Python Binding Source: maa/source/binding/Python
• Project Examples: Browse existing implementations in agent/custom/

Learning Recommendations

1. Read existing custom implementations in the project to understand common patterns
2. Refer to MaaFramework official documentation to understand core concepts
3. Study Python Binding source code for deeper API understanding