Add configurable multi-track rail generation and persistent in-game editing

[Jasupa]

Rail Generator v2 replaces the fixed rail preset with saved rail types. Builders can generate one to eight aligned tracks with individual gaps, sleepers, and optional overhead poles, supports and wires, then manage their presets in-game.

Implementation

• Separate configuration, generation and menu code. Store custom types in versioned rail-types.yml, with validation and transactional save/delete behavior so failed writes do not change active types.
• Add selection, search, pagination, creation, editing and deletion menus, including individual track gaps and overhead settings.
• Validate path overlap, the terrain preparation envelope and the complete placement count before queuing blocks. Abort with a clear error if terrain preparation cannot read the region.
• Preserve every ballast entry, its order and repetitions when editing or copying a type. The current picker selects one block: explicitly choosing a block replaces the mix, as explained in the editor. Saving unrelated changes preserves the entire mix.
• Use the shared permission helper and existing denial-message logic. Reloading types requires btt.generator.rail.edit (the rail type edit permission); menu access alone does not allow reload.
• Remove the incomplete early block estimate. Prepared-region limits and the exact generated block count cover sleepers and overhead infrastructure.
• Create the track-spacing +/- items directly; the center item opens the individual-gap editor.

The track-switch setting stores a preference for future support; it does not generate switches. Dependency and Shadow relocation settings remain unchanged from main.

Commit batches

1. feat(rail): add persistent multi-track railway generation and editor — consolidates the previous implementation, excluding the unrelated build changes.
2. fix(rail): preserve ballast mixes and enforce generation safeguards — addresses the review findings and adds ballast regression tests.

Both batches are based on main at a60f67293681dda3aed4085634038a3342571942.

Validation

• Gradle build passed, including tests and Shadow packaging with the original build configuration.
• Regression tests cover unrelated edits, copying a type and explicitly replacing ballast, including repeated materials.
• git diff --check passed.

Requirements

Rail Generator v2 requirements

[github-actions]

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[Zoriot]

Solid Rail Generator v2 overall: clear package split, transactional save/delete, overlap checks before placement, and a usable in-game type editor.

Main concerns: data loss when editing multi-block ballast, missing permission on reload, underestimated pre-check for block count, and missing null-guard after terrain prep.

In game testing is pending - will be done till Sunday night, review partly done by Cursor

Please rebase. Going forward please explain changes which may not be clear in the commit so it's easier to follow and review.