Summary
Within exactly 1 game tick after switching held weapons, melee attacks combine conflicting weapon properties incorrectly:
Inherits base attack damage and full attack charge progress from the weapon you swapped away from
Applies all enchantments, special weapon mechanics (axe shield-break, mace breach, sword sweep, etc.) of the newly selected weapon
This creates an unfair PvP exploit by mixing high raw damage with powerful enchant/trait effects in one hit.
Steps to Reproduce
Create a new vanilla survival world, no mods, no resource packs.
Obtain two distinct melee weapons for testing:
Example A: Netherite Axe (high base damage, shield-breaking trait) in hotbar slot 1
Example B: Wooden Sword enchanted Fire Aspect III in hotbar slot 2
Target a mob/player for testing (summon husk ~ ~ ~ {NoAI:1} for stable health reading)
Hold slot 1 axe, hold right mouse to fully fill attack charge meter.
On the exact same tick you release right-click to swing, instantly hotkey switch to slot 2 sword within 1 tick window.
Observe the hit result.
Repeat reverse test: charge sword first, swap to mace in 1 tick to verify mace breach works with sword base damage.
Actual Result
The attack deals the original axeβs high base damage, carries over the full charge multiplier, and triggers the new swordβs Fire Aspect burn effect simultaneously. All special traits of the second weapon activate (shield break, armor piercing breach, sweep attack, etc.).
Expected Result
All damage calculation, charge progress, enchantments and weapon special traits must read only the currently held weapon at the moment the swing lands. No cross-weapon stat mixing should occur in any tick window.
Additional Notes
This exploit is widely known in PvP communities as attribute swap / breach swap. It severely unbalances combat by letting players stack the highest raw damage weapon with the most impactful enchant/trait weapon in a single hit. The bug window is limited strictly to 1 tick after item switch. Video/screenshot recording of reproduction can be attached as proof.
Thank you for your report!
We're tracking this issue in MC-28289, so this ticket is being resolved and linked as a Duplicate.
If you would like to add a vote and any extra information to the main ticket, it would be appreciated.
If you haven't already, please make use of the search feature to see if an issue you are about to report has already been reported.
Quick Links:
π Bug Tracker Guidelines β π¬ Community Support β π§ Mojang Support (Technical Issues) β π§ Microsoft Support (Account Issues)
π Project Summary β βοΈ Feedback and Suggestions β π Game Wiki