Foundations PL4 1.6.4 - 0.2a-legacy-preview.3

Legacy item, fluid and energy transport preview. Further API testing is still required.

Added

Craftable energy exporters, importers and a 100,000-unit built-in energy buffer. This target uses PL4-owned sided energy extension (not RF/FE/EU/J compatibility). The default is 400 units per exporter every 10 ticks. Empty-handed sneak-right-clicking a buffer generates 40 units, with a saved per-buffer 10-tick cooldown. Server configuration can disable manual generation or energy transport independently. This is deliberately small manual generation, not an assumed conversion from a foreign power system.

Connect source buffer -> export node -> existing cable -> import node -> destination buffer. Sneak-click the export/import face that points toward the adjacent endpoint. All PL4 hosts and buffers must have the same owner. Powered exporters/importers/buffers pause. Buffers are endpoints, not network bridges. /pl4legacy recipes includes all twelve registered recipes; right-click and /pl4legacy inspect show energy amount, unit, capacity, escrow and faults.

Energy extracted but not yet accepted is persisted in escrow. Execute exceptions and invalid results block replay. Removal creates a sealed energy recovery cell; right-click a compatible owned buffer to restore healthy contents, including partial restores. Uncertain, malformed or differently labelled energy stays quarantined. Recovery follows normal world item-drop semantics: another mod cancelling/deleting drops can still void dropped contents. There is no atomic crash-commit guarantee across external providers/world saves, and provider simulation must be non-mutating.

Native Forge Energy integration is implemented on 1.12.2. 1.6.4 intentionally uses PL4's own integer units and sided extension API; it does not claim an RF, EU, FE or Joules port merely because built-in energy works. Dedicated external-provider fixtures exercise the extension contract. Installed Thermal/CoFH, IC2, GregTech, Mekanism and other provider combinations remain NOT_TESTED/unimplemented as appropriate. No external core mod is bundled or mandatory.

Validation and limits

Publication requires the native build, existing item/fluid rules, new energy rules, all 89 isolated native server scenarios, the fixture cleanup/save guard and runtime packaging checks. These are dedicated-server scenarios, not modern GameTests. Test fixture classes are never included in the runtime.

1.12.2 uses Forge 14.23.5.2864 and Java 8. Experimental 1.6.4 uses Forge 9.11.1.1345 and Java 7 at runtime; its development API remains 9.11.1.960 with modern Gradle/Java 21 and a Java 8 compiler emitting Java 7 bytecode. New 1.6.4 configurable block IDs are 3506/3507/3508; the energy recovery item config ID defaults to 12501 (native item offset applies). Existing IDs are retained.

Back up worlds. Update both client and server and remove the prior JAR. Schema 3 retains existing item/fluid fields and adds energy; do not downgrade an energy-containing world. 1.6.4 is experimental with legacy player-name ownership, not authenticated UUID ownership. Keep obsolete runtimes isolated/trusted. Owner checks protect PL4-to-PL4 routing and player interaction; generic automation capabilities cannot authenticate another mod's player identity.

Advanced displays, tank/energy GUI gauges, multipart geometry, wireless storage, complete scripting, foreign-energy adapters, installed-mod combinations, real-client visuals, live multiplayer and sustained performance acceptance remain open. Full-block visual assets are preliminary. The modern Forge/NeoForge targets are unchanged by this legacy update. GitHub releases are gated; CurseForge publication is not part of this pipeline.