Skip to content

Port to Minecraft 26.1.2 (Fabric)#4

Open
vanlueckn wants to merge 19 commits into
MrTroble:26.1.2-fabricfrom
vanlueckn:26.1.2-fabric
Open

Port to Minecraft 26.1.2 (Fabric)#4
vanlueckn wants to merge 19 commits into
MrTroble:26.1.2-fabricfrom
vanlueckn:26.1.2-fabric

Conversation

@vanlueckn

@vanlueckn vanlueckn commented May 12, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Migrate Fabric port from Yarn to Mojmap for 26.1.2
  • Complete 26.1.2 Fabric migration (incl. ServerPlayer cast for hurtAndBreak)
  • Carries forward earlier 1.20.6 / 1.21 / 1.21.8 Fabric ports
  • Includes merge commit syncing LICENSE and the eu.gircom.troblecodings package rename from upstream (rename already present in this branch — kept current contents)

Nico Froehlich and others added 18 commits October 6, 2022 18:57
Switch all imports and method names from Yarn (World, PlayerEntity,
NbtHelper, ItemUsageContext, ActionResult, Text, MutableText,
TranslatableTextContent, useOnBlock, appendTooltip, etc.) to Mojang
mappings, since Yarn ends with Minecraft 1.21.11. Replace damage(int,
LivingEntity, EquipmentSlot) with the vanilla hurtAndBreak(int,
ServerLevel, LivingEntity, Consumer<Item>) signature; the ServerLevel
cast is guarded by an earlier isClientSide return. Fix the prior
ItemGroups field type to CreativeModeTab.
The branch was half-migrated and could not compile. Restore the
Item.Properties-accepting Linkingtool / MultiLinkingTool
constructors so callers can attach a ResourceKey before
construction (mandatory in 26.1.2), swap the removed
NbtUtils.writeBlockPos / readBlockPos for IntArrayTag helpers,
switch Player.displayClientMessage (gone in 26.1.2) back to
sendSystemMessage, and call Level.isClientSide() as the field is
private. Mirrors the 26.1.2-neoforge fix; the Fabric build path
now uses Mojang mappings, so the same source compiles for both
loaders.
ItemStack#hurtAndBreak in 26.1.2 takes ServerPlayer, not Player.
The server-side branch is already gated on !isClientSide(), so the
cast is safe.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants