How do I install the Train Rail Save Load skill?

Run npx skillmds@latest add tomevault-io/train-rail-save-load in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Train Rail Save Load safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Train Rail Save Load?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Train Rail Save Load free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Train Rail Save Load?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Train Rail Save Load by tomevault-io

Name: Train Rail Save Load
Author: tomevault-io

Train Rail Save Load

Implement and validate save/load for train and rail systems under the current rail-segment-centric architecture and TrainUnit snapshot-sync model. Use when changing train save data, rail persistence, load order, docking restoration, or persistence tests. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Train/Rail Save Load

Overview

Use this skill for train/rail persistence changes under the current runtime architecture.

Reuse-First Rule

Before adding save/load helpers, search existing train/rail persistence code first.
Prefer existing Game.Train save/load components over parallel implementations.
If duplication is unavoidable, record WHY_NEW_IMPLEMENTATION in code/PR notes.
Recommended pre-check:
- rg --line-number "SaveLoad|Restore|ConnectionDestination|RailPosition|TrainUnitSaveData" moorestech_server/Assets/Scripts

Current Architecture (Must Preserve)

Rail connectivity persists as railSegments and restores via RailGraphSaveLoadService.
Train state persists as trainUnits and restores via TrainSaveLoadService.
Rail block placement/load and segment connectivity restoration are separate steps.

Snapshot Boundary Contract (Must Preserve)

Runtime train sync uses:
- per-unit snapshot event (va:event:trainUnitSnapshot)
- full snapshot API (va:getTrainUnitSnapshots)
If TrainUnit/TrainCar state shape changes, update save/load and snapshot serialization together.
Do not persist transport-only runtime values (sequence IDs, future buffers, queue internals).

Save Data Model

railSegments (RailSegmentSaveData) contains:
- A / B (ConnectionDestination)
- Length
- RailTypeGuid
- IsDrawable
trainUnits (TrainUnitSaveData) contains rail position snapshot + train state + cars + diagram.
TrainCarSaveData includes TrainCarMasterId, IsFacingForward, and stateful car data.

Load Order Contract (Must Preserve)

Load world blocks.
Restore rail segments.
Restore common world/player/entity state.
Restore train units.
Restore docking links.

Reason: train rail-position restoration resolves ConnectionDestination via rail graph provider; restore order must keep this mapping valid.

Rail Segment Restore Rules

Skip null segment entries safely.
For drawable segments, keep current length validation/correction behavior.
Restore through datastore APIs (TryRestoreRailSegment), not ad-hoc graph mutation.

Train Restore Rules

Reset previously registered runtime train state before restore.
Resolve rail position through provider/factory from saved snapshot data.
Restore TrainUnit and TrainCar as one consistent unit.
Rebuild docking state after unit restore pass.
Fail safely per unit on invalid references; avoid corrupting global restore state.

Implementation Checklist

Update serializer and restore path together for new fields.
Update snapshot serialization/apply when state affects runtime sync.
Keep railSegments and trainUnits compatible with load order.
Keep ConnectionDestination resolution contract valid.
Add regression tests for rail reconstruction and train restore consistency.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: train-rail-save-loaddescription: Implement and validate save/load for train and rail systems under the current rail-segment-centric architecture and TrainUnit snapshot-sync model. Use when changing train save data, rail persistence, load order, docking restoration, or persistence tests. Use when this capability is needed.---# Train/Rail Save Load## OverviewUse this skill for train/rail persistence changes under the current runtime architecture.## Reuse-First Rule- Before adding save/load helpers, search existing train/rail persistence code first.- Prefer existing `Game.Train` save/load components over parallel implementations.- If duplication is unavoidable, record `WHY_NEW_IMPLEMENTATION` in code/PR notes.- Recommended pre-check: - `rg --line-number "SaveLoad|Restore|ConnectionDestination|RailPosition|TrainUnitSaveData" moorestech_server/Assets/Scripts`## Current Architecture (Must Preserve)- Rail connectivity persists as `railSegments` and restores via `RailGraphSaveLoadService`.- Train state persists as `trainUnits` and restores via `TrainSaveLoadService`.- Rail block placement/load and segment connectivity restoration are separate steps.## Snapshot Boundary Contract (Must Preserve)- Runtime train sync uses: - per-unit snapshot event (`va:event:trainUnitSnapshot`) - full snapshot API (`va:getTrainUnitSnapshots`)- If TrainUnit/TrainCar state shape changes, update save/load and snapshot serialization together.- Do not persist transport-only runtime values (sequence IDs, future buffers, queue internals).## Save Data Model- `railSegments` (`RailSegmentSaveData`) contains: - `A` / `B` (`ConnectionDestination`) - `Length` - `RailTypeGuid` - `IsDrawable`- `trainUnits` (`TrainUnitSaveData`) contains rail position snapshot + train state + cars + diagram.- `TrainCarSaveData` includes `TrainCarMasterId`, `IsFacingForward`, and stateful car data.## Load Order Contract (Must Preserve)1. Load world blocks.2. Restore rail segments.3. Restore common world/player/entity state.4. Restore train units.5. Restore docking links.Reason: train rail-position restoration resolves `ConnectionDestination` via rail graph provider; restore order must keep this mapping valid.## Rail Segment Restore Rules- Skip null segment entries safely.- For drawable segments, keep current length validation/correction behavior.- Restore through datastore APIs (`TryRestoreRailSegment`), not ad-hoc graph mutation.## Train Restore Rules- Reset previously registered runtime train state before restore.- Resolve rail position through provider/factory from saved snapshot data.- Restore TrainUnit and TrainCar as one consistent unit.- Rebuild docking state after unit restore pass.- Fail safely per unit on invalid references; avoid corrupting global restore state.## Implementation Checklist1. Update serializer and restore path together for new fields.2. Update snapshot serialization/apply when state affects runtime sync.3. Keep `railSegments` and `trainUnits` compatible with load order.4. Keep `ConnectionDestination` resolution contract valid.5. Add regression tests for rail reconstruction and train restore consistency.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/moorestech) — claim your Tome and manage your conversions.

Frequently asked questions