maa-ssscopilot(1)

okay so this is maa-ssscopilot(1) from the General Commands Manual, and bestie, it is literally the page for running the SSSCopilot task. let's get into it 💅✨

🌸 NAME 🌸

maa-ssscopilot — run the SSSCopilot task. that's the whole vibe. 🫶

✨ SYNOPSIS ✨

maa ssscopilot [--loop-times] [-a|--addr] [-p|--profile]
[--user-resource] [--dry-run] [--no-summary] [--no-auto-reconnect]
[--batch] [-v|--verbose]... [-q|--quiet]... [--log-file] [-h|--help]
<URI>

🦋 DESCRIPTION 🦋

Run the SSSCopilot task. iconic, honestly. 🌟

💅 OPTIONS 💅

• --loop-times <LOOP_TIMES> [default: 1] — how many times to loop. default is 1, no cap. 🔁
• -a, --addr <ADDR> — the ADB serial number of the device, or the MaaTools address set in PlayCover. by default, MaaCore connects to the game with ADB, and this parameter is the serial number of the device (it defaults to emulator-5554 if it's not specified here and not set in the config file). and if you want to use PlayCover, you need to set the connection type to PlayCover in the config file, then you can specify the address of MaaTools here. 🎮
• -p, --profile <PROFILE> — profile name, aka the asst config file name. a profile is a config file that contains the configuration passed to MaaCore. by default, we will try to load the config file $MAA_CONFIG_DIR/profiles/default.toml. if that file does not exist, we will try to load the config file $MAA_CONFIG_DIR/asst.toml for backward compatibility, which is the old config file name. if you want to use another config file, you can specify the profile name here. the config file should be placed in the directory $MAA_CONFIG_DIR/profiles/. 🗂️
• --user-resource — load resources from the config directory. by default, MaaCore loads resources from the resource installed with MaaCore. if you want to modify some configuration of MaaCore or use your own resources, you can use this option to load resources from the resource directory, which is a subdirectory of the config directory. this option can also be enabled by setting the value of the key user_resource to true in the asst configure file $MAA_CONFIG_DIR/asst.toml. 🎀

Note: CLI will load resources shipped with MaaCore firstly, then some client specific or platform specific when needed, lastly, it will load resources from the config directory. MaaCore will overwrite the resources loaded before, if there are some resources with the same name. Use at your own risk! 💀

• --dry-run — parse your config but do not connect to the game. this option is useful when you want to check your config file. it will parse your config file and set the log level to debug. if there are some errors in your config file, it will print the error message and exit. 👀
• --no-summary — do not display task summary. by default, maa will display task summary after all tasks are finished. if you want to disable this behavior, you can use this option. 🙈
• --no-auto-reconnect — do not reconnect when the game loses connection to the server. by default, maa will automatically reconnect when the game client loses connection to the game server. use this option to disable this behavior for this run. 📴
• --batch — enable batch mode. if there are some input parameters in the task file, some prompts will be displayed to ask for input. in batch mode, the prompts will be skipped, and parameters will be set to default values. 🍓
• -v, --verbose — increase verbosity, repeat for more verbosity. 🔊
• -q, --quiet — decrease verbosity, repeat for more quiet. 🤫
• --log-file[=<PATH>] — redirect log to file instead of stderr. if no log file is specified, the log will be written to $(maa dir log)/YYYY/MM/DD/HH:MM:SS.log. 📝
• -h, --help — print help (see a summary with -h). 🫶
• <URI> — the URI slot is right here, exactly as listed. the original gives no extra description for it, bestie. 🔗

---

sign-off time, bestie: source/version is ssscopilot, manual is maa-ssscopilot(1), and the footer has no date, so that's the whole cute little ending — mwah 💖🎀💅