Idkman
Assigned
Reported
Comments
Hey! I read through your report and it sounds super frustrating—losing all your hard-earned items and getting teleported back to the start because of a crash is the worst.
It sounds like your Realm is experiencing a 'rollback.' This usually happens when the server crashes so fast that it doesn't have time to save your location or your inventory, so it just resets everything to the last time it was 'safe' (which for you seems to be the very beginning).
Since you mentioned that your 'Claims Adjuster' (from your add-ons) is missing after it happens, there's a really high chance that one of your add-ons is actually causing the crash. Mojang usually can't fix bugs caused by third-party add-ons, so you should definitely try playing without them for a bit to see if the crashes stop.
Also, just a heads-up: you posted this in the Minecraft Launcher section, but since it's happening inside the game on a Realm, it should actually be reported in the Minecraft Realms section if you want the right developers to see it.
Hope you can get it sorted so you don't have to keep walking back!
That’s a great catch! If it’s happening on your end with a regular sword too, it confirms the bug is definitely there at all levels.
In my test on 1.21.11, the 'leak' at 8 damage must have been so tiny that the game rounded it down to 0, which is why I didn't see it at first. I used the 120 damage sword specifically to magnify the error and see if I could force it to show up—and it did.
Since you're seeing it even with a standard sword, it proves the Critical Hit math is definitely bypassing the enchantment's safety check. This is really helpful info for the devs because it shows the problem happens no matter how much damage the sword does. Thanks for checking that!
안녕하세요! 메시지를 번역해서 읽어보았습니다. 군입대를 앞두고 친구들과 게임을 하지 못하게 되어 정말 안타까운 마음입니다.
도움이 될 만한 내용을 정리해 드립니다:
계정 및 라이선스 문제 가능성: 구매 후 정확히 한 달 뒤부터 문제가 생겼다면, 이는 마이크로소프트 계정 로그인이나 윈도우 스토어 라이선스 인증 문제일 확률이 높습니다.
고객 지원 문의: 이곳 버그 트래커는 게임 코드를 수정하는 개발자들이 있는 곳이라 개인의 계정 정보를 확인할 권한이 없습니다. Microsoft 지원이나 Minecraft 고객센터에 직접 문의하셔서 계정 오류를 해결하셔야 합니다.
친구분들과 입대 전에 꼭 즐거운 추억 만드시길 응원합니다!
Thank you for the follow-up. To clarify the confusion regarding the modified attack_damage:
In my environment (Vanilla 1.21.11), I was unable to reproduce the damage bypass using the standard Netherite Sword values (~8 damage). In my tests, standard values resulted in 0 damage as expected.
To investigate further, I performed stress-testing by manually increasing the base attribute to 120. This was done to determine if the issue is a calculation/precision error. I found that the 'leak' only occurs when the base damage is high, which suggests that the critical hit multiplier ($1.5 \times$) is being applied at a stage in the pipeline where the 'set to 0' logic is being bypassed by floating-point remainders.
While we are seeing different results at base damage levels, the fact that a bypass is possible at higher values confirms a flaw in the logic. I am reporting these findings to help the developers identify exactly where the damage calculation 'leaks' during a critical hit.
Thank you for helping investigate this bug
To answer your questions:
Test with default damage: Yes, when I run the exact /give @s netherite_sword[minecraft:enchantments={"bugreport:no_damage":1}] (no extras), both normal and crit hits deal 0 damage to the zombie. No bypass!
How attack_damage reached 120: I manually added an attribute modifier after giving the sword, using something like /item modify entity @s weapon.mainhand add attribute_modifiers {attribute:"minecraft:attack_damage",operation:"add_value",value:112,uuid:[I;0,0,0,1]} (to bump the default ~8 up to 120 for testing high-damage scenarios). That's why the NBT shows 120—it's not part of the datapack or base /give.
Crit method: Standard jump-fall attack (jump, then swing while descending). Full attack cooldown, confirmed by the green sparkles/particles on hit.
Exact versions:
Stable: Java Edition 1.21.11 (title screen: "Minecraft 1.21.11", /version output: "Minecraft 1.21.11")
Snapshot: Java Edition 26.1 Snapshot 4 (title screen: "Minecraft Snapshot 26.1-snapshot-4", /version: "Minecraft Snapshot 26.1-snapshot-4")
Normal hit test: Yes, 100% 0 damage on non-crit swings, even with the 120 attribute.
So, the bypass only happens on crits when the base attack_damage is very high (like 120). With default (~8), it's fully nullified. Maybe a floating-point precision issue or overflow in the damage pipeline when crit multiplier hits large numbers before/after the "set 0" effect? The smaller leak in the snapshot (~0.375 vs ~2.25) suggests some calc changes there.
Appreciate the escalation—hope this helps pin it down!
I think when you place armor with trims in a slot it “infects” the slot making the armor trim appear every time
Happens on ios as well, I think when you place armor with trims in a slot it “infects” the slot making the armor trim appear every time
Hey! It sounds like your Launcher is stuck in what’s called an 'Update Loop.' > Basically, the Launcher knows it needs an update, but something is blocking the download halfway through. When it fails, it leaves behind 'half-finished' files, which is why you're getting that 'file is corrupted' error. Even though your internet is working fine, the Launcher gives you that 'No Internet' error because it can’t reach the specific Microsoft update servers it needs.
The reason your reinstalls didn't work is probably because those corrupted files are hiding in your AppData folders, which don't always get deleted when you uninstall.
To safely check for and fix corrupted system files, you can open your Command Prompt (cmd) as an Administrator and type:
sfc /scannowThis is a safe way to let Windows repair itself without risking any of your personal data.Also, just a quick heads-up: Since the game won't even open yet, this is actually a Minecraft Launcher problem, but you reported it in the Minecraft Java section. You should move this over to the Launcher section so it’s in the right place! Hope this helps you get back into the game!"