redstones-engineering

# Redstone Systems Engineering — 1.0.20 **Minecraft:** 1.21.1 **Mod Loader:** NeoForge 21.1.249+ **Java:** 21 **Release Type:** Alpha **License:** MPL-2.0 ## Required Dependencies RSE currently requires the following platform mods: * **Just Enough Items (JEI)** — 19.27.0.336 or newer compatible 19.x version * **Jade** — 15.10.6 or newer compatible 15.x version * **GeckoLib** — 4.9.2 or newer compatible 4.x version * **Cloth Config API** — 15.0.140 or newer compatible 15.x version * **Fusion (Connected Textures)** — 1.3.14 or newer compatible 1.x version These are intentional runtime platform dependencies and are not bundled inside the RSE JAR. *** ## Alpha 1.0.20 Redstone Systems Engineering 1.0.20 Alpha expands the project from a collection of engineering blocks into a more complete Minecraft-native engineering systems environment. RSE preserves vanilla Minecraft's **0–15 world-facing redstone boundary** while extending it through instrumentation, signal conditioning, sampling, control, communications, metrology, mechatronics, diagnostics, commissioning, and engineering evidence. The current engineering workflow is: **Measurement → Conditioning → Sampling → Control → Actuation → Optimization → Acceptance → Evidence → Comparison** ## Engineering Instrumentation Expanded engineering measurement and diagnostic infrastructure, including support for: * Signal measurement * Engineering probes * Signal analysis * Oscilloscope-oriented instrumentation * Logic analysis * Calibration systems * Measurement quality * Saturation and range diagnostics * Engineering topology inspection Measurement remains separated from control and intervention wherever possible. ## Signal Processing Expanded signal-conditioning and data-acquisition systems: * Analog Signal Conditioner * Precision filtering * Sample-and-hold behavior * Threshold processing * Edge detection * Pulse shaping * PWM * Signal taps * Timing and sampling infrastructure World-facing vanilla-compatible signals remain bounded to **0–15**. ## Engineering Port Architecture RSE uses explicit engineering ports to describe: * Physical face * Engineering domain * Input/output direction * Semantic role * Measurement range * Signal quality * Vanilla compatibility Topology diagnostics can identify conditions including: * Connected * Open * Isolated * Domain mismatch * Direction mismatch * Unloaded Visualization and UI remain downstream observers of authoritative simulation state. ## Control Engineering The **Discrete PID Controller** provides closed-loop control functionality with engineering-oriented state including: * Setpoint * Process value * Error * Control output * Automatic/manual operation * Inhibit state * Tuning presets * Rise time * Settling time * Overshoot * Saturation events * Mode-transfer tracking PID commissioning remains server-authoritative. ## Closed-Loop Commissioning RSE now evaluates controller behavior using explicit commissioning evidence rather than only checking whether an output eventually reaches a target. Commissioning can track: * Rise time * Settling time * Overshoot * Error * Saturation * Operating mode * Inhibit state * Commissioning score Results can be classified as: `IDLE / RUNNING / PASS / MARGINAL / FAIL` ## Fault Injection Engineering systems can be evaluated under bounded disturbances. Current infrastructure includes concepts such as: * Noise injection * Latency * Bias * Dropout * Actuator saturation Fault injection modifies test conditions without giving diagnostic or UI systems authority over the underlying simulation. ## Metrology & Calibration RSE includes shared measurement-quality infrastructure for engineering instrumentation. Supported concepts include: * Repeatability * Bias * Drift * Noise * Resolution * Saturation * Sample age * Measurement uncertainty proxy * Reference-versus-observed calibration The uncertainty value is intended as an engineering diagnostic proxy rather than a formal laboratory uncertainty certification. ## Multi-Domain Engineering RSE includes multiple explicitly separated engineering domains rather than treating every cable as a universal wire. Current systems include: * Vanilla/redstone signal transmission * Copper electrical systems * Lapis precision signaling * Quartz timing systems * Instrument buses * Optical systems * Magnetic systems * Thermal systems * Pneumatic systems * Radio communication * Free-space optical communication * Mechanical and vibration systems Cross-domain transmission occurs through appropriate converters, transducers, terminals, emitters, receivers, and scalers. ## Electrical Engineering Electrical systems include components such as: * Copper electrical cables * Voltage sources * Resistive loads * Series resistance * Capacitors * Fuses * Circuit meters * Electromagnets * Induction components ## Communications & Data Systems RSE includes engineering communication infrastructure such as: * 8-bit buses * Byte encoding and decoding * Serial data * Serializers and deserializers * Differential signaling * Signal regeneration * Radio transmission * Optical communication ## Pneumatics & Mechatronics Engineering systems include: * Compressors * Pneumatic piping * Air reservoirs * Regulators * Isolation valves * Check valves * Flow measurement * Proportional valves * Safety relief * Pneumatic cylinders * Servo actuators * Position feedback Mechanical and mechatronic visualization remains driven by authoritative simulation state. ## Engineering Acceptance RSE can combine topology and commissioning evidence into an engineering acceptance result: `NOT_READY / PASS / MARGINAL / FAIL` Acceptance is a read-only interpretation layer. It does not become another controller, network solver, or simulation engine. ## Commissioning Run History Alpha 1.0.20 introduces explicit bounded engineering-run capture. PID Controllers can capture authoritative acceptance evidence for later comparison. Current run-history behavior includes: * Explicit player-owned capture * Maximum 8 captured records per PID Controller * Bounded controller history storage * Sequence identification * Captured tuning preset * Captured game tick * Acceptance result * Commissioning score * Topology evidence The current Alpha history is transient diagnostic evidence rather than permanent world-save laboratory storage. ## Baseline Comparison The latest engineering runs can be compared as: `IMPROVED / SAME / REGRESSED / INCOMPARABLE` Comparison considers: * Commissioning-score change * Topology-issue change * Acceptance severity * Evidence availability This allows RSE systems to be evaluated against previous engineering baselines instead of treating every test as an isolated result. ## Engineering Interface RSE now includes a shared engineering UI framework. Current formal interactive engineering interfaces include: * **Analog Signal Conditioner** * **Discrete PID Controller** * **RSE Diagnostics Console** Engineering screens can expose: * Overview * Ports * Configuration * Diagnostics * History UI state remains synchronized from authoritative game state. ## RSE Diagnostics Console A new diagnostics console is accessible through the player inventory. Features include: * RSE-related INFO/WARN/ERROR capture * ALL / WARN+ / ERROR filtering * Runtime version information * WARN and ERROR counters * Pagination * Clear * Copy Report * Bounded session-local diagnostic storage * Sanitized diagnostic output The Diagnostics Console is observer-only and does not modify engineering simulation state. ## Functional Verification RSE's automated verification now includes: * Java compilation * Gradle tests * Repository and resource audits * Dependency verification * Engineering Port regression gates * Metrology regression gates * Control and commissioning verification * Acceptance and evidence verification * UI authority checks * Diagnostics authority checks * NeoForge Minecraft GameTests * Clean JAR build * SHA-256 artifact generation Current automated in-world testing includes **34 required Minecraft GameTests**. ## Visual & Release Improvements * Added the official RSE penguin engineering logo * Added the logo to NeoForge mod metadata * Expanded the internal mod description * Added visible dependency information * Improved release-facing dependency documentation * Updated README dependency visibility * Maintained MPL-2.0 licensing * Continued replacement of placeholder visuals with dedicated RSE engineering textures ## Alpha Notice This is an **Alpha release**. Core systems are functional and extensively regression-tested, but APIs, balance, configuration, interfaces, engineering behavior, recipes, visuals, and persistence models may still change during continued development. Bug reports and reproducible diagnostic reports are especially valuable during the Alpha phase.