Add PoweredRailBuilder world module

[killermelon1458]

Type of change

• Bug fix
• New feature

---

Description

Adds a new world module, PoweredRailBuilder, for constructing configurable powered rail tunnels.

The module automates tunnel building with support for:

• configurable width and height
• rail placement (all powered or mixed modes)
• configurable power source placement (redstone block or torch)
• optional lighting placement
• handling of liquids and falling blocks before construction
• optional Baritone integration for movement between build steps

The goal is to provide a configurable rail-focused tunnel builder with fine control over layout, power placement, and structure.

---

Related issues

None currently.

---

How Has This Been Tested?

• Built against latest upstream master

• Verified successful compilation (BUILD SUCCESSFUL)

• Tested in-game:

  • module appears in World category
  • basic tunnel and rail placement works
  • power spacing behaves as expected
  • Baritone movement works when enabled
  • Compatible with other modules such as KillAura and AutoEat without interfering behavior

• Tested with multiple configurations (rail modes, offsets, power types)

---

Known limitations

• Hotbar management is minimal and may not correctly maintain required items in all cases
• Torch placement logic is less reliable than other light sources and may require refinement
• No advanced optimization for block placement order or path efficiency
• Food can be moved out of the hotbar and not automatically restored

---

Potential improvements

• Split logic into smaller components (placement, pathing, tool handling)
• Replace block list tool selection with mining speed-based detection
• Improve inventory and hotbar management logic

---

Checklist:

• My code follows the style guidelines of this project
• I have added comments to my code in more complex areas
• I have tested the code in both development and production environments

[master7720]

would prolly b better as a addon

[killermelon1458]

Got it, makes sense.

Just to clarify so I build in the right direction:

Is this the kind of feature that Meteor prefers to keep as an addon regardless of implementation (i.e. large/complex automation modules), or was that specific to how this one is currently structured?

I’m rebuilding it anyway, so I want to know whether to treat core inclusion as off the table or something to potentially target with a different design.