Links
Tags
Creators
Details
0.4.0-B
Compatibility
Required content
Changes
RED-OS Update: 0.4.0-B
New Feature: Locking Tag The ultimate security solution! Attach a Locking Tag to any container to protect it with a digital force field.
- Unbreakable & Unopenable: Protected blocks are indestructible and inaccessible to unauthorized players.
- NWID Key: Access is granted only to players carrying a handheld device with the matching Network ID (IDs must be 'Enabled' in the app).
- Advanced Resilience: Titanium-grade tags are immune to water and lava. (Note: Locking tags can still be destroyed by high-explosives like TNT).
System Improvements:
- Next-Gen Jetpack Engine: Complete overhaul of the flight logic. Particle effects are now calculated 100% client-side, providing a massive performance boost on servers.
- Aerodynamic Drag: Implemented a 'Soft Speed Cap' at 120 m/s. Players are now naturally and smoothly slowed down by air resistance at extreme speeds instead of hitting an abrupt barrier.
- Precision Control: Resolved the "Sticky Engine" bug; thrust now cuts out immediately when the spacebar is released (with a minimal 150ms buffer for network stability).
- Zero-Lag UI Response: Handheld apps now respond visually to your actions (such as Trigger Mode switches) instantly without waiting for the next server ping.
- Equipment Upgrades: The Pulse Disintegrator and Ion Exosuit are now fully enchantable.
- Redstone Trigger: Added "Switch Mode" in the handheld edit menu, allowing the trigger to act as a toggleable power source.
- Smart Shortcuts: The 'H' key now toggles the handheld device, allowing you to both open and close the tablet with a single button.
- App Persistence: Fixed a major bug where the handheld would reset to the home screen; it now correctly remembers your last opened app, even when stored in Shulker boxes or Ender Chests.
- Mesh Clarity: Improved routing labels in the handheld app. It now explicitly shows "MODE: VIA [Name]" to make Mesh connections easier to understand.
- Logistics Visuals: Updated the Logistics App icon to the recognizable Oxidized Copper Golem Statue.
Performance & Stability:
- High-Performance Architecture: Full migration from legacy JSON to binary NBT storage, significantly reducing world load times and eliminating periodic saving lag.
- Intelligent ID Indexing: Implemented instant device lookups via a new indexing system, eliminating server "tick spikes" even in networks with hundreds of nodes.
- Smart Signal Caching: Obstruction calculations are now cached in RAM and only refreshed during chunk loads, reducing CPU raytracing overhead by over 99%.
- Decentralized Drone Logistics: Offloaded flight logic from the main server thread. The engine now only processes state transitions upon arrival (Handshake protocol), reducing server overhead by 90%.
- Intelligent Throttling: Client-to-server network traffic has been reduced by 50% during flights and interactions, ensuring a more stable experience on busy servers.
- Physical Inventory Validation: Drone Hubs now verify the actual presence of items before launching, completely eliminating "Ghost Drones".
- Anti-Desync Protection: Improved server-client communication when placing secured tags. You will no longer "lose" items in your inventory if placement is blocked by encryption.
- Auto-Discovery Hubs: Drone Stations now automatically synchronize their local network upon opening the GUI, making IO Tags instantly visible without requiring a manual handheld scan.
- Altitude-Tolerant Pathfinding: Refined route planning for drones that accounts for flight height, ensuring stable mesh connections during long-distance automated transit.
- Seamless Data Migration: Integrated an automated bridge system that converts legacy 0.3.0 networks to the new binary format on first launch with 100% data integrity.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:lRhOulOp:XVkmhCzG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lRhOulOp:XVkmhCzG"
}

