Create: Stressbound

Create: Stressbound is a Minecraft 1.21.1 NeoForge addon for Create 6. It adds server-friendly wireless stress links that can bridge rotational power between local Create networks, remote machines, Create contraptions, trains, and compatible moving structures.

Instead of running shafts across long distances, players can bind a Stress Transmitter to a Stress Receiver with the Kinetic Binder. The receiver then outputs the transmitter's rotational speed while still respecting stress budgets and server-side limits.

Demo

In-Game Test

In-game stress link test

Ponder Tutorial

Ponder tutorial

Wireless Controller Demo

Wireless controller demo

Create Aeronautics Compatibility

Create Aeronautics compatibility demo

Compass Tumbler Template

Compass tumbler template demo

The bundled tumbler template demonstrates analog redstone throttling as a feedback controller. A simulated:gimbal_sensor reads tilt, Create redstone links cross-feed that signal, and Stress Receivers throttle the opposite thrusters to push the body back toward level.

Features

Adds Stress Transmitter, Stress Receiver, and Kinetic Binder.
Provides a dedicated creative tab: Create: Stressbound.
Transfers rotational speed through saved stress links without requiring a physical shaft line.
Reserves configurable SU budgets per receiver to avoid free stress duplication.
Supports static Create kinetic networks.
Supports runtime anchors for Create contraptions and Create trains.
Includes heuristic runtime-anchor support for Create Aeronautics / Simulated-style moving structures.
Supports analog redstone throttling on both transmitters and receivers.
Displays link state, remote speed, requested SU, and granted SU through Create goggles.
Provides Ponder scenes for basic linking, moving-structure behavior, and the compass tumbler template.
Ships a placeable tumbler structure template for testing feedback-driven Create Aeronautics / Simulated-style builds.
Includes English and Simplified Chinese localization.
Keeps server control in config: link limits, receiver limits, stress budgets, overload mode, and evaluation interval.

Requirements

Minecraft 1.21.1
NeoForge 21.1.x
Create 6.0.10
Ponder 1.0.82+
Flywheel 1.0.6
Java 21

Optional compatibility targets:

Create contraptions
Create trains
Create Aeronautics / Simulated-style moving structures

Quick Start

Place a Stress Transmitter next to an existing powered Create kinetic network.
Place a Stress Receiver where you want remote rotational output.
Right-click the transmitter with a Kinetic Binder to store it.
Right-click the receiver with the same binder to create the link.
Connect shafts, gearboxes, or machines to the receiver output.
Wear Create goggles to inspect speed, status, and SU budget.

Useful interactions:

Shift-right-click a receiver with the Kinetic Binder to clear that receiver's link.
Shift-right-click air with the Kinetic Binder to clear the stored transmitter selection.
Use a Create wrench to adjust block facing as usual.

Tumbler Template

Place the bundled compass tumbler structure with:

/place template create_stressbound:stressbound/tumbler

The template uses a motor/transmitter bank as its remote stress source, four side receivers with propellers for corrective thrust, a center receiver with a gyroscopic propeller bearing, and four redstone-link channels driven by the gimbal sensor. Because this is a feedback build, keep redstoneEvaluationIntervalTicks at 1 so output changes follow the tilt signal every tick.

Stress Budget Model

Stressbound is designed to avoid turning remote transmission into free power.

Each receiver reserves a configurable SU budget. During evaluation, the transmitter checks the available stress of its local network and grants output only if the linked receivers fit within the configured limits.

Important behavior:

A transmitter does not generate stress by itself.
A receiver outputs the remote rotational speed only while the link is valid and loaded. Analog redstone can throttle either endpoint from full output at signal 0 to stopped at signal 15.
Strict overload mode can shut down all receivers on a transmitter when total reserved stress exceeds available stress.
Server owners can limit links per player, receivers per transmitter, and max SU per link.

Commands

The following commands require permission level 2:

/stressbound links list
/stressbound links remove <uuid>
/stressbound links removeplayer <player>
/stressbound links setstress <uuid> <su>
/stressbound links setallstress <su>
/stressbound compat

For high-speed testing, raise the reserved stress budget of existing links:

/stressbound links setallstress 8192

If that is still not enough for your setup, raise it further:

/stressbound links setallstress 16384

Configuration

The common config is generated at:

config/create_stressbound-common.toml

Common options:

defaultRequestedStress: default SU reservation for newly bound receivers.
maxStressPerLink: maximum SU per link. Use -1 for unlimited.
strictOverloadMode: when enabled, over-budget transmitter groups stop instead of partially granting receivers.
evaluationIntervalTicks: base server tick interval for recalculating link state and stress budgets.
redstoneEvaluationIntervalTicks: faster interval used while redstone throttling is enabled. Keep this at 1 for feedback builds such as the tumbler template.
maxLinksPerPlayer: maximum active links owned by one player.
maxReceiversPerTransmitter: maximum receivers bound to one transmitter.
transmitterPoweredStops: redstone signal throttles transmitter output.
receiverPoweredStops: redstone signal throttles receiver output.

Existing links store their RequestedStress in world data. Changing defaultRequestedStress affects new links only. To update existing links, rebind them or use:

/stressbound links setallstress <su>

Compatibility Notes

Current support:

Static Create kinetic networks: supported.
Create contraptions: runtime anchor support.
Create trains: runtime anchor support.
Create Aeronautics / Simulated-style bodies: heuristic runtime anchor support.
Valkyrien Skies: detected, but full runtime bridging is not implemented yet.

For server safety, moving receivers do not continuously rewrite Create kinetic networks while riding moving entities. Links remain saved and recover when endpoints return to a supported static/runtime state.