Base Scheduling Protocol
About 2107 wordsAbout 7 min
Usage and field descriptions for resource/custom_infrast/*.json
Tips
Please note that JSON files do not support comments. The comments in this document are for demonstration purposes only. Do not copy them directly into your JSON files.
Visual Schedule Generator Tool
Visual Tool for Automatic Schedule Generation
Automatic RIIC Schedule Generator
Complete Field Reference
{
"title": "小号的换班方案", // Task name, optional ("小号的换班方案" = "Alt Account Shift Plan")
"description": "哈哈哈哈", // Task description, optional ("哈哈哈哈" = "Hahaha")
"plans": [
{
"name": "早班", // Plan name, optional ("早班" = "Morning Shift")
"description": "lol", // Plan description, optional
"description_post": "", // Description displayed after plan execution, optional
"period": [
// Shift time period, optional
// If current time is within this range, this plan will be automatically selected (JSON file may contain multiple plans)
// If this field doesn't exist, automatically switches to the next plan after each shift ends
// Core doesn't process this field; if you're using MAA through integration, implement this logic yourself
[
"22:00", // Format required: hh:mm, currently just compares number sizes, for cross-day periods follow this example
"23:59"
],
[
"00:00",
"06:00"
]
],
"duration": 360, // Work duration (minutes), reserved field, currently not used. May be used for shift change reminders in the future
"Fiammetta": {
// Which operator to use "Fiammetta" on, optional, omit if not using
"enable": true, // Whether to use "Fiammetta", optional, default true
"target": "巫恋", // Target operator, uses OCR, requires operator name in client language ("巫恋" = "Shamare")
"order": "pre" // Use before entire shift change or after, optional, values "pre"/"post", default "pre"
},
"drones": {
// Drone usage, optional, omit if not using drones
"enable": true, // Whether to use drones, optional, default true
"room": "trading", // Which room type to use drones on, values "trading"/"manufacture"
"index": 1, // Which instance of that room type to use drones on, corresponds to left tab number, range [1, 5]
"rule": "all", // Usage rule, reserved field, currently not used. May support plug/unplug operations in future
"order": "pre" // Use before operator changes or after, optional, values "pre"/"post", default "pre"
},
"groups": [
// For "control"/"manufacture"/"trading"/"recycle", you can set operator groups
{
"name": "古+银", // ("古+银" = "Gummy+Silver")
"operators": ["古米", "银灰", "梅"] // ("古米" = "Gummy", "银灰" = "SilverAsh", "梅" = "Plum")
},
{
"name": "清流", // ("清流" = "Purestream")
"operators": ["清流", "森蚺", "温蒂"] // ("清流" = "Purestream", "森蚺" = "Eunectes", "温蒂" = "Weedy")
}
],
"rooms": {
// Room information, required
// Values: "control"/"manufacture"/"trading"/"power"/"meeting"/"hire"/"dormitory"/"processing"/"training"/"recycle"
// Missing rooms use default algorithm for shift change.
// If a facility array holds fewer room entries than actual rooms, shift change stops from the first unconfigured room onward for that facility and sends one facility-wide unconfigured notice.
// An empty facility array (the facility key explicitly written with content []) keeps the entire facility unchanged without shift change, as distinct from a missing facility key (default algorithm shift change); facility-level actions such as the meeting room's clue flow and the training room's continue training still run.
// A room entry written without any staffing intent (operators/candidates empty or missing, no autofill or operator groups) only skips operator replacement for that room, keeps its current staff unchanged and emits a ｢room kept as-is｣ callback; other fields such as product are still processed
// The skip field skips both operator replacement and product switching for that room; drones are still used (when the room's operators are not changed, pre/post makes no timing difference); facility-level actions are unaffected (e.g. the meeting room's clue flow and the training room's continue training still run). The difference is that skip only logs, while empty intent emits the ｢room kept as-is｣ callback
// To skip a room, use skip field or uncheck the facility in software Task Settings - Base Management
"control": [
{
"operators": [
"夕", // Uses OCR, requires operator name in client language ("夕" = "Dusk")
"令", // ("令" = "Ling")
"凯尔希", // ("凯尔希" = "Kal'tsit")
"阿米娅", // ("阿米娅" = "Amiya")
"玛恩纳" // ("玛恩纳" = "Closure")
]
}
],
"manufacture": [
{
"operators": ["芬", "稀音", "克洛丝"], // ("芬" = "Fang", "稀音" = "Scene", "克洛丝" = "Kroos")
"sort": false // Whether to sort (by operators order above), optional, default false
// Example: When using Scene, Pallas, Shamare, etc. with "sort": false, operator order may be scrambled, losing warm-up effect.
// Using "sort": true can avoid this issue
},
{
"skip": true // Whether to skip current room (by array index), optional, default false
// If true, other fields can be empty. Skips operator change and product switching; drones are still used, and facility-level actions are unaffected, e.g. the meeting room's clue exchange and the training room's continue training still occur
},
{
"operators": ["Castle-3"],
"autofill": true, // Use original algorithm to auto-fill remaining positions, optional, default false
// If operators is empty or missing, the room stays unchanged per the empty-intent rule above
// If operators not empty, considers only single operator efficiency, not combination efficiency
// May conflict with custom operators defined later, e.g., using operators needed later, use cautiously or place autofill rooms last
"product": "Battle Record" // Current manufacturing product, optional.
// If detected facility product doesn't match task setting, UI will show red warning; may have more uses in future
// Values: "Battle Record"|"Pure Gold"|"Dualchip"|"Originium Shard"|"LMD"|"Orundum"
},
{
"operators": ["多萝西"], // ("多萝西" = "Dorothy")
"candidates": [
// Backup operators, optional. Uses whoever's available until positions filled;
// operators currently working in other facilities are never selected (excluded at selection time);
// those below the base shift-change morale threshold are skipped; dormitories are the
// opposite: operators with full morale are skipped to free the rest slot, and those
// not yet full (including ones resting in this very dormitory) stay selectable
// Incompatible with autofill=true, i.e., autofill must be false when this array not empty
"星源", // ("星源" = "Astgenne")
"白面鸮", // ("白面鸮" = "Ptilopsis")
"赫默" // ("赫默" = "Silence")
]
},
{
"use_operator_groups": true, // Set true to use operator groups from groups field, default false
"operators": [
// When enabled, names in operators are interpreted as group names
"古+银", // Will select groups by mood threshold and setting order ("古+银" = "Gummy+Silver")
"清流" // If Gummy+Silver group has operators below threshold, will use Purestream group ("清流" = "Purestream")
// If all groups are unavailable, the candidates list still applies; with neither candidates nor autofill configured, the room stays unchanged without falling back to the default algorithm
]
}
],
"meeting": [
{
"autofill": true // Completely autofill this room
}
],
"training": [ // Training Room, configures the trainee slot and the assistant slot
{
// Assistant candidates, optional; no assistant is selected when omitted. The
// assistant slot has no eligibility restriction like the trainee slot, so any
// operator can be staffed there; consistent with the generic candidates field,
// candidates currently working in other facilities are never selected (excluded
// at selection time); candidates below the base shift-change morale threshold are
// likewise skipped at selection time with the same semantics as production
// facilities; if no candidate remains, the assistant is kept unchanged; this
// also covers skills of operators working
// in other facilities that need ｢an operator of the same faction staffed in the
// base for higher efficiency｣ (put one matching-faction operator in operatorsA).
// Naming requirements as in operators (on non-CN clients the simplified Chinese
// name must be used; recognized names are normalized to simplified Chinese
// before matching)
"operatorsA": ["杜宾"],
// Trainee slot candidates, optional; when omitted the trainee slot operator is not
// changed. The first candidate present in the in-game selection list is staffed.
// Staffing is subject to the trainee slot's eligibility restriction: the operator
// must be promoted to elite 2 with at least one skill below max mastery;
// operators with all masteries maxed never appear in the list, so configuring
// them is effectively a skip. While training is in progress the trainee slot is
// locked and cannot be changed. Staffing alone does not start a new training
// session; starting mastery training still requires a manual tap. Naming
// requirements as in operators
"operatorsB": ["银灰"]
// Generic roomConfig fields such as operators/candidates have no effect on the training room; only skip and operatorsA/operatorsB take effect
// ｢Continue training｣ is a standalone GUI option outside the schedule file and is unaffected by the three room states; with an empty array, skip, or empty intent, continue training still runs and only operator replacement is skipped
// When ｢continue training｣ is enabled, the shift-change flow first tries to continue the current operator's mastery training; on success the trainee slot stays unchanged and only the assistant is replaced per configuration, otherwise (materials insufficient or mastery already maxed) it falls back to replacing the trainee slot operator per configuration
}
],
"recycle": [ // 回收站, two slots without role distinction, same format as manufacture, product field has no effect
{
"operators": ["Fang", "Kroos"]
}
]
}
},
{
"name": "晚班" // ("晚班" = "Night Shift")
// ...
}
]
}Example
Schedule Extension Protocol
The MAA base scheduling protocol only includes operator shift information. The schedule extension protocol builds on the MAA scheduling protocol by adding optional base layout layout, operator information operators, and source and version metadata metadata, allowing MAA, the Arknights Yituliu - Automatic Base Schedule Generator, the Arknights Yituliu - Base Schedule Income Calculator, and other third-party applications to share one file and exchange data in both directions. All extension fields are optional and can be adjusted according to the actual needs of third-party applications.
| Top-level field | Purpose |
|---|---|
layout | Record the base layout, including facility types, levels, and positions |
operators | Record operator promotion stages and levels |
metadata | Record data such as the protocol version, generating tool, and module versions, as well as additional data required by third-party tools |
Extension Field Reference
Combine the example with base protocol fields such as plans. Progression and version numbers are illustrative; remove comments from actual JSON.
{
// All three top-level fields are optional, can be provided independently, and do not affect MAA's base scheduling execution
// Tools should preserve extension information during import, editing, and export
"layout": [ // Complete built layout, optional; absence means no layout information is provided
// Unlisted facilities are unbuilt; facilities omitted from plans[].rooms retain the base protocol's default rules
// type: facility type; level: facility level; position: physical position
{ "type": "control", "level": 5 },
// Same-type room order matches plans[].rooms and drone index numbering
{ "type": "trading", "level": 3, "position": "B101" },
{ "type": "trading", "level": 3, "position": "B102" },
{ "type": "trading", "level": 1, "position": "B103" },
{ "type": "manufacture", "level": 3, "position": "B201" },
{ "type": "manufacture", "level": 3, "position": "B202" },
{ "type": "manufacture", "level": 2, "position": "B203" },
{ "type": "manufacture", "level": 2, "position": "B301" },
{ "type": "power", "level": 3, "position": "B302" },
{ "type": "power", "level": 3, "position": "B303" },
{ "type": "meeting", "level": 3 },
{ "type": "processing", "level": 3, "position": "B105" },
{ "type": "hire", "level": 3, "position": "B205" },
{ "type": "training", "level": 3, "position": "B305" },
{ "type": "dormitory", "level": 1, "position": "B104" },
{ "type": "dormitory", "level": 1, "position": "B204" },
{ "type": "dormitory", "level": 1, "position": "B304" },
{ "type": "dormitory", "level": 1, "position": "B404" },
{ "type": "recycle", "level": 1, "position": "B405" }
],
"operators": { // Operator progression, optional; keyed by in-game IDs
// Does not replace room assignments
"char_002_amiya": {
"name": "Amiya", // Operator name, optional
"elite": 2, // Promotion stage: 0, 1, or 2
"level": 80 // Level within the current promotion stage
},
"char_124_kroos": {
"name": "Kroos",
"elite": 1,
"level": 55
}
},
"metadata": { // Source and version metadata, optional
"extensionVersion": "1.0", // Optional version string for the entire extension protocol; absence means the unversioned format
"generator": { // Original generating tool information
"id": "yituliu-riic-schedule-generator",
"name": "明日方舟一图流-排班表自动生成工具",
"url": "https://ark.yituliu.cn/tools/scheduleV3"
},
"moduleVersions": { // Versions used during generation; module identifiers are defined by the generating tool and interpreted with generator.id
"layout": "v20260924.2314", // Layout module
"data": "v20260924.2314", // Data module
"team": "v20260928.1118", // Team module
"assembler": "v20260822.2233", // Schedule assembler
"yield": "v20261002.1334", // Income calculator
"recommendation": "v20260928.1102" // Debug information
}
}
}