Mod Name: Maid File Manager
Chinese Alias: 车万女仆档案（迁移）管理器
Parent Mod: TLM (Touhou Little Maid)
Author: zgxhzhr (Bilibili: 逐光星火-执火人)
License: MIT
Source Code: https://github.com/zgxhzhr/MaidFileManager
MCmod.cn: 车万女仆档案（迁移）管理器 (Maid File Manager) - MC百科|最大的Minecraft中文MOD百科
Keywords: Touhou Little Maid, TLM, maid migration, cross-version transfer, maid export, maid import, world transfer, server migration, maid backup, maid profile, maid data manager, addon data migration SPI, 车万女仆, 女仆迁移, 跨版本转移, 女仆导出, 女仆导入, 整合包转移, 女仆数据管理, 女仆档案, 女仆备份, 女仆备份管理, 附属数据迁移, 万法皆通, maid backup manager, save rescue, All Methods, Fabric, Forge, NeoForge.
Maid File Manager is an addon for Touhou Little Maid built around two core purposes: take your maid with you wherever you go, and manage (and rescue) the maid backups Touhou Little Maid produces automatically.
Whether you are switching modpacks and starting fresh, or bringing your single-player maid to a multiplayer server, this mod allows you to freely transfer maid data across 1.20 / 1.20.1 / 1.21 / 1.21.1, with full support for Forge, NeoForge, and Fabric. And when a save breaks or rolls back, the built-in Backup Manager lets you browse the automatic maid backups — across every local save, and on a server for every player within your permissions — and pull the maid back out.
Note: Fabric versions are based on community unofficial ports of TLM, not officially supported by the Touhou Little Maid mod itself. If you encounter issues on Fabric, please first confirm whether they are caused by the port itself.
Search keywords: Touhou Little Maid addon, maid cross-version transfer, maid world migration, maid export import, TLM maid backup, maid profile manager, maid data migration tool, addon migration API, 车万女仆附属模组, 女仆跨版本迁移, 女仆跨存档转移, 女仆导出导入, 女仆档案管理, 女仆备份管理, 女仆数据迁移, 附属模组数据迁移, 换整合包保留女仆, 万法皆通兼容, save rescue, crashed save recovery, backup manager, 存档救援, 崩溃存档恢复, 备份恢复.
Why do you need this mod?
Transferring a maid is far more complicated than it seems. You might think just copy the entity data, but a maid's data — and her "memories" — are actually scattered across at least four unrelated places:
- Entity NBT (inside world save): Model ID, tasks, 4 equipment sets, favor/experience, YSM data, kill records, chess stats, AI chat history. Can travel with the maid? Yes, but only within the same world, and copying it raw means the same entity UUID collides in the destination world.
- File backups (maid_backups): Backup files organized by owner UUID. Can travel with the maid? Possibly, but the directory structure is hard-tied to the owner UUID. Change worlds or servers, the player UUID changes, and the backups become unreadable.
- Player data (Capability / DataAttachment): Maid count, AI token quota. Can travel with the maid? No — completely independent from the maid, so nothing on the maid's side can pull it along.
- Addon storage (independent SavedData / Capability / external databases): This is the invisible part. Many maid addons keep their own values and "memories" OUTSIDE the entity NBT — oath/bond lock flags, mood and affinity values, ability unlocks, favor counters, custom event records — and associate them with the maid purely by her UUID. Copying the entity carries not a single byte of it; in the new world the addon sees a total stranger with a blank slate. There is no common channel for addons to migrate this data, each addon would need its own solution.
This means:
- There is no one-click export/import tool in the base mod.
- Owner UUID is hard-linked. Moving to a new world or server means the maid becomes ownerless.
- There is no official cross-server transfer channel.
- Cross-version migration is risky due to major refactors between 1.20 and 1.21.
- Addon-raised stats and memories are stranded even if you copy the entity by hand.
This mod was created precisely because the base mod makes it so difficult to take your maid with you — and as of v1.4.0 it also offers a standard migration API (SPI) so addon authors can bring their own data along with one registration.
Keywords: maid transfer tool, cross-version maid migration, TLM maid backup manager, maid profile manager, maid world transfer, server maid migration, maid addon migration API, 女仆跨服转移, 女仆备份管理, 女仆档案管理, 整合包女仆迁移, 附属数据迁移接口, 1.20 to 1.21 maid transfer, maid backup rescue, server backup admin, 备份管理, 存档救援, Fabric maid mod.
What Maid File Manager can do?
Core Purpose 1 — Take your maid with you (migration):
- One-click Export / Import: Press U in-game, select your maid or a .maid file, and export or restore with one click.
- Batch Operations: Select multiple maids or files at once for bulk export or import, with per-file failure reasons listed in the summary.
- Cross-Version Migration: Seamless data transfer between versions 1.20, 1.20.1, 1.21, and 1.21.1.
- Portable .maid file: one file per maid; her profile photo is packed in and travels with her.
- Maid profile: view and edit a maid's photo, occupation, birthday, personal notes, preferences and background story right in game — and preview the profile inside any .maid file before importing.
- Duplicate Import Protection: the same maid cannot be imported twice; a clear message explains the rejection. Different players importing the same file on a server never conflict; re-importing works normally after the maid dies or is dismissed.
- No Residue: Uninstalling the mod does not affect maids that have already been imported.
Core Purpose 2 — Manage and rescue maid backups (Backup Manager):
- Browse every automatic backup Touhou Little Maid produces, grouped as world → player → maid → backup file, and export any of them as a .maid. In single-player / LAN (or from the main menu) you can browse every local save at once, so you no longer have to dig through folders or guess UUIDs.
- Rescue a crashed or rolled-back save: even if a world no longer opens, its maid backup files are still on disk, and you can pull a maid straight out of them into a fresh world.
- On a dedicated server, admins (OP, permission level 2) can browse and locate any player's backups, which makes recovery and audit far easier.
- Non-OP players can still see and export their own backups, without waiting for an admin.
- The server side is strictly read-only: it never writes, never deletes anything.
New in v1.6.0 — Maid Profile Manager & Backup Manager:
Maid Profile Manager (press U, then the Profile button):
- View and edit a maid's profile: photo, occupation, birthday, personal notes, preferences & skills, background story.
- Shows the Tribulation (lightning trial) mark — visible both for an online maid and in the read-only import preview.
- Multi-line fields support Chinese/IME input and full Ctrl+A/C/V/X clipboard operations.
- The "Model" field became a "Name" field: shows the name tag (custom name) when set, otherwise falls back to the model name.
- Photos are now stored outside the entity at maid_file/maid_photos/<maid-uuid>.png (longest side 512 px, proportional), so the entity save no longer carries the image every time; they are still packed into the .maid file and remain visible in the read-only import preview.
Backup Manager:
- Browse Touhou Little Maid's automatic backups, grouped as world → player → maid → backup file, and export any of them as .maid.
- Single-player and LAN host read the local saves directly; entering from the main menu merges every local world, so every save's backups can be browsed in one place.
- Rescue a crashed or rolled-back save: even when a world no longer opens, its maid backups are still on disk — select the maid and export her into a fresh world.
- On a dedicated server, admins (OP) can browse and locate any player's backups; non-OPs can still see and export only their own, without waiting for an admin.
- A dedicated server reads its own save and returns the result. The server side is strictly read-only: it never writes, never deletes anything.
- Exported files always land on the client at maid_file/maid_exports/<player>/.
- Entry points: the "Backup" button in the title bar of the profile manager, or "Backup Manager" in the game main menu.
- Fixed: the "Open Export Folder" button in the Backup Manager used to stay dark and unusable.
Other changes in v1.6.0:
- Unified folder layout: everything now lives under maid_file/ — maid_exports/, maid_imports/, photos/ and maid_photos/. Legacy folders in the game root are migrated automatically on first launch.
- .maid format raised to v7: adds a profile snapshot field. Old files (v1 through v6) import without any conversion; the new field is ignored by older mod versions.
- The maid list in the profile manager is filtered by save, making it easier to look across saves.
- When a maid uses a YSM model in place of the TLM model, the export list, the profile screen and the backup list now show the YSM custom name / model name correctly (the modelId stored in .maid stays the underlying TLM value, so cross-version import and fallback are unaffected).
- The "keep baubles" switch was removed from the import tab; whether baubles travel is now controlled solely by the server setting "allow carrying baubles on import". The left toolbar was re-arranged accordingly.
- The server switch "allow carrying the maid's invulnerability (Substitute Jizo) on import" now defaults to off (it used to default to on).
New in v1.5.0 — Cross-Version Bauble Attribute Preservation (bidirectional):
- Baubles are carried by default and can be turned off by the server.
- Same-version imports parse the full item NBT (enchantments, durability, unbreakable, data components) and keep it.
- Cross-version imports convert attributes both ways: 1.20 → 1.21 upgrades item NBT through DataFixerUpper; 1.21 → 1.20 manually downgrades the component format (enchantment levels → Enchantments, damage → Damage, etc.), because the 1.20 platform cannot downgrade through DFU. Enchantments, durability, unbreakable and base values are preserved.
- Items are rebuilt as brand-new only when the source version is unknown or the data cannot be parsed; a WARN is logged and the import is never aborted.
- Only baubles from the Touhou Little Maid and Touhou Little Maid: All Methods namespaces are allowed; anything outside is dropped.
- Bauble Import Settings (server-side, OP-managed): a "strip bauble attributes on import" toggle (default off = keep attributes) and a blocked-bauble list. The list contains only real baubles — resolved through TLM's internal bauble registry, so tools / materials / books no longer mix in — and supports live search by name or ID. Clients sync on join; non-OPs are read-only.
- Every processed bauble is reported item by item (dropped / rebuilt as a new item, and why); overflow notes are still delivered to the chat.
- Fixed: on 1.21 the Bauble Import Settings list ignored scroll direction (the 3rd parameter of the 4-arg mouseScrolled is the horizontal amount, which is always 0; the 4th is now used).
- Fixed: on 1.21 the Bauble Import Settings list was always empty ("no matching baubles") because the old check tested whether the item implemented IMaidBauble, which bauble items do not; it now queries TLM's bauble registry.
- Fixed: on 1.21 exporting and re-importing lost all potion effects — 1.21 uses the lower-case key active_effects while the old code only read 1.20's ActiveEffects; both keys are now accepted.
New in v1.4.x:
- v1.4.0: Addon Migration API (SPI) — MaidMigrationProvider + MaidMigrationRegistry, carried in the .maid v5 extras field. Duplicate import prevention: the imported entity UUID is derived deterministically from (source maid UUID + importing player UUID). Base health/attack reset to TLM's vanilla values by favorability level (including the Tribulation bonus); a bounded per-tick recalibration window fixes full-health maids losing health after import.
- v1.4.1: removed the pre-import existence check (restored in v1.4.3 with the registration-leak issue fixed).
- v1.4.2: fixed forced re-granting of the guide book / smart slab when the "grant on first join" advancements are disabled.
- v1.4.3: modal confirmation when exporting with "keep the maid in the world" unchecked (with a per-world "don't ask again" option); restored duplicate-import pre-check; NeoForge dependency range widened to 1.21–1.22 (exclusive); added the invulnerability toggle (default was on, now off in v1.6.0).
- v1.5.1: fixed a dedicated-server startup crash by moving client-only code out of the mod main class.
Existing Features (v1.3.0 and earlier):
Platform Support:
- Forge, NeoForge and Fabric official builds. Since v1.4.0 minor versions share one JAR per loader (see Supported Versions).
Potion Effect Migration:
- Cross-version potion effect migration. Export saves both vanilla NBT (active_effects) and cross-version normalized data; import auto-recovers based on target version.
- All Methods permanent buff protection. On servers with potion effects disabled, the 11 fixed permanent effects of All Methods structural maids (minecraft:regeneration/strength/resistance/speed, irons_spellbooks:vigor/blight/true_invisibility/abyssal_shroud, goety:save_effects/leeching, youkaishomecoming:native_god_bless) are preserved to the persistent tag by the dual condition "effect ID in whitelist AND Duration=-1".
- Pure effect judgment (whitelist + Duration=-1), no dependency on maid entity identity.
Advancement System:
- Advancement import toggle, configurable whether to restore maid achievement progress.
Post-Import Cleanup:
- Delete source files after import toggle (disabled by default). Only deletes the batch confirmed successful by the server; failed files are retained as-is.
Multiplayer / Server-Side Configuration (OP-managed, synced to clients, non-OP read-only):
- Five server switches: allow clients to import maids (on), allow carrying baubles on import (on), import maid-related advancements (on), restore potion effects on import (on), allow carrying the maid's invulnerability (Substitute Jizo) on import (off).
- Bauble Import Settings: strip bauble attributes on import (off = keep) and the blocked-bauble list.
- Player-side switch: "allow the server to batch-export your maids" (default off / not consented); the OP can only export a player's maids after the player turns it on.
- Per-world switch: skip the confirmation dialog when exporting and removing maids, remembered per save / server, and can be re-enabled at any time.
- Server unified export: OP-only, grouped by player, exports each player's tamed maids within 128 blocks; never removes maids.
- Network limits: single .maid file capped at 512 KiB on the wire; decompressed NBT capped at 16 MiB (anti GZIP bomb).
Other Existing Features:
- AI chat persona and chat history import/export.
- Automatic stripping of inventory and main/off-hand items during export to prevent duplication exploits (baubles are the only exception, and they are constrained by namespace, server settings and the blocked list).
- Full support for Touhou Little Maid: All Methods.
Keywords: maid exporter, maid importer, TLM maid utility, Minecraft maid migration, Touhou maid backup, maid profile editor, 女仆导出器, 女仆导入器, TLM女仆工具, 我的世界女仆迁移, Fabric女仆模组.
Supported Versions
Since v1.4.0, minor versions share one JAR per loader:
| Loader | Minecraft Versions | JAR |
|---|---|---|
| Forge | 1.20, 1.20.1 | maid_file_manager-forge-1.20.1 |
| NeoForge | 1.21, 1.21.1 | maid_file_manager-neoforge-1.21.1 |
| Fabric | 1.20, 1.20.1 | maid_file_manager-fabric-1.20.1 |
| Fabric | 1.21, 1.21.1 | maid_file_manager-fabric-1.21.1 |
Note: the current release is v1.6.0. Since v1.4.3 the NeoForge build's Minecraft dependency range is 1.21–1.22 (exclusive), so both 1.21 and 1.21.1 can load it; actual usability depends on the TLM base mod supporting that version.
How to Use
The mod keeps everything under the maid_file/ folder next to mods:
| Folder | Purpose |
|---|---|
| maid_file/maid_exports/ | export results, per player: maid_file/maid_exports/<player>/ |
| maid_file/maid_imports/ | import source: put the .maid files to import here |
| maid_file/photos/ | candidate profile photos (proportional, longest side up to 512 px) |
| maid_file/maid_photos/ | profile photo library, maintained automatically by the mod — do not edit by hand |
- Export: Press U, click Refresh on the Export tab, select your maid(s), and click Export.
- Import: Press U, switch to the Import tab, click Refresh, choose a file, and click Import (optionally check "Delete source files after import").
- Open Folder: click "Open Export Folder" (or "Open Import Folder" on the Import tab).
- Profile: click the Profile button to view / edit a maid's profile.
- Backup Manager: the "Backup" button in the profile manager title bar, or "Backup Manager" in the game main menu.
- Server Unified Export: only visible to OPs. Click the "Unified Export" button to export each player's tamed maids within 128 blocks, grouped by player.
- Legacy folders (maid_exports/, maid_imports/, config/maid_file_manager/photos/ in the game root) are migrated into maid_file/ automatically on first launch.
Requirements
- TLM (Touhou Little Maid) must be installed.
- Corresponding Forge, NeoForge, or Fabric environment.
- To use the bauble carrying feature with All Methods baubles, Touhou Little Maid: All Methods is required.
- Fabric versions require the corresponding Fabric API.
Notes
- When importing across versions, ensure that the corresponding model exists on your client or the server; otherwise, the maid will appear as Reimu.
- Importing the same maid twice is intentionally rejected with an explicit message; there is no need for any workaround. A maid inside a Soul Talisman cannot be used to bypass this either — a second copy would block the talisman from releasing (same UUID).
- Whether baubles travel on import is decided by the server ("allow carrying baubles on import" plus the blocked list and the modpack whitelist / blacklist); the client cannot bypass it.
- The invulnerability (Substitute Jizo) state is not carried by default; the OP must enable it explicitly.
- Imported base health/attack always return to TLM's vanilla values by favorability level; only legitimate bonuses from baubles / affixes are restored after the maid enters the world.
- About the Backup Manager on a dedicated server: the server only reads its own save and returns data; it never writes or deletes anything. OPs see all players, non-OPs only their own.
- About server unified export scope: Many players think this feature can package all maids on the entire server at once, but it is constrained by design. On one hand, allowing players to directly view others' maid lists could lead to privilege escalation and export disputes; on the other hand, some maids may be in unloaded chunks, or sealed in Soul Talismans, photos, film rolls, and other containers, which unified aggregation cannot technically cover. Therefore, the actual scheme is: each player's exportable scope is limited to maids tamed by themselves within a 128-block radius; server unified export essentially aggregates each player's visible list and hands it to the server host—only when the player is online and the maid is within their loaded range can it be included in unified export. For modpack switches or disaster recovery backups, please notify players in advance to gather at the main city or bring their maids to themselves.
- Fixed in v1.1.1: Resolved the issue where the 20 bonus HP gained from Tribulation Transcendence would disappear after export/import.
- Fixed in v1.1.2: Resolved the issue where imported HP was capped at 20 and abnormal potion effects after import.
- Fixed in v1.2.0: Resolved the NBT export failure caused by the Anchoring Core from All Methods and the resulting blank maid issue.
- Fixed in v1.3.0: Potion effect migration — vanilla NBT and normalized dual data storage; All Methods permanent buffs no longer lost on potion-disabled servers.
- Fixed in v1.4.0: Full-health maids with HP baubles/affixes no longer lose health after import; duplicate imports are explicitly rejected with clear reasons (including batch failure details).
- Fixed in v1.4.2: Importing no longer force-grants the guide book / smart slab when the "grant on first join" advancements are disabled.
- Fixed in v1.4.3: 1.21 potion effects are no longer lost after export/import; restored duplicate-import pre-check without false positives after the original maid was removed.
- Fixed in v1.5.1: dedicated server no longer crashes on startup (client-only code moved out of the mod main class).
- Fixed in v1.6.0: the "Open Export Folder" button in the Backup Manager no longer stays unusable; profile photos no longer draw only the top-left three quarters; read-only profile previews can scroll through long multi-line text; YSM-replaced maids show the correct name and model ID.
- Fabric versions are based on community unofficial ports of TLM. If you encounter issues on Fabric, please first confirm whether they are caused by the port itself.
Links
- Source Code: https://github.com/zgxhzhr/MaidFileManager
- Issue Tracker: https://github.com/zgxhzhr/MaidFileManager/issues
- Author's Bilibili: 逐光星火-执火人
Author: zgxhzhr
License: MIT
Keywords: Touhou Little Maid, TLM, 车万女仆, maid migration, cross-version, 跨版本, 女仆转移, maid export, maid import, 女仆导出, 女仆导入, world transfer, 跨存档, server migration, 服务器迁移, maid backup, 女仆备份, maid profile, 女仆档案, maid data manager, 女仆数据管理, addon migration SPI, 附属数据迁移, All Methods, 万法皆通, maid cross-world, 女仆跨服, Minecraft maid, 我的世界女仆, Forge maid mod, NeoForge maid mod, Fabric maid mod, maid backup manager, save rescue, backup recovery, 备份管理, 存档救援.
——————————————————————————————————————————————
模组名称：Maid File Manager
中文别称：车万女仆档案（迁移）管理器
归属模组：TLM 车万女仆 (Touhou Little Maid)
作者：zgxhzhr（B站：逐光星火-执火人）
开源协议：MIT
源码地址：https://github.com/zgxhzhr/MaidFileManager
MCmod.cn: 车万女仆档案（迁移）管理器 (Maid File Manager) - MC百科|最大的Minecraft中文MOD百科
搜索关键词：车万女仆，TLM，女仆迁移，跨版本转移，女仆导出，女仆导入，跨存档转移，服务器迁移，女仆备份，女仆档案，女仆数据管理，附属数据迁移，万法皆通，All Methods，整合包转移，女仆跨服，我的世界女仆，Forge女仆模组，NeoForge女仆模组，Fabric女仆模组，备份管理，存档救援，崩溃存档恢复。
Maid File Manager 是一款车万女仆的附属模组，围绕两个核心功能：把你的女仆打包带走，以及管理与救援车万女仆自动产出的女仆备份。
无论你是想换个整合包重新开始，还是把单机养成的女仆带到服务器里，这个模组都能让你在 1.20 / 1.20.1 / 1.21 / 1.21.1 之间自由迁移女仆数据，同时支持 Forge、NeoForge 与 Fabric 三大加载器。而当存档损坏或回档时，内置的备份管理让你直接浏览车万女仆自动产出的备份——本机所有存档都能看，联机服务器上在自己权限范围内可见——并把女仆重新捞出来。
注：Fabric 版本基于社区非官方移植的 TLM，非车万女仆本体官方支持。如有相关 Bug，请先确认是否为移植版自身问题。
为什么需要这个模组？
转移女仆这件事，远比想象中复杂。你可能以为把实体数据拷走就行，但实际上女仆的数据——以及她的各种"记忆"——至少分散在四个互不相干的地方：
- 实体 NBT（世界存档内）：模型 ID、任务、4 套物品栏、好感度/经验、YSM 数据、击杀记录、棋类战绩、AI 聊天历史。能随女仆走，但只限于同一存档内；而且直接原样拷贝，实体会带着同一个 UUID 到目标世界引发冲突。
- 文件备份（maid_backups）：按主人 UUID 归档的备份文件。可以拷贝，但目录结构与主人 UUID 硬绑定——换了存档或服务器，玩家 UUID 一变，这些备份就谁也读不出来了。
- 玩家数据（Capability / DataAttachment）：女仆数量、AI token 配额。完全独立于女仆，女仆侧没有任何办法把它一起带走。
- 附属存储（独立 SavedData / Capability / 外部数据库）：这是最隐形的一块。不少女仆附属会把自己的数值与"记忆"存在实体 NBT 之外——誓约/羁绊锁定值、心情与好感类数值、能力解锁、计数器、自定义事件记录等等——仅靠女仆 UUID 与女仆关联。只拷实体，这些数据一个字节都带不走；到了新世界，附属眼里就是一只白纸般的陌生女仆。而且这些数据没有统一迁移通道，每装一个附属都可能踩一次同样的坑。
这意味着：本体没有一键导出导入工具；主人 UUID 是硬关联，换世界就成了无主女仆；跨服没有官方通道；1.20 到 1.21 的大重构让跨版本迁移风险很高；哪怕你手工拷贝实体，附属养成的数值与记忆也会被丢下。
正因为本体在把女仆带走这件事上有这么多不方便的地方，才有了这个模组；v1.4.0 起更进一步，提供标准迁移接口（SPI），附属模组只需一次注册，就能让自己的数据随 .maid 一起搬家。
Maid File Manager 能做什么？
核心功能一 · 把女仆带走（迁移）：
- 一键导出 / 导入：游戏内按 U 键唤出面板，勾选女仆或 .maid 文件，一键导出或还原。
- 批量操作：同时处理多个女仆或文件，导入汇总中逐条列出失败原因。
- 一键打开文件夹：面板中直接打开导出文件夹或导入文件夹。
- 跨版本迁移：1.20 ↔ 1.20.1 ↔ 1.21 ↔ 1.21.1 数据互通。
- 单文件打包：一只女仆一个 .maid 文件，档案头像一并打包带走。
- 女仆档案：游戏内直接查看与编辑女仆的照片、职业、生日、个人资料、偏好与背景故事；导入前还能只读预览 .maid 文件里的档案。
- 防重复导入：同一位女仆无法导入两次，拒绝时给出明确原因；不同玩家在服务器导入同一文件互不冲突，女仆死亡或解散后可正常重新导入。
- 无残留：卸载模组不影响已导入的女仆。
核心功能二 · 管理与救援女仆备份（备份管理）：
- 浏览车万女仆自动产出的全部备份，按「存档 → 玩家 → 女仆 → 备份文件」四层展开，随时导出为 .maid。单人 / 局域网（或从主菜单进入）可一次浏览本机所有存档，不必再翻文件夹、猜 UUID。
- 救援崩溃 / 回档的存档：即便世界已经打不开，女仆备份文件仍在磁盘上，可以直接从备份里把女仆捞进新世界。
- 联机服务器中，管理员（OP）可浏览并定位任意玩家的备份，排查与恢复都更省事。
- 非 OP 玩家也能查看并导出自己名下的备份，无需等待管理员。
- 服务端侧只读：不写入、不删除任何数据。
v1.6.0 新增：女仆档案管理与备份管理
女仆档案管理（按 U 唤出面板 → 「档案」按钮）：
- 查看与编辑女仆档案：照片、职业、生日、个人资料、偏好与技能、背景故事。
- 展示「渡劫」标记（读取车万女仆雷击标记），在线档案与导入预览均可见。
- 多行输入框支持中文输入，并补全 Ctrl+A/C/V/X 剪贴板操作。
- 基础信息区的「模型」栏改为「姓名」栏：设有命名牌（自定义名称）时显示姓名，否则回退显示模型名。
- 档案照片改为外置存储（maid_file/maid_photos/<女仆UUID>.png，最长边 512 像素等比缩放），实体存档不再每次携带图片；导出时仍打包进 .maid，导入界面的只读档案预览仍能看到图片。
备份管理：
- 浏览车万女仆自动产出的备份，按「存档 → 玩家 → 女仆 → 备份文件」四层展开，随时导出为 .maid。
- 单人世界 / 局域网主机直接读取本机存档；从游戏主菜单进入时合并展示本机所有存档，所有存档的备份在一个界面里就能浏览。
- 救援崩溃 / 回档的存档：即便世界已经打不开，女仆备份仍在磁盘上——选中女仆即可导出到新世界。
- 联机服务器中，管理员（OP）可浏览并定位任意玩家的备份；非 OP 玩家也能查看并导出自己名下的备份，无需等待管理员。
- 专业服务端由服务端代读并回传。服务端只读：不写入、不删除任何数据。
- 导出文件一律落在客户端的 maid_file/maid_exports/<玩家名>/ 下。
- 入口：档案管理界面标题栏的「备份」按钮，或游戏主菜单「备份管理」。
- 修复：「打开导出文件夹」按钮此前常黑不可用。
v1.6.0 其他改动：
- 目录统一：导出 / 导入 / 照片一律收纳至 maid_file/（maid_exports、maid_imports、photos、maid_photos），首次启动自动搬运旧目录。
- .maid 文件格式升至 v7，新增档案快照字段。旧版文件（v1～v6）无需转换即可导入；新字段在旧版本模组中被忽略。
- 档案列表改为按存档维度筛选，便于跨存档查找。
- 女仆使用 YSM 模型替换车万女仆本体模型时，导出列表、档案界面与备份列表正确显示 YSM 自定义名称 / 模型名（.maid 内 modelId 仍保持底层 TLM 值，不影响跨版本导入回退）。
- 主界面导入页移除「保留饰品」开关，饰品是否随行统一由服务端设置「导入时允许携带饰品」控制，左侧工具列随之重排。
- 服务端开关「导入时允许携带无敌状态（替身地藏）」默认值由开启改为关闭。
v1.5.0 新增：跨版本饰品属性保留（双向）
- 饰品默认携带，可由服务端关闭。
- 同版本导入走平台层完整物品 NBT 解析，保留附魔、耐久、无法破坏、数据组件等全部状态。
- 跨版本导入双向转换属性：1.20 → 1.21 走 DataFixerUpper 升级物品 NBT；1.21 → 1.20 因 1.20 平台没有 References.ITEM_STACK、DFU 只能升不能降，改为手动降级组件格式（附魔 levels → Enchantments、耐久 damage → Damage 等），附魔 / 耐久 / 无法破坏 / 基础数值等一并保留。
- 仅在来源版本未知或数据无法解析时才还原为同类型全新饰品；转换失败不静默——记 WARN 日志后回退全新化，不阻断导入。
- 允许携带的命名空间：车万女仆本体 + 车万女仆：万法皆通；命名空间之外的饰品一律丢弃。
- 饰品导入设置（服务端配置，仅 OP 可改，客户端进服自动同步、非 OP 只读）：提供「导入时丢弃饰品属性」开关（默认关闭 = 保留属性）与「禁用携带的饰品」清单。清单只列出真正的饰品——以车万女仆本体的饰品注册表判定，工具 / 材料 / 书籍不再混入——支持按名称或 ID 实时搜索。
- 导入后逐件反馈饰品处理结果（被丢弃 / 被还原为全新物品及原因），列表放不下的说明仍会完整送达聊天栏。
- 修复：1.21 系「饰品导入设置」列表滚轮无论上滚下滚都只能向下滚动（1.21 的四参 mouseScrolled 第三参是水平滚动量，滚轮恒为 0，现改取第四参）。
- 修复：1.21 系「饰品导入设置」列表恒为空、显示「没有匹配的饰品」（旧判定用「物品是否实现 IMaidBauble」，而饰品物品本体并未实现该接口；现改为查询车万女仆本体的饰品注册表）。
- 修复：1.21 系导出再导入后药水效果全部丢失（1.21 效果列表键名为小写 active_effects，旧版只识别 1.20 的 ActiveEffects，现双键名兼容）。
v1.4.x 新增与调整：
- v1.4.0：附属模组统一迁移接口 SPI（MaidMigrationProvider + MaidMigrationRegistry），数据随 .maid v5 的 extras 字段承载；同一女仆重复导入拦截（导入实体 UUID 由「源女仆 UUID + 导入玩家 UUID」确定性派生）；血量 / 攻击力基础值无条件回归车万女仆白板值；修复满血带血量饰品女仆导入后掉血（入世界后约 1 秒有界窗口逐 tick 校准）。
- v1.4.1：移除前置重复导入拦截（v1.4.3 在修复登记残留问题后恢复）。
- v1.4.2：修复开启「导入时一并导入女仆相关成就」且关闭开局赠送手册 / 魂符时，导入仍强行补发的问题。
- v1.4.3：取消勾选「保留女仆在原世界中」导出时弹出二次确认窗（可按存档记忆「不再提示」）；恢复重复导入前置拦截；NeoForge 版 Minecraft 依赖范围放宽为 1.21～1.22（不含）；新增无敌状态开关（当时默认开启，v1.6.0 改为默认关闭）。
- v1.5.1：修复专用服务端启动崩溃（客户端专属代码从模组主类剥离）。
v1.3.0 及更早的已有功能：
平台支持：
- Forge、NeoForge、Fabric 均有正式构建。v1.4.0 起同一加载器的小版本合并为单个 jar（见支持版本表）。
药水效果迁移：
- 药水效果跨版本迁移，导出时同时保存原版 NBT（active_effects）与跨版本标准化数据，导入按目标版本自动恢复。
- 万法皆通药水效果保护：禁药水服务器下，万法皆通结构女仆的 11 种固定常驻效果（minecraft:regeneration/strength/resistance/speed、irons_spellbooks:vigor/blight/true_invisibility/abyssal_shroud、goety:save_effects/leeching、youkaishomecoming:native_god_bless）按「效果 ID 命中白名单 AND Duration=-1」双条件写入持久化标签保留。
- 纯效果判定（白名单 + Duration=-1），不依赖女仆实体身份。
进度系统：
- 进度导入开关，可配置是否还原女仆成就进度。
导入后清理：
- 导入后删除源文件开关（默认关闭），仅删除服务端确认生成成功的那批文件，失败文件原样保留。
联机 / 服务端配置（OP 管控，客户端进服自动同步，非 OP 只读）：
- 五项服务端开关：允许客户端导入女仆（开启）、导入时允许携带饰品（开启）、导入时允许携带进度（开启）、导入时允许药水效果（开启）、导入时允许携带无敌状态（替身地藏）（关闭）。
- 饰品导入设置：导入时丢弃饰品属性（关闭 = 保留）、禁用携带的饰品清单。
- 玩家侧开关：「允许服务端统一导出你的女仆」（默认不同意）；玩家开启后 OP 才能导出其女仆。
- 按存档开关：导出并移除女仆时不再二次确认（按存档 / 服务器分别记忆，可随时恢复）。
- 服务端统一导出：仅 OP 可用，按玩家分组导出各自周围 128 格内驯服的女仆，只导出不移除。
- 网络上限：单个 .maid 文件线上体积上限 512 KiB；NBT 解压后上限 16 MiB，防 GZIP 炸弹。
其他已有功能：
- AI 聊天人设及历史记录导入导出。
- 导出时自动剥离背包与主副手物品，防止刷取（饰品是唯一例外，且受命名空间、服务端设置与禁用清单约束）。
- 完整支持车万女仆：万法皆通模组。
支持版本
v1.4.0 起同一加载器的小版本合并为单个 jar：
| 加载器 | Minecraft 版本 | jar |
|---|---|---|
| Forge | 1.20、1.20.1 | maid_file_manager-forge-1.20.1 |
| NeoForge | 1.21、1.21.1 | maid_file_manager-neoforge-1.21.1 |
| Fabric | 1.20、1.20.1 | maid_file_manager-fabric-1.20.1 |
| Fabric | 1.21、1.21.1 | maid_file_manager-fabric-1.21.1 |
注：当前版本为 v1.6.0。v1.4.3 起 NeoForge 版 Minecraft 依赖范围为 1.21～1.22（不含），1.21 原版与 1.21.1 均可加载；实际可用性以前置车万女仆本体对相应版本的支持为准。
使用方法
游戏目录（与 mods 平级）下的 maid_file/ 文件夹：
| 文件夹 | 用途 |
|---|---|
| maid_file/maid_exports/ | 导出结果，按玩家名分子文件夹 maid_file/maid_exports/<玩家名>/ |
| maid_file/maid_imports/ | 导入来源，把要导入的 .maid 文件放这里 |
| maid_file/photos/ | 档案头像的候选图片（等比缩放，最长边不超过 512 像素） |
| maid_file/maid_photos/ | 档案头像图片库，模组按女仆 UUID 自动维护，请勿手动改动 |
- 导出：游戏内按 U 唤出面板 → 导出 Tab 点「刷新」→ 勾选女仆 → 点击导出。
- 导入：游戏内按 U 唤出面板 → 导入 Tab 点「刷新」→ 选择文件 → 点击导入（可勾选「导入后删除文件」）。
- 打开文件夹：面板中点击「打开导出文件夹」（导入 Tab 对应打开导入文件夹）。
- 档案：点击「档案」按钮查看 / 编辑女仆档案。
- 备份管理：档案管理界面标题栏的「备份」按钮，或游戏主菜单「备份管理」。
- 服务端统一导出：仅 OP 面板上可见「统一导出」按钮，点击后按玩家分组导出各自周围 128 格内驯服的女仆。
- 旧版本散落在游戏根目录的 maid_exports/、maid_imports/ 与 config/maid_file_manager/photos/ 会在首次启动时自动搬运并入 maid_file/ 下，无需手动处理。
前置要求
- 必须安装 车万女仆 (Touhou Little Maid)。
- 对应的 Forge、NeoForge 或 Fabric 环境。
- 如需携带万法皆通的饰品，需安装 车万女仆：万法皆通。
- Fabric 版本需对应 Fabric API。
注意事项
- 跨版本导入时，请确保本端或联机主端有对应模型，否则会变成博丽灵梦。
- 同一女仆重复导入是被有意拒绝的，并有明确提示，无需任何"变通方法"；把女仆收进魂符也无法绕过——再导入一份会导致魂符因 UUID 相同无法放出。
- 饰品是否随行由服务端决定（「导入时允许携带饰品」开关 + 禁用清单 + 整合包白 / 黑名单），客户端无法绕过。
- 无敌状态（替身地藏）默认不携带，需 OP 显式开启。
- 导入女仆的血量 / 攻击力基础值一律回归车万女仆白板值，仅饰品 / 词条等合法加成在入世界后恢复。
- 专业服务端的备份管理：服务端只读取自身存档并回传，不写入、不删除任何数据；OP 可见全部玩家，非 OP 仅自己。
- 关于服务端统一导出的范围说明：很多玩家以为这个功能可以一次性打包整个服务器的所有女仆，但实际上它受设计约束。一方面，若允许玩家直接查看他人女仆列表，可能带来越权与导出纠纷；另一方面，部分女仆可能身处未加载区块，或被封进魂符、相片、胶卷等容器内，统一汇总在技术上无法覆盖这些场景。因此实际方案是：每位玩家能导出的范围仅限其半径 128 格以内、由自己驯服的女仆；服务端统一导出本质上就是把每位玩家各自能看到的这份列表汇总后交给联机宿主——只有玩家在线、且女仆在其加载范围内，才能被纳入统一导出。换整合包或灾备备份时，请提前通知玩家集中到主城或各自把女仆带到身边。
- v1.1.1 已修复：渡劫增加的 20 点血量上限在导入导出后消失的问题。
- v1.1.2 已修复：导入后血量上限被锁 20 及药水效果异常的问题。
- v1.2.0 已修复：万法皆通锚定核心导致导出 NBT 失败及由此导致的导入白板女仆问题。
- v1.3.0 已修复：药水效果迁移——原版 NBT 与标准化双份数据存储，跨版本恢复不再异常；万法皆通常驻 buff 在禁药水服务器下不再丢失。
- v1.4.0 已修复：满血带血量饰品/词条的女仆导入后掉血；重复导入（含批量导入）现在有明确的失败原因提示。
- v1.4.2 已修复：开启「导入时一并导入女仆相关成就」且关闭开局赠送手册 / 魂符时，导入不再强行补发。
- v1.4.3 已修复：1.21 系导出再导入后药水效果丢失；恢复重复导入前置拦截后不再误伤已移除的原女仆。
- v1.5.1 已修复：专用服务端启动崩溃（客户端专属代码已从模组主类剥离）。
- v1.6.0 已修复：备份管理「打开导出文件夹」按钮常黑不可用；档案照片头像只画左上四分之三；只读档案预览中长多行文本无法滚动；YSM 换模后展示名与模型 ID 错误。
- Fabric 版本基于社区非官方移植，相关问题请先确认是否为移植版自身原因。
相关链接
- 源码：https://github.com/zgxhzhr/MaidFileManager
- 问题反馈：https://github.com/zgxhzhr/MaidFileManager/issues
- 作者 B站：逐光星火-执火人
Author：zgxhzhr
License：MIT
搜索关键词：车万女仆，TLM，女仆迁移，跨版本转移，女仆导出，女仆导入，跨存档转移，服务器迁移，女仆备份，女仆档案，女仆数据管理，附属数据迁移，万法皆通，All Methods，整合包转移，女仆跨服，我的世界女仆，Forge女仆模组，NeoForge女仆模组，Fabric女仆模组，女仆导出器，女仆导入器，TLM女仆工具，女仆数据迁移，附属迁移接口，换整合包保留女仆，备份管理，存档救援，崩溃存档恢复。
