Rob DeWolf
Assigned
Reported
Comments
Still an issue in 1.18.2.
Confirmed for 1.17.1.
In my case, it affects fireballs. Reflecting Ghast fireballs back at the Ghast (using commands), after modifying the Owner NBT, doesn't trigger Return To Sender, as I'd expect it to.
@Scuti
Fine to vent your frustrations, but Mojang HAS been listening to us. And until you're a developer (or are friends with a few), I'd really hold back on opening your mouth about how an update should be free of bugs.
When you have a game as complex as Minecraft, when you add things, sometimes other things break. Sometimes when you try and fix old bugs, you create new ones. Sometimes bugs happen to one person, but are not reproducible by the devs on their system. You can't fix a bug you can't see in action. And sometimes, there isn't enough time in the day to test and retest every single tiny interaction in the game - you rely on community consensus if the bug is large enough. There is a reason for the saying "54 bugs in the code, take one down, pass it around, 1458 bugs in the code..."
If you really want to complain, name one game in the past 10 years that has been an ABSOLUTELY perfect release. You can't. Because every game gets patched. Every game has bugs. No Man's Sky, Overwatch, Watchdogs, CyberPunk, Valorant, Minecraft, Skyrim (largely unpatched - left to the community to fix), even Pokemon and single player games have bugs and glitches.
Don't be an entitled brat. Mojang could easily amend their policies, and have you pay for every new content update.
This happens when you have a single player world as survival, but open to LAN and activate creative through /gamemode creative.
Save your game, re-enter. Even though you're still in creative mode, the game doesn't recognize you are. Will copy the NBT data, but won't place it. Just reopen to LAN, and it will work again.
I'd consider this a bug, but mainly posting in case anyone runs into this, and finds this comment.
Optifine is still in pre-release (thus the PRE) in the name - they have a Discord and spot where you can report bugs.
@tryashtar This issue is different.
It IS tagging all entities. Not just thinking it did and returning all entities. If I specify a limit, it doesn't seem to be following it - specifically in /tag.
If I use /scoreboard the bug doesn't replicate. It will affect one entity. The issue is that even though I specify a limited area, it still tags all entities spanning the entire server.
/execute at @e[type=area_effect_cloud,distance=..5,tag=Point] run tag @e[limit=1] add Mob
That will tag all entities, even ones that are 32,000 blocks away. This shouldn't be happening. The bug you referenced may be related, but it's not the same bug. Mine is reporting all entities have been added, and they have been. Even when they shouldn't be.
But if I tag a zombie using:
/tag @e[type=zombie,limit=1,sort=nearest] add Tagged
Then do:
/tag @e remove Tagged
It says "Removed from 1 entity".
—
I'm going off this from memory, I'm unable to test that right now. But previously removing a tag from all entities would only show the number of entities that tag was actually removed from.
Can confirm: if you execute the function/command as the armor stand itself, then it works. I use the system for a sethome/home system.
It broke during the 1.14 snapshots. But updating the data pack so that the armor stand executes the teleport, works. Someone told me to use that since when something is the target (as @s), it doesn't get unloaded from memory.
System now works again.
Is there are argument server owners can run to optimize the world? I know the forceupgrade and erasecache. Just wondering about the optimize.
Side note: The PRE-RELEASE states it has been fixed. If you are playing on Realms, you have NOT received the fix yet. Realms only runs full versions, not pre-releases. Don't report it as "still not working" if you're on Realms.
I have a full prod server on 1.14 right now, so I won't be able to test reliably myself. I hope it gets fixed soon, if it isn't already. 🙂
I did the force upgrade, and the only issues I have noticed is lighting at bedrock level near lava in the overworld is broken. It reports as 15 light level, even when the lava is behind a wall of blocks.
This is still a bug in 1.14. Can you please fix this? Super annoying as an admin to see all of the command feedback.
I have had some players have this problem to a greater extent than others. They set MC to be 64-bit, and removed all the JVM arguments other than setting available memory, and that seems to alleviate the issue.
Bug still exists - version 1.14, vanilla.
When will this not be "Postponed", and actually fixed? It's been in the game since the beginning.
This is a "Works as Intended".
Pigmen have an anger NBT data tag. You need to wait for them to despawn (don't go into the nether portal right away), or for their anger to go away. You can do this by building up a couple of blocks so they can't hit you.
Unless you can provide further info on why it's a bug...your description is just a regular feature of MC.
This will be a "Works as Intended".
Has been this way in Java Edition forever. @e selects ALL entities. Here are two ways around it:
Don't target players:
/kill @e[type=!player]
Or, don't target creative players:
/kill @e[m=!1]
Any way of doing that on a server? Issue is still there - while I'm sure a cached data will reset it, I also don't want to delete the entire region file to fix it, if possible.
Fabian, FPS on a client does not affect servers - unless they are both being run on the same machine.
I have this issue on my dedicated i7-7700k server (boost to 5GHz). No one on, and CPU idling at 90-100%, with nothing running except spawn chunks.
Will see if it's resolved later on today. 🙂
Tried what Michal had done, filling a single layer at 254 with stone. Then immediately with air after. This seems to update the sky light, and remove the dark patches on ground left over from /fill command.
Can confirm - running 1.13 - setting sendCommandFeedback to true returns the expected functionality.
However, as an admin, I'd like to have feedback hidden, but give players the ability to see sent messages again. 😛
Still an issue in 1.19 pre-release 3.