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.6.0.jar

File nametickmender-1.6.0.jar
Uploader
NavrelisNavrelis
Uploaded
Nov 7, 2026
Downloads
39
Size
1.3 MB
Mod Loaders
Fabric
File ID
9501249
Type
R
Release
Supported game versions
  • 1.21.1

Curse Maven Snippet

Fabric

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

Learn more about Curse Maven

What's new

1.6.0 - 2026-11-07

Four new switches: adminTools (off by default), and debugifySwitcherDebugScreen, locateAnyNamespace and petSharing (on by default). TickMender now has 57 switches. The 53 of 1.5.5 are unchanged, with their defaults.

adminTools adds two commands, /admin and /adminrtp, with the tools of the people who run a server. locateAnyNamespace and petSharing are not repairs either: they are wishes of the Nytheria pack's owner that change the game a little (/locate takes part of a name, the members of a party share their tamed pets), so they are on by default and can be switched off. debugifySwitcherDebugScreen is a repair for the client.

Admin tools (adminTools): the /admin and /adminrtp commands

It is a feature that the owner of the Nytheria pack asked for, so it is off by default: a pack that does not switch it on plays and runs as it did with 1.5.5. The Nytheria pack turns it on in config/tickmender.json. With the switch off, no command is added, none of the mixins of the feature is applied and no file is written.

  • What it is: one root command, /admin <subcommand>, for the operators of a server (vanilla operator level, nothing else), and a chest-style menu that opens when a player types /admin alone. The server builds the menu; no client part is needed, and it works with a vanilla client. It needs no other mod (FTB Essentials, for example) and adds no packets and no registries.
  • Permissions: permissionLevel (default 3) for /admin and /adminrtp, ownerPermissionLevel (default 4) for sudo, ipban, webhook and the IP addresses of players. The console always counts as owner.
  • Vanish: vanish [player], vanish list, vanish silentjoin, vanish fakejoin, vanish fakequit, spectate, follow. A vanished player is hidden from everybody who is not staff in the world, the tab list, the server list, join, leave and death messages, /list, selectors, tab completion, public chat (an option), mob targeting, sculk, pressure plates, item pickup (an option), chests, sleeping and the sounds they make. It reaches into the mods that keep their own list of players, each only when installed: Xaero's Minimap and World Map, Open Parties and Claims, FTB Teams, Simple Voice Chat, Waystones and WATUT. The state is saved with the player and survives a restart.
  • Inventory: invsee (online and offline, with armor, offhand and Accessories slots), endersee, backpacksee, invsnapshot, invclear, invcopy, deathinv, revive, itemsearch. Every action that replaces or removes items takes a snapshot first and gives up when that fails.
  • Staff mode: staffmode puts the items, experience, game mode, place, health and effects aside and gives an empty, vanished, invulnerable body that can fly; doing it again gives everything back exactly. It ends by itself at logout and at a server stop, before the player's file is saved, and after a crash the items are given back at the next join. It switches vanish directly, so the log no longer gets a false warning that vanish is "still off" or "still on" when staff mode is used.
  • Revive without duplicated items: revive gives back the items and experience of the last death, and now also removes that death's drops from the world, so the items do not exist twice. The items and experience orbs a death drops carry the command tag tickmender.death.<uuid>.<time> and never merge with other items or orbs; a revive removes the loaded ones, and the ones in unloaded chunks are refused when the chunk loads (for 30 days after the revive). Nothing is removed or given before the revive is written to death-drops.json, and if giving fails the items stay in the death snapshot. The question before a revive says how many drops lie on the ground, who picked some up (not taken back), and what is gone (hoppers and mobs are not recorded, so what they took counts as gone), and warns about graves (You're in Grave Danger). death-drops.json in <world>/tickmender-admin/ is new for this (revived deaths for 30 days; pickups for 30 days, at most 500 deaths and 10 players each, the rest as "others"). The Revive button in the menu runs /admin revive, so its question is the only one.
  • Moderation: ban, tempban, ipban, unban, banlist (in the game's own ban lists, so /pardon and other tools see them), kick, mute, tempmute, unmute, warn, warnings, unwarn (with automatic actions at a number of warnings), freeze, unfreeze, setjail, deljail, jails, jail, unjail, history, note, notes, delnote, alts, socialspy, commandspy, chat clear|lock|slow, sc (staff chat) and maintenance.
  • Players, items and server: whois, seen, playtime, ping, near; heal, feed, extinguish, fly, god, speed, gm, tp, tphere, tpall, tppos, back, unstuck, smite, kill, xp, effects clear, attributes reset, nick, realname, sudo; item, repair all, more, hat, powertool; lag, tps, entities, killall, butcher, clearlag, chunks, restart, broadcast, title, actionbar, whitelist, time, weather, uptime, mem; and help, reload and audit.
  • One question, not two: clearlag now and killall ask once above 100 entities, and the menu's "Clear lag now" asks in the menu and then runs clearlag now confirm, which does not ask again; the menu's "Kill all" is a chat prompt that lets the command ask. In the same way the menu's clear inventory, snapshot restore, invcopy and butcher never ask twice.
  • Discord webhook: webhook status|set|clear|enable|disable|toggle|test, in game or in the settings file. Four categories (moderation, staff, server, audit). The address is a secret: it is shown masked everywhere and left out of the audit log. Posts go through one thread of their own with a bounded queue and never block the server tick.
  • Files: settings in config/tickmender-admin.json (created with defaults while the switch is on; the one settings file the mod rewrites, when the webhook is changed in game), data in <world>/tickmender-admin/ (player records, server.json, audit.log, inventory snapshots, the items put aside by staff mode, death-drops.json). Bans use banned-players.json and banned-ips.json.
  • Known limits: a vanilla selector with a limit and no sort, such as @a[limit=1], picks its players before the vanished ones are taken out for a player who is not staff, so it may find nobody; the sounds a vanished player causes are dropped for everybody, staff included; FTB Teams has one view for a whole team, so a vanished player is offline there for their staff teammates too; a revive does not take back what another player picked up from the death's drops. There is no player-side /report, no block logging or rollback, and sudo runs commands only.
  • The full list of commands, the menu, the settings and the limits are in the README section adminTools.

Random teleport (/adminrtp [targets])

  • A command outside /admin, at the same staff level (permissionLevel). Alone it teleports you; with players named or a selector it teleports them (from the console too). The target goes to a random safe place in the dimension they are in, on a ring around the world origin at the distances of FTB Essentials' /rtp (min_distance and max_distance read from config/ftbessentials.snbt when it exists, else 500 and 25 000). No cooldown, no warm-up, and nothing of FTB Essentials is used or changed.
  • A place needs a solid floor (not leaves or bedrock), two free blocks above it, nothing that hurts and a spot inside the world border; in the Nether the search starts 8 blocks under the roof. Up to 32 columns are tried; chunks are requested without making the server thread wait. The place left becomes the back position, and the move is audited and posted to the webhook's staff category. The player page of the menu has a "Random teleport" button.

F3 and the game mode switcher (debugifySwitcherDebugScreen)

  • What players saw: with Debugify installed, closing the game mode switcher (F3+F4) with a click on a mode or with Escape before letting go of F3 showed the debug screen; with BetterF3 the whole BetterF3 screen slid in.
  • Why: Debugify's fix for MC-183776 makes Keyboard.processF3 answer "not handled" after it opened the switcher, so the flag "F3 was used in a combination" is never set. The release of F3 is ignored while the switcher is open, but not after it was closed first.
  • debugifySwitcherDebugScreen: sets the flag again where the switcher opens, and clears it when F3 is released while the switcher is open, so the next press of F3 still works. Client only, applied to Debugify 1.21.1+1.1 only.
  • Checked with unit tests of the rule and with the mixin applied to the game's real Keyboard; not run in a real client before the release.

/locate without a namespace (locateAnyNamespace)

  • What players saw: /locate biome deser offered nothing, because the suggestions only look at one namespace at a time, and an id needed its namespace.
  • locateAnyNamespace: the suggestions of /locate structure, /locate biome and /locate poi look in the path of every namespace, by its start and by the start of any word of it (deser offers minecraft:desert, terralith:desert_oasis and terralith:desert_spires), best match first and minecraft before the others; # tags work the same way. An id without a namespace is accepted (minecraft:<name> if there is one, else the one id with that path; if several namespaces have it, the command fails and lists them). The chat line does not turn red while a name is being typed.
  • Both sides: the server resolves the ids and gives the suggestions to every client, also one without TickMender. A TickMender client on a server without it gets the suggestions for biomes and points of interest and the colour, but not the structure suggestions. On by default; not run in a game before the release.

Pet sharing (petSharing)

  • The members of the same FTB Teams party or Open Parties and Claims party as a pet's owner can sit and stand the pet, dye its collar, put on and repair wolf armor and heal a cat, as the owner can. A pet never targets or turns angry at its owner's teammates or their pets, also when two teammates hit each other (and with the game rule universalAnger on). Ownership, following and teleporting stay with the owner; the personal team of FTB Teams is not a party. Neither team mod is needed (both are read by reflection). On by default; checked with stand-ins of the two mods, not with the real jars or in a game.

Updating from 1.5.5

Replace the jar. The new switches are added to an existing config/tickmender.json with their defaults (adminTools false, the other three true); everything already in the file is kept. Whoever wants the admin tools sets "adminTools": true and restarts; the first start writes config/tickmender-admin.json. Whoever wants /locate or the pets as in the game sets "locateAnyNamespace": false or "petSharing": false. Nothing else changes.

Build of 1.6.0: 1945 tests (1921 in test, 16 in testFixesOff, 8 in testFabricApi), all green; real-server admin probe 95 PASS / 0 FAIL.

This mod has no additional files