RailOptimization 2.0-snapshot.3 для Minecraft 26.2 (NeoForge)
Это не последняя версия. Последняя для 26.2 · NeoForge — 2.0Открыть 2.0 →
Тестовая версия — возможны ошибки. Для игры без сюрпризов выберите релиз 2.0.
Файлы · 2
Основной · 98,9 КБ
SHA-1
b80cf0777a3c814a4cb37c058eca6ecfff425b66SHA-5128918dd268ed169054335fe8cb0bb74675f8cda6f70d55d94cdac81f7bc8341a9a21efe804bc69af7ce008a73b83012589c7d824cb5dfad04e7f00dcef5b90008Что изменилось
RailOptimization v2.0-snapshot 3
This snapshot brings RailOptimization to NeoForge, adds persistent configuration, and further reduces powered and activator rail signal-search overhead while preserving vanilla behavior.
✨ What's New
- Added NeoForge support for Minecraft 26.1.x
- Runtime settings are now saved to
config/railoptimization.jsonand persist across game or server restarts - Added
/railoptimization reloadto apply configuration-file changes without restarting - Fabric and NeoForge share the same optimization engine, commands, and configuration behavior
- Configuration writes are handled asynchronously and replaced atomically
🚀 Performance
- Reused block states already read during direct-power checks, avoiding duplicate world lookups on unsuccessful rail signal searches
- Streamlined direct-signal direction checks without changing Minecraft's signal observation order
- In balanced local measurements, complete no-signal searches were about 10% faster at the default power range and 13% faster at
powerLimit=64, with successful and early-exit paths effectively unchanged - No additional per-update allocation was introduced
⚠️ Snapshot Notes
- This is a snapshot intended for testing before the final v2.0 release
- Snapshot builds are only provided for selected Minecraft versions; all supported versions will be updated with the final release
- There are no intentional gameplay behavior changes; vanilla behavior and the default rail power range remain unchanged