Перейти к содержимому
Mineforgian

Trident Killers 4 Java

Bedrock-style trident killers for Java Edition — no carpets, no gimmicks. Throw a trident, aim a piston at it, farm. Server-side only.

Загрузки
1K
Подписчики
4
Обновлён
5 августа 2026 г.
Лицензия
All-Rights-Reserved

Опубликован 3 июня 2026 г.

Исходный кодСообщить об ошибке

Trident Killers 4 Java

Bedrock-style trident killers for Minecraft: Java Edition. Server-side, no dependencies.

Throw a trident, push a piston into it to lock it, and the locked trident kills mobs in its hitbox with full player credit - the core of XP and drop farms. Kill credit, Looting, and player-only drops all work, even while you are offline (loot keeps flowing; XP is suppressed). It damages mobs only, so players are safe in the kill zone, and a trident you never piston-move stays fully vanilla. No carpet or datapack tricks - it works at the game level.

Ships as a Fabric, Forge, and NeoForge mod (and runs on Quilt), with no Fabric API dependency.

Using it

Install it on the server - it does nothing client-side, and vanilla clients can join. Build a normal trident killer (throw a trident, push a piston into it) and mobs that enter the locked trident die with full player credit. Adds no blocks, items, or commands.

Links

By Kishku7. All Rights Reserved.

Ченджлог

1.2.14+26.3-snapshot-7Бета26.3-snapshot-7 · 5 августа 2026 г.

Changed

  • Fabric 26.3 cell moved to MC 26.3-snapshot-7 (from snapshot-6): fabric-api 0.156.1+26.3 -> 0.156.2+26.3, resource pack_format 94 -> 95, exclusive window [26.3-alpha.6, 26.3-alpha.7) -> [26.3-alpha.7, 26.3-alpha.8). Every 26.3 snapshot bumps pack_format by one, so each jar stays snapshot-exclusive. No other cell changed.

Notes

  • No source change required. snapshot-7's breaking surfaces were checked against this mod and none are touched: the trailing Prediction argument on LivingEntity.drop(ItemStack, boolean) / Inventory.placeItemBackInInventory, the client-side LocalPlayer.drop(boolean) return type going boolean -> void, the InteractionResult.SwingSource CLIENT/SERVER -> PREDICTED/SERVER_ONLY rename together with the deletion of ServerboundSwingPacket, and the 32 new concrete slab/stair blocks plus the filled-map colour component removals.
1.2.13+26.3-snapshot-6Бета26.3-snapshot-6 · 1 августа 2026 г.

Changed

  • Every jar is now 1.2.13, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix.

Fixed

  • Claim ranges now match the loader gates. Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series.
  • pack.mcmeta on MC 1.21.9-1.21.11. The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack.
  • AbstractArrow constructor era boundary in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2.
  • Forge and NeoForge jars reported their version as 0.0NONE. Those manifests ask the loader to read the version from the jar (${file.jarVersion}), but the jar never carried an Implementation-Version attribute, so the mod list and every log line showed 0.0NONE. All 24 loader jars now carry the real version.

Added

  • Ten new build targets: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.
1.2.13+26.2-neoforgeРелиз26.2 · 1 августа 2026 г.

Changed

  • Every jar is now 1.2.13, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix.

Fixed

  • Claim ranges now match the loader gates. Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series.
  • pack.mcmeta on MC 1.21.9-1.21.11. The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack.
  • AbstractArrow constructor era boundary in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2.
  • Forge and NeoForge jars reported their version as 0.0NONE. Those manifests ask the loader to read the version from the jar (${file.jarVersion}), but the jar never carried an Implementation-Version attribute, so the mod list and every log line showed 0.0NONE. All 24 loader jars now carry the real version.

Added

  • Ten new build targets: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.
1.2.13+26.2Релиз26.2 · 1 августа 2026 г.

Changed

  • Every jar is now 1.2.13, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix.

Fixed

  • Claim ranges now match the loader gates. Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series.
  • pack.mcmeta on MC 1.21.9-1.21.11. The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack.
  • AbstractArrow constructor era boundary in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2.
  • Forge and NeoForge jars reported their version as 0.0NONE. Those manifests ask the loader to read the version from the jar (${file.jarVersion}), but the jar never carried an Implementation-Version attribute, so the mod list and every log line showed 0.0NONE. All 24 loader jars now carry the real version.

Added

  • Ten new build targets: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.
1.2.13+26.1.2-neoforgeРелиз26.1, 26.1.1, 26.1.2 · 1 августа 2026 г.

Changed

  • Every jar is now 1.2.13, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix.

Fixed

  • Claim ranges now match the loader gates. Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series.
  • pack.mcmeta on MC 1.21.9-1.21.11. The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack.
  • AbstractArrow constructor era boundary in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2.
  • Forge and NeoForge jars reported their version as 0.0NONE. Those manifests ask the loader to read the version from the jar (${file.jarVersion}), but the jar never carried an Implementation-Version attribute, so the mod list and every log line showed 0.0NONE. All 24 loader jars now carry the real version.

Added

  • Ten new build targets: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.
1.2.13+26.1.2Релиз26.1, 26.1.1, 26.1.2 · 1 августа 2026 г.

Changed

  • Every jar is now 1.2.13, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix.

Fixed

  • Claim ranges now match the loader gates. Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series.
  • pack.mcmeta on MC 1.21.9-1.21.11. The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack.
  • AbstractArrow constructor era boundary in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2.
  • Forge and NeoForge jars reported their version as 0.0NONE. Those manifests ask the loader to read the version from the jar (${file.jarVersion}), but the jar never carried an Implementation-Version attribute, so the mod list and every log line showed 0.0NONE. All 24 loader jars now carry the real version.

Added

  • Ten new build targets: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.
1.2.13+1.21.9-neoforgeРелиз1.21.9 · 1 августа 2026 г.

Changed

  • Every jar is now 1.2.13, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix.

Fixed

  • Claim ranges now match the loader gates. Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series.
  • pack.mcmeta on MC 1.21.9-1.21.11. The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack.
  • AbstractArrow constructor era boundary in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2.
  • Forge and NeoForge jars reported their version as 0.0NONE. Those manifests ask the loader to read the version from the jar (${file.jarVersion}), but the jar never carried an Implementation-Version attribute, so the mod list and every log line showed 0.0NONE. All 24 loader jars now carry the real version.

Added

  • Ten new build targets: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.
1.2.13+1.21.8Релиз1.21.6, 1.21.7, 1.21.8 · 1 августа 2026 г.

Changed

  • Every jar is now 1.2.13, replacing the mixed 1.2.9 / 1.2.11 / 1.2.12 state across the matrix.

Fixed

  • Claim ranges now match the loader gates. Every pre-26 Forge and NeoForge jar declared an MC range whose oldest versions its own loader floor refused, so those versions could never load. Each range now starts at the first version the jar's loader actually admits, and the open-ended NeoForge dependency ranges are closed to the cell's own series.
  • pack.mcmeta on MC 1.21.9-1.21.11. The Fabric and NeoForge jars for that span no longer ship a pack.mcmeta at all (both loaders generate correct metadata themselves); the Forge jars declare the exact data-pack format (1.21.10 -> 88, 1.21.11 -> 94). Removes the "couldn't load pack metadata" warning and the dropped resource pack.
  • AbstractArrow constructor era boundary in the code generator was off by one version: the ItemStack parameter arrives at MC 1.20.3, not 1.20.2.
  • Forge and NeoForge jars reported their version as 0.0NONE. Those manifests ask the loader to read the version from the jar (${file.jarVersion}), but the jar never carried an Implementation-Version attribute, so the mod list and every log line showed 0.0NONE. All 24 loader jars now carry the real version.

Added

  • Ten new build targets: Forge 1.20.2 and 1.20.4; NeoForge 1.21, 1.21.2, 1.21.3, 1.21.4, 1.21.6, 1.21.7, 1.21.9 and 1.21.10. Every one boots on a dedicated server.

Комментарии

Загружаем…