tickmender-1.5.1.jar
Curse Maven Snippet
What's new
1.5.1 - 2026-10-26
One new switch: supplementariesBookPileLimit, on by default. TickMender now has 47 switches. The
46 of 1.5.0 are unchanged, with their defaults. Four things changed in the code (the new switch,
the lists of versions, the stop line and the scan cache line), a few statements in the README were
corrected, and the documentation of the compass wear was made exact (see below).
Supplementaries (supplementariesBookPileLimit): a book used on a full book pile no longer crashes the game
supplementariesBookPileLimit: a crash that Supplementaries 1.21.1-4.0.2 and Underlay 1.0.5 cause together. A book used on a block next to or under a Supplementaries book pile that already holds four books (the most) made the game fail withIllegalArgumentException: Cannot set property books=[1, 2, 3, 4] to 5 on Block{supplementaries:book_pile}, it is not an allowed value(a client on its render thread, a dedicated server on its server thread). The game never asks a full pile for the state of another book, becausecanBeReplacedisfalsefor it; Underlay's overlay placement asks, for a click the game has refused, before it looks at what stands there, and the pile'sgetStateForPlacementadds the book without checking the limit. A full pile (the vertical and the horizontal block) now answersnull, "nothing to place", which Underlay and the game accept: the click does nothing, no item is used up, nothing is changed. A pile with room for a book, an empty position and every other block are placed exactly as before.- It applies to Supplementaries 1.21.1-4.0.2 only (the version whose jar was read with
javap); with another version the switch isidle (written for Supplementaries 1.21.1-4.0.2, installed is ...). Underlay 1.0.5 and Supplementaries 4.0.2 are the latest versions; no upstream fix was found. - Not yet seen in a running game. The names of the injected methods (
method_9605ofBookPileBlockand ofBookPileHorizontalBlock) were read in the real jar; the tests run stand-ins. The start line shows whether the fix was applied.
Four version-gated fixes accept a list of versions
Until 1.5.0 each of these four fixes was applied to one exact version of its target mod and was
idle with every other. For each of them the class it relies on was compared in the jars of the
further versions (same SHA-256, empty javap diff), so the fix now accepts an explicit list of
versions. A list, never a range: any version that is not on it is still idle.
| Switch | Target mod | Until 1.5.0 | Now |
|---|---|---|---|
puzzlesLibConfigHolderLookup |
PuzzlesLib | 21.1.62 | 21.1.62, 21.1.64, 21.1.66 |
twilightForestModelEvents (client) |
Twilight Forest | 4.8.734 | 4.8.734, 4.8.754 |
twilightForestFlaskData |
Twilight Forest | 4.8.734 | 4.8.734, 4.8.754 |
biomesWeveGoneConfigWrite |
Oh The Biomes We've Gone | 2.6.0 | 2.6.0, 2.6.3 |
puzzlesLibConfigHolderLookup:ConfigHolderImplis byte-identical in 21.1.62, 21.1.64 and 21.1.66. 21.1.63 and 21.1.65 were not available to compare and are not on the list.twilightForestModelEvents:TFClientSetup,TwilightForestModandJarRenderer*are identical in 4.8.734 and 4.8.754 (17 other classes differ).twilightForestFlaskData:PotionFlaskTrackingAttachmentis identical, and the defect (optionalFieldOf(..., null)) is still in 4.8.754.biomesWeveGoneConfigWrite:ConfigLoaderandConfigLoader$1are identical, with all four injection places as before; the write-back is still unprotected in 2.6.3.- The idle text names the list, for example
idle (written for PuzzlesLib 21.1.62, 21.1.64 or 21.1.66, installed is 21.1.67). The text for a fix of one version is unchanged. - In a pack with PuzzlesLib 21.1.66, Twilight Forest 4.8.754 and Biomes We've Gone 2.6.3 (the Nytheria pack) these four fixes were idle with 1.5.0 and are active again.
- Compared in the jars only, not run in a game. The comparison is static; none of the four has been seen working with the new versions yet. The start line shows whether they were applied.
Stopped-server statics (stoppedServerModStatics): the stop line names the skipped fields
The line written when a server has stopped said only ... 6 of 16 known fields were empty or their mod is not installed, so it could not be seen which of the sixteen fields were skipped (for
example whether BCLib's and WorldWeaver's were). It now names them, in two groups:
... released from the stopped server (...); 13 of 16 known fields had nothing to release: empty: <Mod Class.field>, ...; mod not installed: <Mod Class.field>, ...
empty: the mod is there and the field was null or the collection was empty; mod not installed:
the class does not exist. A group with no field is left out, and when nothing was skipped the line
ends after had nothing to release. On a dedicated server the BCLib entry is always listed under
empty, because it is not looked at there. What is released does not change.
CraftTweaker scan cache (craftTweakerScanCache): the log says why it rebuilt
When the stored key differs from the current one, the scan cache logs one INFO line that names the first class path entry that changed, was added or was removed:
TickMender: CraftTweaker scan cache: rebuilt, the class path changed: <entry> was <old> and is now <new>
or <entry> is new or <entry> is gone, with (+N more) when more than one differs. A file written
by 1.5.0 does not list its entries, so for it the line ends (the old file does not list its entries); the same ending without a name is (no single entry differs) when the file lists its
entries and none differs. The file .cache/tickmender/ctscan-<side>.json gained an optional array
fingerprint with the readable lines of the key, about 100 to 150 bytes per class path entry. It
takes no part in the decision: a file without it is read as before, and hit and miss are decided by
the key as before. A damaged file or one of another format is deleted without this line.
Compass wear (naturesCompassWear, explorersCompassWear): documentation made exact
A behaviour probe against the real Nature's Compass 2.6.0 and Explorer's Compass 2.6.0 (see the README, "The compass wear probe") showed three behaviours that the 1.5.0 text did not state or stated too loosely. The code is unchanged; the README, this file and the CurseForge description now say:
- The levels of a search that finds nothing are not refunded. They are charged when the search starts. Only the use and the cooldown are spared, so "a search that finds nothing costs no use and starts no cooldown" does not mean it is free.
- The cooldown overlay on the item is set lazily. It appears on the first refused right-click or
refused search after a successful one, not at the instant of the success. The cooldown itself is
enforced from the
laststamp from the moment of the success. - Two more known limits. A second search started while the first is still running is allowed (no
laststamp yet) and charged again, the compass mod stops the first worker, and only the search that ends successfully counts as a use. Explorer's Compass also leaves a stalependingstamp when the structure does not exist in the dimension at all; it is harmless and the next search overwrites it.
README
chunkSendingExpiryScan: its number (about 0.3 ms per tick) was measured with Chunk Sending 3.9 and no longer holds for 4.1. Chunk Sending 4.1 fixed the full-map walk itself (an insertion-ordered set, and the walk stops at the first entry that has not expired), compared in the bytecode of the two versions. The fix has no version gate, stays active and is harmless; it is redundant with 4.1.stoppedServerModStatics: BCLib and WorldWeaver 30.5.1 and later clear their own references at a server stop. The entries for these two stay (the fields still exist), but they are redundant from 30.5.1.- Target versions that were checked and named: Artifacts 1.0.1 (
DoubleJumpbyte-identical to 1.0.0), Twilight Forest 4.8.754 (the spawn lookupgatherPotentialSpawnsandTFPortalBlockare identical), Polytone 5.1.2 and 5.3.1 (the same). The older versions stay named. - Build of 1.5.1: 702 tests (686 in
test, 8 intestFixesOff, 8 intestFabricApi).
Updating from 1.5.0
Replace the jar. The new switch supplementariesBookPileLimit is added to an existing
config/tickmender.json with its default (true); everything already in the file is kept. Whoever
wants the old behaviour sets "supplementariesBookPileLimit": false. The scan cache is rebuilt once
at the first start, with the new INFO line ending (the old file does not list its entries), and
the file then holds the fingerprint array. The four fixes with a list of versions become active
where they were idle.
This mod has no additional files