TickMender

37 switchable fixes for crashes, memory leaks, server lag and slow starts in large Fabric 1.21.1 packs. No gameplay change.
Back to Files

tickmender-1.5.3.jar

File nametickmender-1.5.3.jar
Uploader
NavrelisNavrelis
Uploaded
Oct 28, 2026
Downloads
8
Size
464.3 KB
Mod Loaders
Fabric
File ID
9351267
Type
R
Release
Supported game versions
  • 1.21.1

Curse Maven Snippet

Fabric

modImplementation "curse.maven:tickmender-1726415:9351267"

Learn more about Curse Maven

What's new

1.5.3 - 2026-10-28

Two new switches, both on by default: kibeRingDimensionState and kibeRingDoubleCount. TickMender now has 51 switches. The 49 of 1.5.2 are unchanged, with their defaults. Both defects were reported by players of the Nytheria pack about KIBE's Angel Ring and were found in the bytecode of KIBE 2.3.1 and of the Accessories compatibility layer. Both fixes were checked with stand-in classes in the game tests of this repository and on a real dedicated server with the real jars by a new probe (see the end of this section).

KIBE (kibeRingDimensionState): the Angel Ring no longer switches itself off when two wearers are in different dimensions

  • What players saw: with two players wearing Angel Rings (or Magma or Water Rings) in different dimensions, the rings flickered off and on, and a ring could stay off until its wearer switched it on again by hand. Alone, or with both wearers in the same dimension, nothing went wrong.
  • kibeRingDimensionState: after its wearer has changed dimension KIBE switches a ring off for one tick and on again, which gives the player the Pal ability (flight for the Angel Ring) back. To notice the change it keeps the world of the last tick and a "switch on next tick" flag in two instance fields of the ring item (lastworld, togglenexttick of AbilityRing), and an item is one object for every player of the server. With two wearers in different dimensions every tick of one finds "the world changed" (the other wrote its own world there), switches its ring off and sets the flag; the tick of the other consumes the flag and switches the wrong ring on. The fix keeps KIBE's logic and gives it a state of its own for every player and every ring item: at the head of both tick methods (AbilityRing.inventoryTick and TrinketAbilityRing.tick, which KIBE uses when Trinkets is there) the two fields are filled from the player's state, and at the return they are stored again and emptied. A single wearer gets exactly KIBE's own sequence (off for one tick after a change of dimension, then on again).
  • The world is stored as its registry key, never as the world object, so nothing keeps a server world alive after the server has stopped.
  • Edges: two stacks of the same ring item held by one player share one dimension state, as they do in KIBE. The state is kept per player UUID and ring item and is never cleaned: a few bytes for every player that has ticked a ring since the game started.
  • It applies to KIBE 2.3.1 only (the two tick methods were read in that jar). With another KIBE version the switch is idle (written for KIBE 2.3.1, installed is ...).

KIBE (kibeRingDoubleCount): an Angel Ring in an Accessories ring slot gives flight again

  • What players saw: an Angel Ring worn in a ring slot of Accessories gave no flight; the same ring in the inventory worked.
  • kibeRingDoubleCount: Accessories ticks every stack of its slots twice, once as an inventory item (inventoryTick, which is AbilityRing.inventoryTick) and once through its compatibility layer for Trinkets (Trinket.tick, which is TrinketAbilityRing.tick). Both KIBE methods put the ring with the current game time into the player's list of active rings. KIBE's player tick counts the enabled entries of that list and, above maxRingsPerPlayer (1 by default and in the pack), takes the ability away and marks the ring as "overflowed". One ring in the slot was therefore two entries (2 > 1). The List.add in both methods is now redirected: when the same stack was already added at the same game time, the second add is not made. Two different ring stacks are two objects and still count two, so KIBE's limit keeps its meaning.
  • Edge: a ring in an Accessories slot and the same item in the inventory are two stacks and still count two, which is KIBE's limit unchanged. The setting maxRingsPerPlayer is not touched.
  • It applies to KIBE 2.3.1 only (the two methods were read in that jar; the Accessories side was read in Accessories 1.1.0-beta.54 and accessories_compat_layer 0.1.13). With another KIBE version the switch is idle (written for KIBE 2.3.1, installed is ...).

Checked against the real mods

Both switches were checked in the game tests of this repository with stand-in classes that have the logic of the real KIBE methods (the two fields shared by all wearers, the list of active rings and its limit), once with the switches on and once with them off. They were then run on a real Fabric 1.21.1 dedicated server with the real jars (KIBE 2.3.1 with Player Ability Lib 1.10.0, Trinkets 3.10.0, Accessories 1.1.0-beta.54, the Accessories compatibility layer 0.1.13, owo-lib 0.12.15.4, Fabric API 0.116.17) by a new probe, testing/run-kiberings-probe.sh, once with both switches on and once with both off (the control run). Its players are real server player objects that are not connected, ticked once per server tick; the ring is KIBE's Angel Ring. With the switches on, all four checks passed: two wearers in the overworld and the nether with the ring in the inventory kept the ring on and kept flight for 40 ticks; one wearer sent from the overworld to the nether got KIBE's own sequence (ring off for one tick, then on, flying again); a ring in an Accessories ring slot gave flight, kept its kibe:unique mark and made one entry in KIBE's list of active rings; and two wearers with the ring in the slot in two dimensions showed no deviation for 40 ticks. The start line showed both switches active and each logged its first-use line. With both switches off, the control run showed the defects: the rings were switched off 51 times in 38 ticks (a flicker with a period of three ticks) and one player ended without flight, and a ring in the slot made two entries, was marked "overflowed" (no kibe:unique) and gave no flight at all; the single wearer's sequence was the same as with the switches on, since that case was never affected. The probe does not show a real client (flight on screen, the tooltip) or a real Nytheria server with all its mods. Build of 1.5.3: 745 tests (726 in test, 11 in testFixesOff, 8 in testFabricApi), all green.

Updating from 1.5.2

Replace the jar. The two new switches are added to an existing config/tickmender.json with their default (true); everything already in the file is kept. Whoever wants the old behaviour sets "kibeRingDimensionState": false or "kibeRingDoubleCount": false. Nothing else changes.

This mod has no related projects