@jsprismarine/mapping 0.0.0 → 0.16.0-unstable-20261029132853

package/CHANGELOG.md

@@ -0,0 +1,168 @@
+# @jsprismarine/mapping
+
+## 0.16.0-unstable-20261029132853
+
+### Minor Changes
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`232a1ce`](https://github.com/JSPrismarine/JSPrismarine/commit/232a1ce20b5ade2e33b703300fb671f0c3f62076) Thanks [@filiphsps](https://github.com/filiphsps)! - Read a Bedrock biome and a Bedrock block state back into Java's vocabulary.
+  
+  The seam was one-way, and three things were stuck behind that. A chunk stores a numeric biome id,
+  so `blocks.biome` and `blocks.biomeTags` on the content world adapter both refused - block
+  behaviors and the spawn rules' `is_biome` and `has_biome_tag` had nothing to read. And
+  `@jsprismarine/engine-systems` carries Java's redstone, fluid and piston models, so it spells a
+  direction as a word where Bedrock spells it as a number, which meant a piston arm resolved to no
+  palette state at all and pistons never extended.
+  
+  `bedrockBiomeToJava` takes the number a chunk holds, or the Bedrock identifier, and answers both
+  the Bedrock biome and the Java 26.3 biome behind it. It is total over the 89 biomes the pinned
+  Bedrock data lists: 62 carry a Java source, and the 27 legacy terrain biomes Java deleted in its
+  1.18 rewrite are `BEDROCK_BIOME_LOSSES`, each with a reason rather than a guessed stand-in.
+  
+  `bedrockBlockStates` and `javaBlockStates` translate a whole state record each way. The
+  correspondence is per block and cannot be worked out from a state's name: a dropper's
+  `facing_direction` calls north 2 and a piston's calls it 3, a redstone torch spells north `south`,
+  and a door spells it `east`. The write direction also drops the states a Bedrock block does not
+  carry, which is how Java's piston `extended` disappears. 309 blocks share thirty vocabularies; the
+  27 `(block, state)` pairs with no vocabulary at all are `BLOCK_STATE_LOSSES`.
+  
+  Both tables are generated from the pinned sources and committed, so a version bump regenerates them
+  and the diff is reviewable, and both join the property tests the other domains already have.
+  
+  In `@jsprismarine/prismarine`, the world subsystem answers `blocks.biome` through the biome inverse
+  and `blocks.biomeTags` out of the `minecraft:tags` component of the pack stack's biome definitions,
+  which nothing parsed; `EngineWorld` translates every block it hands the engine and every block it
+  takes back.
+  
+  Breaking: `worldContentGroups` takes a `content` option, the biome registry it reads the tags from.
+  `registriesTable.bedrock.biome` is gone, replaced by the richer `registriesTable.bedrockBiomes`.
+  
+  Also fixes every piston letting light through: when the generated block property table collapses a
+  Java property Bedrock does not carry, it now keeps the value of the Java state nearest the block's
+  default rather than whichever came first. Java lists a boolean's `true` ahead of its `false`, so
+  all twelve piston states took the extended row's `lightDampening` of 0 where Java's retracted
+  piston, which is what a Bedrock piston almost always is, dampens the full 15.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`9e53c61`](https://github.com/JSPrismarine/JSPrismarine/commit/9e53c61399266bf9e26dd87160c45ccd251a21f8) Thanks [@filiphsps](https://github.com/filiphsps)! - Refuse to start when a Java identifier has no Bedrock mapping and no reviewed loss.
+  
+  This is the rule plan section 5 gives the loader, and the reason the mapping module can promise
+  totality rather than hope for it. The machinery existed and nothing ran it: `reportIdentifiers`
+  and `createPackIdentifierResolver` had no caller outside their own tests, the resolver covered 5
+  of the 21 registries the vanilla datapack references, and the one assertion about the vanilla
+  corpus expected every identifier to resolve as `unknown`, which is the opposite of what Phase 0
+  asks for.
+  
+  The content build now resolves every Java identifier the pack stack references. A strict build
+  throws `UnmappedIdentifierError`, naming the identifier, its registry and the pack and file it
+  came from. A normal build keeps going and writes one `identifier.unmapped` error per identifier,
+  the way it already reports the defaults it had to invent, so the startup line that counts content
+  errors counts these too.
+  
+  Closing the gap took three things. `@jsprismarine/packs` falls back to the loaded stack when the
+  resolver has no answer, which closes a `#tag` whose tag file the stack carries and a reference
+  into a registry a datapack fills, such as one loot table calling another; 359 of the vanilla
+  corpus's references resolve that way and never cross to a client. It also reads an `id` field from
+  the keys beside it rather than always as an item, because 26.3 spells five unrelated things `id`
+  and the other four were reaching the report as missing items.
+  
+  `@jsprismarine/mapping` maps mob effects and potions, joined by name against the pinned
+  bedrock-samples metadata, and answers the registries with no Bedrock side from a generated Java
+  26.3 census: a reference into one of them resolves only when Mojang's own data publishes the
+  entry, so a typo still fails the load. The nine registries the server evaluates in Java's own
+  shape are listed with a reason each in `packRegistries.ts`. Five new per-entry losses cover the
+  four mob effects and the one potion Bedrock has no id for, and three registry-wide rows cover
+  banner patterns, goat horn instruments and painting variants, which do reach a Bedrock client but
+  as a short code, a data value and a texture name that no pinned source pairs with the Java id.
+  Each registry-wide row pins its entry count, so a version that adds an entry fails the property
+  test instead of widening the row in silence.
+  
+  Against the real 26.3 datapack: 4088 referenced identifiers, 3977 mapped, 111 allow-listed, none
+  left over.
+  
+  Breaking: `ReferencedIdentifier` carries `source`, `pack` and `path`, and a reference the stack
+  closes itself now reports `known` rather than `unknown`. `MAPPED_REGISTRIES` and the
+  `RegistryLoss` registry union gained `mob_effect` and `potion`, and `RegistriesTable` gained the
+  two tables and their Bedrock name sets.
+
+### Patch Changes
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`cde1039`](https://github.com/JSPrismarine/JSPrismarine/commit/cde1039d276df8d3787b361e072fafdb32a6da9a) Thanks [@filiphsps](https://github.com/filiphsps)! - Translate what a Java block entity holds, so a block entity a structure template saved arrives
+  furnished rather than named. A structure template saves the whole compound and the generator read
+  three fields out of it, the loot table, the spawner's mob and the end gateway's exit, and dropped
+  everything else.
+  
+  A census of Java 26.3's 1511 templates decided what to write and where to stop. They declare 1124
+  block entities once the jigsaws and the structure blocks consumed during placement are set aside,
+  and 149 of those carry contents. The translation covers all 149: 107 banners, 48 containers with
+  stacks or timers, 19 comparators, 14 trial spawners, 5 signs, 5 decorated pots, 2 vaults and 2
+  monster spawners. The census also said where not to go. Every one of the 128 campfires is empty and
+  all their cooking timers are zero, no lectern holds a book, and the bells, skulls, ender chests and
+  sculk sensors carry nothing at all.
+  
+  None of it is a copy. Bedrock keeps a banner's color in the block entity where Java keeps it in the
+  block, and counts the sixteen dyes backwards, so a brown banner is 12 on one side and 3 on the
+  other. It draws the raid banner from one `Type` field and refuses patterns beside it, which is how
+  a pillager outpost banner comes out blank when both are sent. It joins a sign's four text
+  components into one newline-separated string, packs the text color into one ARGB integer and calls
+  the glow flag `IgnoreLighting`. It orders a decorated pot's sherds back, left, right, front where
+  Java names the four faces. It takes a trial spawner's configuration inline where Java may write a
+  reference, and defaults the spawn interval to 20 ticks where Java defaults it to 40.
+  
+  `@jsprismarine/mapping` gains the three vocabularies this needs: Bedrock's short code for each of
+  Java 26.3's 43 banner patterns, checked for totality against the pinned Java census; the Bedrock dye
+  index, derived from the generated item table rather than listed again; and the packed ARGB a Bedrock
+  sign draws each dye in.
+  
+  Six fields are reviewed losses rather than omissions, listed in `BLOCK_ENTITY_CONTENT_LOSSES` and
+  counted on the parity dashboard: a sign's operator-click permission and its Realms-filtered text, a
+  furnace's per-recipe experience tally, a trial spawner configuration written as a registry reference
+  with nothing loaded to resolve it, a banner pattern a datapack shipped, and a named potion, which
+  Bedrock tells apart by a data value no pinned source publishes.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`f8a43ce`](https://github.com/JSPrismarine/JSPrismarine/commit/f8a43ce910da3d8e1c88091c8886a7c1d09ab0c0) Thanks [@filiphsps](https://github.com/filiphsps)! - Drop the right items from the blocks Bedrock spells as a name where Java spells a state.
+  
+  `@jsprismarine/mapping` gains `bedrockBlockStateToJava` and `bedrockBlockToJava`, the inverse of
+  `javaBlockStateToBedrock`, derived from the same generated table. The round trip is exact for all
+  15953 Bedrock states the Java palette reaches.
+  
+  The server resolved a block's loot table by mapping each Java table forward through the block's
+  default state, which never produced the 113 Bedrock identifiers that only a non-default state
+  reaches, so all 59 double slabs, the lit furnace, smoker, blast furnace and redstone ore, the
+  powered repeater and comparator, the inverted daylight detector, the unlit redstone torch and the
+  berried cave vines dropped nothing at all. Resolving the block's own state back to Java reaches
+  them, and carries the Java properties into the roll's `block_state`, so the tables that branch on
+  it are right: a double slab yields two slabs and a grown shelf mushroom yields two mushrooms.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`f370405`](https://github.com/JSPrismarine/JSPrismarine/commit/f37040563ed0cac590fe971ef3a448cb2e01a581) Thanks [@filiphsps](https://github.com/filiphsps)! - New package: the Java Edition to Bedrock Edition identifier seam. Four total lookup functions (`javaBlockStateToBedrock` over all 35723 Java 26.3 block states, `javaItemToBedrock` over 1658 items, `javaEntityTypeToBedrock` over 161 entity types, and `javaIdentifierToBedrock` for biomes and enchantments), backed by tables generated from the pinned GeyserMC/mappings join and this repository's BDS 1.26.51.1 captures, plus a reviewed loss allow list where every known loss carries a reason and a reference. Lookups return typed results and never `undefined`. Chunker's five property tests verify totality, state-set exactness, round-trip identity outside the loss list, and that every output exists in the pinned Bedrock palette.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`c1591b1`](https://github.com/JSPrismarine/JSPrismarine/commit/c1591b1e567a51dc80ecbbdfdbdc8e7c7f4f6c42) Thanks [@filiphsps](https://github.com/filiphsps)! - Add the Java data generator step the pipeline was missing. `pnpm --filter
+  @jsprismarine/bedrock-data run datagen:java` re-checks the fetched server jar's sha1, runs
+  Mojang's `net.minecraft.data.Main` against it, and writes the vanilla datapack to
+  `node_modules/.cache/jsprismarine/vanilla-datapack/<version>/` and the data reports to
+  `node_modules/.cache/jsprismarine/java-reports/<version>/generated/reports/`, the two
+  directories every Java-data reader already looks in. A re-run is a no-op unless `--force` is
+  passed.
+  
+  Nothing produced those directories before, so the data-driven overworld generator failed on
+  every server start with a message naming `fetch:sources` and `dump:java`, neither of which
+  writes them. Those messages now name `datagen:java`, and so does the pack stack diagnostic for
+  a missing Java vanilla datapack.
+  
+  The mapping and item table generators read `java -version` from stdout, which is empty
+  because the banner goes to stderr, so their own fallback run of the data generator always
+  threw "No JDK >= 25 found". They read `java --version` now.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`c9cafc8`](https://github.com/JSPrismarine/JSPrismarine/commit/c9cafc8529e05fe90ea2812920feb76cbcaf4a1b) Thanks [@filiphsps](https://github.com/filiphsps)! - Add `bedrockBlockPropertiesOf`: the Java-sourced per-state block property table (hardness, blast
+  resistance, friction, light emission and dampening, correct-tool requirement, random tick, push
+  reaction, fire odds) keyed by Bedrock block state, with `BEDROCK_ONLY_BLOCKS` naming the blocks
+  that have no Java source and `BLOCK_PROPERTY_CONFLICTS` listing the reviewed collapse
+  disagreements.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`8518afc`](https://github.com/JSPrismarine/JSPrismarine/commit/8518afc7b9ee684ebe4255ce26e7b56d612a145a) Thanks [@filiphsps](https://github.com/filiphsps)! - Add `createPackIdentifierResolver`: the `IdentifierResolver` implementation for the
+  `@jsprismarine/packs` identifier report, answered from the mapping tables. Items, blocks, entity
+  types, biomes and enchantments resolve through their lookups, with `mapped` and `passthrough`
+  reporting as `known` and reviewed losses as `loss`; tag references and uncovered registries report
+  as `unknown`.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`03d0f89`](https://github.com/JSPrismarine/JSPrismarine/commit/03d0f89125f6101873fbee9df425f33497b0cc7a) Thanks [@filiphsps](https://github.com/filiphsps)! - Run data-driven entity dyeing through the item behavior runtime.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`32ce6f2`](https://github.com/JSPrismarine/JSPrismarine/commit/32ce6f2f752e7e89c4445d1936e13a6e243a3a30) Thanks [@filiphsps](https://github.com/filiphsps)! - Preserve Java water states for kelp and water plants during fluid spread, and use Java's sturdy-face rule for kelp support.

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/NOTICE

@@ -0,0 +1,33 @@
+The mapping tables under src/tables/ are generated from GeyserMC/mappings
+(https://github.com/GeyserMC/mappings), commit
+81700ab543c1f4e9f9041f58dac4154ecb0d0c8b, joined against the output of
+Mojang's Java Edition data generator and this repository's own Bedrock
+Dedicated Server captures. GeyserMC licenses that data under the MIT
+license reproduced below.
+
+GeyserMC's own scope note applies here too: GeyserMC only licenses the
+original work its contributors have the right to license. Neither GeyserMC
+nor this repository relicenses Minecraft, its data, or any other material
+owned by Mojang or Microsoft.
+
+The MIT License
+
+Copyright (c) 2019-2026 GeyserMC. http://geysermc.org
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.