Bertie
- Bertie2011
- bertie2011
- Europe/Stockholm
- Yes
- No
MC-85251
BDS-110
The following doesn't work and it worked before in 1.10:
/scoreboard teams add Test
/scoreboard players join Test @e/testfor @e[team=Test]
It's supposed to output all items, currently loaded in that team, but it doesn't work anymore.
When I add myself to the same team and ONLY change @e to @a, it works.
EDIT: After a bit more of testing, using @e only shows players on a scoreboard team.
I am using a /fill command on an one second clock to convert all emerald blocks (in a big area) into redstone blocks and back. However, the redstone dust and command blocks connected to the replaced emerald block won't update after setting it to redstone. It worked in previous snapshots.
Replacing the block by hand works.
Replacing the block using /setblock works.
Replacing the block using /fill works (all blocks in an area).
Replacing the block using /fill replace doesn't work (tested with both subid 0 and 1, both air and emerald blocks).As I said, the clock runs once a second so the redstone should have time to update.
I ran through all the latest versions of snapshots in every week, 17w17b was the last one that worked properly.EDIT: I also tried replacing the attached redstone wire, thinking it might be a bug with block conversion between versions. This didn't help.
Steps to reproduce:
/summon minecraft:falling_block ~ ~ ~ {BlockData:
{Name:"minecraft:diamond_block"},NoGravity:1b,Time:1}
/data modify entity @e[type=falling_block,limit=1,sort=nearest] BlockState.Name set value "minecraft:gold_block"
I'd expect the diamond_block entity to change into a gold_block, but it doesn't visually. The block id inside (using /data get) does show "minecraft:gold_block".
Steps to reproduce:
/summon minecraft:falling_block ~ ~ ~ {BlockData:{Name:"minecraft:diamond_block"},NoGravity:1b,Time:1} /data modify entity @e[type=falling_block,limit=1,sort=nearest] BlockState.Name set value "minecraft:gold_block"I'd expect the diamond_block entity to change into a gold_block, but it doesn't visually. The block id inside (using /data get) does show "minecraft:gold_block".
Steps to reproduce:
/summon minecraft:falling_block ~ ~ ~ {BlockData:{Name:"minecraft:diamond_block"},NoGravity:1b,Time:1} /data modify entity @e[type=falling_block,limit=1,sort=nearest] BlockState.Name set value "minecraft:gold_block"I'd expect the diamond_block entity to change into a gold_block, but it doesn't visually. The block id inside (using /data get) does show "minecraft:gold_block".
Steps to reproduce:
/summon minecraft:falling_block ~ ~ ~ {BlockState:{Name:"minecraft:diamond_block"},NoGravity:1b,Time:1} /data modify entity @e[type=falling_block,limit=1,sort=nearest] BlockState.Name set value "minecraft:gold_block"I'd expect the diamond_block entity to change into a gold_block, but it doesn't visually. The block id inside (using /data get) does show "minecraft:gold_block".
It doesn't say the bug also applies to latest snapshot there!
Voted!
Its really annoying that you fly up when you take damage...
This should really be fixed!!!
votes before closing this thread???
This really needs to change...
I made a claim system that obviously needs to work even after chunks are unloaded. Same goes for servers that use Armor Stands for flying text or other minigames and builds that use entities to mark moving locations (and use /execute to do things to these locations).
TrazLander's solution sounds good.
Sorry to caps, but THIS NEEDS TO CHANGE
oops, it's still a thing in the new snapshots though.
Also a bug with the bug system:
16w04a is clearly released and I could choose the version, but the bot says that I can't use that version number.
Did you mark this bug as a duplicate of it's own? Smart....
I have the same problem
Yeah I could go there. But I feel like it's a problem, instead of more like a suggestion. If I look at that link it shows me random ideas that could be implemented in mc, while this actually bothers me instead and is not really a suggestion.
If that makes any sense...
"Whenever a player has the glowing effect, the edges of said player's screen should glow the color he's glowing."
"squids defends them self shooting ink (particle effect). Ink gives you blindness for 5 seconds."
"After the rain dirt should look wet for sometime"
I don't feel like this "report" should belong between those stupid ideas...
@tryashtar
No, I don't mind. I didn't have much time to test things out, thanks for expanding my post =)
Confirmed for 1.12!
I hoped that the delay would mean a fix before the release.
EDIT:
Possible temporary fix for map makers: Use the destroy argument instead of the replace argument and make sure to do: /gamerule doTileDrops false. This prevents the block to appear as item after destruction.
The fact that teleporting a falling block doesn't visually move it either (and just makes blocks appear seemingly out of thin air at the destination) is probably related to this.
And damnit, of course I find an already existing issue after posting, while I couldn't find anything during the first search. MC-72849
The mentioned issue is closed as won't fix without reason, which quite a few players commented on for reconsideration or at least an explanation.
Still not fixed and also appearing in 1.15.2 (with updated BlockState tag and /data command).... No reason given for "Will not fix", which is really annoying.
Wow! Finally someone kind enough to point me to an answer for not being able to edit player NBT!
The weirdness around editing falling_block nbt probably has something to do with this.
For anyone finding this issue, as of 1.15.2 a neat workaround involves force loading a chunk far far away (outside anyone's render distance), summoning and modifying the falling_block there and then TPing it back into the right position.
Apparently applying the glowing effect sets the Glowing tag to true on entities, which obviously isn't desired. (Even on the player, which cannot be reset!)
Still an issue in 21w15a
Did you try using /data to set Glowing back to 0b? For players you could either /kill or open their files with NBTExplorer and set their Glowing to 0b as well.
It would seem weird to me if Mojang had to implement data conversion code between snapshots as well. (Bugs happen all the time) so I wouldn't count on them adding a fix for affected entities.
Confirmed for 21w16a (for both the general description and the mentioned cases in which the item does show up). Seems to be independent of OS or gamemode (bug also appears on Windows, Survival).
What the heck.... I just restarted Minecraft (no changes to resource packs or whatever) and indeed they were partially visible. It must have been multiple armor stands at the same position, from an earlier testing session. My bad, I guess this issue can be closed then.