@jsprismarine/engine-systems 0.0.0 → 0.16.0-unstable-20261029141316

package/CHANGELOG.md

@@ -0,0 +1,146 @@
+# @jsprismarine/engine-systems
+
+## 0.16.0-unstable-20261029141316
+
+### Minor Changes
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`3ce20e2`](https://github.com/JSPrismarine/JSPrismarine/commit/3ce20e248ddf68967062a79a0b5766bf8ac4fa8c) Thanks [@filiphsps](https://github.com/filiphsps)! - Run every destroyed block through one path.
+  
+  A blast, a stream of water, a piston, fire and a falling block each took blocks out with a rule
+  of their own, and none of them raised the block's `onBreak`. A chest the TNT caught kept its
+  contents, a double chest left its other half paired to air, and what fell was a hardcoded copy
+  of the block rather than Java's loot table.
+  
+  `WorldAccess` gains `destroyBlock`, which the host answers by running the same path a player's
+  break takes: the hook before the write, then the roll with whatever the caller knows, the blast
+  radius for an explosion and nothing at all for a plank the fire burned. It also gains
+  `moveBlock`, so a pushed block carries its block entity instead of being written twice and
+  arriving empty. `WorldAccess.spawnItem` is gone with them.
+  
+  `World` now raises `onNeighborChanged` for every block write rather than only for the content
+  adapter's own, so a torch whose support a command or a generator removed finally hears about it.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`fd43ade`](https://github.com/JSPrismarine/JSPrismarine/commit/fd43ade59e80f19e3e7ef994ca80adb15e1f7907) Thanks [@filiphsps](https://github.com/filiphsps)! - Make fire tick on a running server, and gate it on the 1.21.11 game rule.
+  
+  `Engine.setBlockAndUpdate` raised the six neighbor updates and the extra ones a signal source
+  reaches with, and stopped. Nothing ran the work a block's own `onPlace` does, which is the work
+  that reads the world the new block landed in rather than telling the world about it. Three
+  systems were dead because of it: fire never got the first of the ticks that spread it and burn it
+  out, so placed fire sat where it was lit; dust placed beside a live lever stayed dark; and a
+  piston placed into a position something already powered never extended. `runPlacementUpdates` now
+  runs `FireBlock.onPlace`, `RedstoneWireBlock.onPlace` and `PistonBaseBlock.onPlace` alongside the
+  fluid's, and `createTestEngine` wires a notifying write back through `setBlockAndUpdate` so the
+  package's own harness behaves like the server.
+  
+  `fireTick` takes an options record in place of its `increasedBurnout` flag, and its new `spreads`
+  is Java's `ServerLevel.canSpreadFireAround`: false stops the tick after it has booked the next
+  one, so the fire keeps its place in the tick list and does not even go out. `EngineOptions`
+  gains `canSpreadFireAround` for the host to answer it.
+  
+  The host's answer is `minecraft:fire_spread_radius_around_player`, which 1.21.11 folded
+  `doFireTick` and `allowFireTicksAwayFromPlayer` into. It is an integer with a default of 128 and
+  a minimum of -1, read out of `GameRules.class` in the pinned 26.3 jar: -1 lifts the limit, and
+  anything else is a euclidean distance from the block to the nearest non-spectating player. Mojang's
+  own `GameRuleRegistryFix` converts the two booleans a Bedrock world still spells, so `doFireTick`
+  off is 0, which no player is ever inside. `gameRuleValue` is the registry-resolved read the content
+  adapter already did inline, now shared with the world code that reads a rule outside it.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`abd3869`](https://github.com/JSPrismarine/JSPrismarine/commit/abd38698ac421ed89eda5afc3e6aac1ab03981ae) Thanks [@filiphsps](https://github.com/filiphsps)! - Remove Engine-owned redstone and piston handlers, and route block behavior through resolved content families.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`5e47439`](https://github.com/JSPrismarine/JSPrismarine/commit/5e474396321b54f696760962ceb9d24b85917640) Thanks [@filiphsps](https://github.com/filiphsps)! - Resolve redstone conductor overrides from `minecraft:redstone_conductivity` block components.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`d0b36e7`](https://github.com/JSPrismarine/JSPrismarine/commit/d0b36e7d517f9f057cadbc261c6a77d3cb58329a) Thanks [@filiphsps](https://github.com/filiphsps)! - Route server fluid ticks through data-driven block families, expose liquid state reading from block behaviors, and remove fluid handling from `Engine`.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`3093e34`](https://github.com/JSPrismarine/JSPrismarine/commit/3093e340fc9a98a5a408f3c175e844b576289940) Thanks [@filiphsps](https://github.com/filiphsps)! - Remove legacy fire handlers from the engine and dispatch fire ticks through block behavior families.
+
+### Patch Changes
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`b6eccf4`](https://github.com/JSPrismarine/JSPrismarine/commit/b6eccf49493ed702c5c13eb831ad9fa54258a47d) Thanks [@filiphsps](https://github.com/filiphsps)! - Route block power changes through data-driven redstone hooks.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`bd32c08`](https://github.com/JSPrismarine/JSPrismarine/commit/bd32c08eac967ec9e0068cd56cf1788053539a6b) Thanks [@filiphsps](https://github.com/filiphsps)! - Move slope-directed fluid flow, falling levels, and source conversion into the data-driven liquid family.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`d231208`](https://github.com/JSPrismarine/JSPrismarine/commit/d231208b7ed03ea5f62f14a2f72741881b57f128) Thanks [@filiphsps](https://github.com/filiphsps)! - Route observer pulses through block family hooks
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`3cde97f`](https://github.com/JSPrismarine/JSPrismarine/commit/3cde97f56f87dbf9ce3636a6ccf142950fa23cf8) Thanks [@filiphsps](https://github.com/filiphsps)! - Add the weather cycle, which is Java's `ServerLevel.advanceWeatherCycle` over `WeatherData`: three counters, two flags, and the jar's own durations. `advanceWeatherCycle` is a function from one state to the next rather than something that owns a world, so a host steps it, saves the five numbers that come back, and tells its clients when `weatherOf` changed. `weatherCommandState` is the part of `WeatherCommand` that belongs here, which is which counters each of the three forms sets and the duration it uses when the command names none.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`7b155cd`](https://github.com/JSPrismarine/JSPrismarine/commit/7b155cdeb90769ec011f29706cb65a95832196f5) Thanks [@filiphsps](https://github.com/filiphsps)! - Add `@jsprismarine/engine-systems`, the four engine systems neither edition publishes as data: the
+  tick scheduler, redstone, flowing fluids, and fire spread with the random tick driver. Every
+  constant and ordering rule is read out of the pinned Java 26.3 server jar, which carries original
+  names since Mojang removed obfuscation in 26.1, rather than from a wiki page.
+  
+  All four read and write the world through one `WorldAccess` interface covering block state, block
+  entity data, tick scheduling and its two queries, item drops, sounds, difficulty, weather, rain,
+  dimension, game time, the world random and the height bounds. `createTestWorld` implements it over
+  a map of positions and `createTestEngine` returns a world and an engine wired to each other, so a
+  test builds a real circuit rather than a mock.
+  
+  The scheduler is `LevelTicks`, `LevelChunkTicks` and `ScheduledTick`: Java's drain order, the seven
+  `TickPriority` values of -3 through 3, the rule that a second tick for the same position and type is
+  ignored, and the budget of 65536 ticks per list per game tick. `createNeighborUpdates` is
+  `CollectingNeighborUpdater`, which is what keeps an immediate neighbor update apart from a scheduled
+  tick.
+  
+  Redstone implements Java Edition's rules, because redstone is server-decided and invisible to the
+  Bedrock client. Power runs 0 to 15 through `SignalGetter` and the per-block signal overrides, dust
+  uses `DefaultRedstoneWireEvaluator` rather than the experiment Mojang ships behind a feature flag,
+  repeaters take their delay state times 2 game ticks and lock from a diode on either side,
+  comparators run compare and subtract and read a container's fill, observers pulse 15 for two game
+  ticks on a shape change from the block they face, and pistons use `PistonStructureResolver`
+  unchanged, including the 12-block limit and the slime and honey rules. Quasi-connectivity is
+  implemented; Bedrock's produce and consume tick split, soft inversion, its dust refresh rule and its
+  observer-as-update-detector are not, and the README lists them.
+  
+  Fluids run `FlowingFluid` over Bedrock's two blocks per fluid, encoding the level into Bedrock's own
+  `liquid_depth` by Java's `getLegacyLevel` rule. Water drops 1 level per block, searches 4 for a hole
+  and ticks every 5; lava drops 2, searches 2 and ticks every 30 outside the nether, and drops 1,
+  searches 4 and ticks every 10 inside it. Obsidian, cobblestone, stone and basalt all come out of
+  `LiquidBlock`.
+  
+  Fire is `FireBlock` with the ignite and burn odds read from `@jsprismarine/mapping` rather than
+  restated, running on scheduled ticks 30 to 40 game ticks apart as Java does. The random tick driver
+  is `ServerLevel.tickChunk` with `Level.getBlockRandomPos` transcribed exactly, drawing Java's
+  absolute three positions per section where Bedrock's rule is documented as relative with no
+  published mapping.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`3d89810`](https://github.com/JSPrismarine/JSPrismarine/commit/3d89810e3456d9c9108e1b33535197d2bab4786e) Thanks [@filiphsps](https://github.com/filiphsps)! - Cast Java's explosion rays instead of clearing a sphere.
+  
+  `@jsprismarine/engine-systems` gains `explode`, a transcription of `ServerExplosion` from the
+  pinned 26.3 jar: 1352 rays off the surface of a 16 by 16 by 16 grid, each starting at
+  `radius * (0.7 + random * 0.6)` and losing `(blastResistance + 0.3) * 0.3` per block it crosses and
+  0.22500001 per 0.3-block step. The blocks behind a wall now survive, a one-block moat tames TNT,
+  and the crater is the irregular shape vanilla's is. Entity damage comes off
+  `getSeenPercent`, which grades cover by sampling a grid of rays over the entity's box, and
+  knockback reads `EXPLOSION_KNOCKBACK_RESISTANCE`.
+  
+  The server no longer holds its own model. `entity/Explosion.ts` and the data-driven runtime's
+  `explode` both call the package, so a creeper destroys terrain where it used to leave the hole for
+  later, and every block a blast takes out is rolled through its Java loot table with the
+  `explosion_radius` parameter that `survives_explosion` and `explosion_decay` turn into a `1 / radius`
+  chance.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`276ebd1`](https://github.com/JSPrismarine/JSPrismarine/commit/276ebd1a17e2876e128b41321145a816df6e8918) Thanks [@filiphsps](https://github.com/filiphsps)! - Move redstone placement updates and piston movement into data-driven block families
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`c8ed1c5`](https://github.com/JSPrismarine/JSPrismarine/commit/c8ed1c5b88953b3f5f1e3ccec99e8de623faeeb2) Thanks [@filiphsps](https://github.com/filiphsps)! - Route redstone torch ticks through block family hooks
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`1fa9eda`](https://github.com/JSPrismarine/JSPrismarine/commit/1fa9edaec739e3f7b11648b5662d9860cf569c45) Thanks [@filiphsps](https://github.com/filiphsps)! - Stop a piston and a copper bulb conducting redstone. Java's `Blocks` refuses both through `isRedstoneConductor(Blocks::never)`, but it does so from shared property factories rather than from an inline registration, so the ten blocks they cover were missing from `NON_CONDUCTING_FULL_CUBES` while being opaque enough for `isFullCube` to read them as conductors. `powered_repeater` and `unpowered_repeater` leave the set: Java's `REPEATER` registration calls `isRedstoneConductor` not at all, and the default already refuses them.
+  
+  The surrounding documentation said "26 blocks override it". 26 is the number of call sites in `Blocks`; they cover 65 blocks and 2.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`b3360c0`](https://github.com/JSPrismarine/JSPrismarine/commit/b3360c05087155a4aa71299a2042646fa91d6f14) Thanks [@filiphsps](https://github.com/filiphsps)! - Route repeater and comparator updates and scheduled transitions through their data-driven block behavior hooks.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`59f8ec6`](https://github.com/JSPrismarine/JSPrismarine/commit/59f8ec6fcd56487b167a9641cf74d60601d8af7e) Thanks [@filiphsps](https://github.com/filiphsps)! - Run fire spread, burnout, and scheduled ticks through data-driven block behavior hooks.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`21887ca`](https://github.com/JSPrismarine/JSPrismarine/commit/21887ca1f152fa69516fb80543e32a5ce047ec39) Thanks [@filiphsps](https://github.com/filiphsps)! - Draw random ticks only where Java draws them, which is also what makes an idle world free.
+  `ServerLevel.tickChunks` visits a chunk when a player ticket holds it and draws in a section when
+  that section's palette holds something that ticks; this server drew in all 24 sections of all 441
+  loaded chunks with nobody online. `WorldSystemsView.randomTickChunks` is the world's answer to both
+  halves, and `World` gives it from the players' simulation distance and the chunk's occupied sub
+  chunks. Measured over the real loop on a flat world: 29.5 ms per tick to 3.5 with the section half,
+  and to nothing at all with no players online, against a 50 ms tick budget.
+  
+  `EngineOptions.randomTickHandlers` now receives the block with the position. The engine has just
+  read it to find the handler, so reading it again cost a chunk lookup and a block-state construction
+  in the hottest loop the world has.
+- Updated dependencies [[`232a1ce`](https://github.com/JSPrismarine/JSPrismarine/commit/232a1ce20b5ade2e33b703300fb671f0c3f62076), [`ea083fb`](https://github.com/JSPrismarine/JSPrismarine/commit/ea083fb8d67d0c285724b73bf94b41947afc4013), [`f33a57c`](https://github.com/JSPrismarine/JSPrismarine/commit/f33a57c3750488f1ed77a441ab26b7c1086eff68), [`cde1039`](https://github.com/JSPrismarine/JSPrismarine/commit/cde1039d276df8d3787b361e072fafdb32a6da9a), [`f3fa1c6`](https://github.com/JSPrismarine/JSPrismarine/commit/f3fa1c6bf9096223ac9d2b0396bcc71cd04e244e), [`57f252b`](https://github.com/JSPrismarine/JSPrismarine/commit/57f252b2781508290fac2e842cf37fb652467d66), [`f8a43ce`](https://github.com/JSPrismarine/JSPrismarine/commit/f8a43ce910da3d8e1c88091c8886a7c1d09ab0c0), [`d4afedd`](https://github.com/JSPrismarine/JSPrismarine/commit/d4afeddfc1a6016173261b800813e9f248208db8), [`89a02c8`](https://github.com/JSPrismarine/JSPrismarine/commit/89a02c81dd66293ab2b303851aad61c891535081), [`bfb9a31`](https://github.com/JSPrismarine/JSPrismarine/commit/bfb9a31a40c8173f1b811ee63b2308f357c47fd0), [`b6eccf4`](https://github.com/JSPrismarine/JSPrismarine/commit/b6eccf49493ed702c5c13eb831ad9fa54258a47d), [`e17199e`](https://github.com/JSPrismarine/JSPrismarine/commit/e17199e28be25659495b398dc05d6a48baa2b593), [`18f0d0c`](https://github.com/JSPrismarine/JSPrismarine/commit/18f0d0ca7bfb691c75d2d2453eb21b0126e4a4e3), [`9f58b70`](https://github.com/JSPrismarine/JSPrismarine/commit/9f58b7012e39f08ef869149252312f3617c5d057), [`440e164`](https://github.com/JSPrismarine/JSPrismarine/commit/440e164b88f43548c9c4fe8ae896387157f21701), [`e678a6a`](https://github.com/JSPrismarine/JSPrismarine/commit/e678a6a48dd00568f1186f37f2d460b1c898f059), [`a540a4c`](https://github.com/JSPrismarine/JSPrismarine/commit/a540a4cc5879f62d5d3b39d59100200af8e3d313), [`a4abb61`](https://github.com/JSPrismarine/JSPrismarine/commit/a4abb61b7a03101b4f22ebab35da281066530430), [`f370405`](https://github.com/JSPrismarine/JSPrismarine/commit/f37040563ed0cac590fe971ef3a448cb2e01a581), [`c1591b1`](https://github.com/JSPrismarine/JSPrismarine/commit/c1591b1e567a51dc80ecbbdfdbdc8e7c7f4f6c42), [`c9cafc8`](https://github.com/JSPrismarine/JSPrismarine/commit/c9cafc8529e05fe90ea2812920feb76cbcaf4a1b), [`8518afc`](https://github.com/JSPrismarine/JSPrismarine/commit/8518afc7b9ee684ebe4255ce26e7b56d612a145a), [`5e47439`](https://github.com/JSPrismarine/JSPrismarine/commit/5e474396321b54f696760962ceb9d24b85917640), [`03d0f89`](https://github.com/JSPrismarine/JSPrismarine/commit/03d0f89125f6101873fbee9df425f33497b0cc7a), [`4ab02e5`](https://github.com/JSPrismarine/JSPrismarine/commit/4ab02e5cf76b88f09ba19106e971337c1da2d1b9), [`a3db50e`](https://github.com/JSPrismarine/JSPrismarine/commit/a3db50eef709e1d2e3848d71383d6801d5f69773), [`cc8b110`](https://github.com/JSPrismarine/JSPrismarine/commit/cc8b1109b9c174940cdd4549615a05affb459b9a), [`32ce6f2`](https://github.com/JSPrismarine/JSPrismarine/commit/32ce6f2f752e7e89c4445d1936e13a6e243a3a30), [`35e7df5`](https://github.com/JSPrismarine/JSPrismarine/commit/35e7df54b5bba03f65c9e3a972bac32b01ba4fe4), [`13792da`](https://github.com/JSPrismarine/JSPrismarine/commit/13792daea4f024f559c9392e93328694db22e164), [`9e53c61`](https://github.com/JSPrismarine/JSPrismarine/commit/9e53c61399266bf9e26dd87160c45ccd251a21f8)]:
+  - @jsprismarine/mapping@0.16.0-unstable-20261029141316
+  - @jsprismarine/blocks@0.16.0-unstable-20261029141316

package/LICENSE

@@ -0,0 +1,373 @@
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+    means each individual or legal entity that creates, contributes to
+    the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+    means the combination of the Contributions of others (if any) used
+    by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+    means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+    means Source Code Form to which the initial Contributor has attached
+    the notice in Exhibit A, the Executable Form of such Source Code
+    Form, and Modifications of such Source Code Form, in each case
+    including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+    means
+
+    (a) that the initial Contributor has attached the notice described
+        in Exhibit B to the Covered Software; or
+
+    (b) that the Covered Software was made available under the terms of
+        version 1.1 or earlier of the License, but not also under the
+        terms of a Secondary License.
+
+1.6. "Executable Form"
+    means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+    means a work that combines Covered Software with other material, in
+    a separate file or files, that is not Covered Software.
+
+1.8. "License"
+    means this document.
+
+1.9. "Licensable"
+    means having the right to grant, to the maximum extent possible,
+    whether at the time of the initial grant or subsequently, any and
+    all of the rights conveyed by this License.
+
+1.10. "Modifications"
+    means any of the following:
+
+    (a) any file in Source Code Form that results from an addition to,
+        deletion from, or modification of the contents of Covered
+        Software; or
+
+    (b) any new file in Source Code Form that contains any Covered
+        Software.
+
+1.11. "Patent Claims" of a Contributor
+    means any patent claim(s), including without limitation, method,
+    process, and apparatus claims, in any patent Licensable by such
+    Contributor that would be infringed, but for the grant of the
+    License, by the making, using, selling, offering for sale, having
+    made, import, or transfer of either its Contributions or its
+    Contributor Version.
+
+1.12. "Secondary License"
+    means either the GNU General Public License, Version 2.0, the GNU
+    Lesser General Public License, Version 2.1, the GNU Affero General
+    Public License, Version 3.0, or any later versions of those
+    licenses.
+
+1.13. "Source Code Form"
+    means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+    means an individual or a legal entity exercising rights under this
+    License. For legal entities, "You" includes any entity that
+    controls, is controlled by, or is under common control with You. For
+    purposes of this definition, "control" means (a) the power, direct
+    or indirect, to cause the direction or management of such entity,
+    whether by contract or otherwise, or (b) ownership of more than
+    fifty percent (50%) of the outstanding shares or beneficial
+    ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+    Licensable by such Contributor to use, reproduce, make available,
+    modify, display, perform, distribute, and otherwise exploit its
+    Contributions, either on an unmodified basis, with Modifications, or
+    as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+    for sale, have made, import, and otherwise transfer either its
+    Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+    or
+
+(b) for infringements caused by: (i) Your and any other third party's
+    modifications of Covered Software, or (ii) the combination of its
+    Contributions with other software (except as part of its Contributor
+    Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+    its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+    Form, as described in Section 3.1, and You must inform recipients of
+    the Executable Form how they can obtain a copy of such Source Code
+    Form by reasonable means in a timely manner, at a charge no more
+    than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+    License, or sublicense it under different terms, provided that the
+    license for the Executable Form does not attempt to limit or alter
+    the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+*                                                                      *
+*  6. Disclaimer of Warranty                                           *
+*  -------------------------                                           *
+*                                                                      *
+*  Covered Software is provided under this License on an "as is"       *
+*  basis, without warranty of any kind, either expressed, implied, or  *
+*  statutory, including, without limitation, warranties that the       *
+*  Covered Software is free of defects, merchantable, fit for a        *
+*  particular purpose or non-infringing. The entire risk as to the     *
+*  quality and performance of the Covered Software is with You.        *
+*  Should any Covered Software prove defective in any respect, You     *
+*  (not any Contributor) assume the cost of any necessary servicing,   *
+*  repair, or correction. This disclaimer of warranty constitutes an   *
+*  essential part of this License. No use of any Covered Software is   *
+*  authorized under this License except under this disclaimer.         *
+*                                                                      *
+************************************************************************
+
+************************************************************************
+*                                                                      *
+*  7. Limitation of Liability                                          *
+*  --------------------------                                          *
+*                                                                      *
+*  Under no circumstances and under no legal theory, whether tort      *
+*  (including negligence), contract, or otherwise, shall any           *
+*  Contributor, or anyone who distributes Covered Software as          *
+*  permitted above, be liable to You for any direct, indirect,         *
+*  special, incidental, or consequential damages of any character      *
+*  including, without limitation, damages for lost profits, loss of    *
+*  goodwill, work stoppage, computer failure or malfunction, or any    *
+*  and all other commercial damages or losses, even if such party      *
+*  shall have been informed of the possibility of such damages. This   *
+*  limitation of liability shall not apply to liability for death or   *
+*  personal injury resulting from such party's negligence to the       *
+*  extent applicable law prohibits such limitation. Some               *
+*  jurisdictions do not allow the exclusion or limitation of           *
+*  incidental or consequential damages, so this exclusion and          *
+*  limitation may not apply to You.                                    *
+*                                                                      *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+  This Source Code Form is subject to the terms of the Mozilla Public
+  License, v. 2.0. If a copy of the MPL was not distributed with this
+  file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+  This Source Code Form is "Incompatible With Secondary Licenses", as
+  defined by the Mozilla Public License, v. 2.0.

package/README.md

@@ -0,0 +1,72 @@
+# @jsprismarine/engine-systems
+
+Shared world-system primitives that do not come from Bedrock data: tick scheduling, neighbor
+update ordering, redstone signal calculations, random tick selection, explosions, and the weather
+cycle. Resolved block families own block behavior, including fluid flow, fire, redstone state
+changes, and piston movement.
+
+The Java-derived rules in this package are based on the pinned 26.3 server jar in
+`node_modules/.cache/jsprismarine/java-server/`. Source comments name the Java classes behind the
+transcribed behavior.
+
+## World access
+
+The engine reads and writes blocks through a small `WorldAccess` interface. Block tick scheduling
+lives in `TickScheduler`, and explosions use a separate `ExplosionWorld` interface.
+
+```typescript
+import { block, createEngine, createTestWorld } from '@jsprismarine/engine-systems';
+
+const world = createTestWorld();
+const engine = createEngine(world);
+engine.setBlockAndUpdate({ x: 0, y: 0, z: 0 }, block('minecraft:stone'));
+```
+
+`setBlockAndUpdate` writes the block, runs the six neighbor updates in Java's
+`CollectingNeighborUpdater` order, and reports resulting signal power to the content bridge. It
+does not implement individual block behavior. The active block family's hooks handle placement,
+neighbor changes, scheduled ticks, and state transitions.
+
+## Tick scheduling
+
+`TickScheduler` owns the block and fluid tick lists. A scheduled tick carries a trigger tick, a
+priority, and insertion order. Ticks drain by trigger tick, then priority, then insertion order;
+the per tick budget defaults to Java's 65536 for each list. The host drains the scheduler and
+dispatches each tick to the active block family's `onTick` hook.
+
+`TickList` uses one queue for the whole world. Java shards each list by chunk and merges those
+shards while draining, so a backlog can produce a different order. This queue runs the oldest due
+ticks first.
+
+## Redstone signals
+
+This package calculates weak and strong signal, conductor re-emission, and wire connections for
+the Bedrock block identifiers the content families use. `WorldSystems` reports the resulting
+power to `onRedstoneUpdate`; `@jsprismarine/block-behaviors` owns the redstone components' state
+changes and scheduled behavior. The engine no longer owns their scheduled ticks or state
+transitions; it keeps the signal output rules needed to calculate the shared network.
+
+Resolved `minecraft:redstone_conductivity` values override the Java full-cube conductor default.
+The vanilla overlay supplies the 28 exceptions extracted from Java's block registrations, and
+data-driven packs can declare the same component for their blocks. Collision shapes are not
+published, so the full-cube fallback remains an approximation for partial blocks.
+
+## Random ticking
+
+The driver draws `random_tick_speed` positions from each selected section using Java's
+`Level.getBlockRandomPos` step, `state * 3 + 1013904223`. Positions are drawn with replacement;
+a position whose block does not take random ticks still consumes its draw. Block behavior comes
+from the active family's random tick hook.
+
+## Explosions
+
+`explode` traces Java's 1352 rays from the surface of a 16 by 16 by 16 grid. It returns affected
+positions and entity hits; the host applies damage, knockback, drops, and entity callbacks.
+Blast resistance is read from the mapping table. Exposure treats full cubes as the only
+occluders because neither edition publishes collision shapes.
+
+## Weather
+
+`advanceWeatherCycle`, `resetWeatherCycle`, and `weatherCommandState` model Java's saved rain and
+thunder counters. They are pure functions: the host stores the returned state, applies game-rule
+and dimension checks, and sends any client updates.