Former user

The point here is that I followed exactly what Minecraft said to do, but they refuse to accept their own instructions. On top of that, they’ve known about this for 3 years and nothing has changed. That’s why I submitted this as a bug again, and I hope they finally fix it instead of just closing the report as 'resolved' or 'duplicate'.

I tried at the time (lots of times). They ask for a lot of information about the account to verify ownership, and if you can’t provide 100% of the answers, they instantly close the ticket. If you try to say something like: ‘I already deleted the account the way the Minecraft page instructed. I don’t need to verify ownership because the account is already deleted. Can’t you just check that the Microsoft account is gone and delete my Minecraft account as well?’ they’ll just reply: ‘Unfortunately, we could not verify account ownership. Please submit a new ticket.’

Is there any information on whether Minecraft will ever sync with Microsoft account/Xbox profile events? It's already been 3 years...

I know there is a report about this in WEB-5669, however, three years later, deleting a Microsoft account still does not delete the Minecraft account. I am stuck trying to delete my Minecraft account because support cannot verify me, and I have already tried hundreds of times. Can a staffer help me?

Did you manage to delete your Minecraft account?
I have created a new WEB post about this because I cannot verify the questions Minecraft Support asks me in order to delete my account, since the Microsoft account was already deleted. Can a staffer help me?

I saw a mod say this needs to be reported to Minecraft Support. When you submit the ticket, make sure to select Technical Support as the category.

I'm not the only one who mistakenly deleted a Microsoft account; I also have other accounts. The Minecraft GDPR process was misleading.

Observed Results: It summons a firework rocket and teleports it to -100 by Y axis and then the explosion happens.

Expected Results: As in 1.20.4, there should be an explosion first and then teleport a rocket to -100 by Y axis because of LifeTime NBT is set to 0.

Sorry for the previous incomplete message and formatting.

1. Use the attached datapack.
   Steps to Reproduce:
   1. Add the attached datapack into your world’s datapack folder.
   2. Reload datapacks with command “/reload“.
   3. Run a command:

2. /function firework:function1

3. The function will summon a firework that is supposed to explode right after summoning and teleport rocket to -100 by Y axis.
   
   Observed results:

Updated datapack

Does your function1.mcfunction file look like this?

summon firework_rocket ~ ~ ~ {LifeTime:0,FireworksItem:{id:"minecraft:firework_rocket",count:1,components:{"minecraft:fireworks":{explosions:[{shape:"large_ball",has_twinkle:true,has_trail:true,colors:[I;16711680]}]}}}}
tp @e[type=firework_rocket] ~ -100 ~

Try to call this function on both versions: 1.20.4 and the current one and compare the results, correcting the syntax. Also, when you do this “trick“ in 1.20.4, the firework rocket doesn’t deal any damage for players because the rocket itself - the source of explosion, gets teleported immediately but the explosion effect was still there. That was pretty useful in mapmaking. You can also check this by setting your gamemode to survival/adventure and call the function.

In my first message I used “schedule“ command to check, how many ticks it takes for explosion and turned out that it wasn’t 0 or 1, but 2. Thank you for your responds!

function1.mcfunction file that is called in the video:

Version 1.20.4:

Version 1.21.5-rc1 (also previous snapshots):

Delete my account

Thank you

Sure, here’s an easy way to reproduce the issue: you can download this datapack or create a datapack that only has two functions in it, for example, function1.mcfunction & function2.mcfunction.
[mediaInline]

function1.mcfunction

summon firework_rocket ~ ~ ~ {LifeTime:0,FireworksItem:{id:"minecraft:firework_rocket",count:1,components:{"minecraft:fireworks":{explosions:[{shape:"large_ball",has_twinkle:true,has_trail:true,colors:[I;16711680]}]}}}}
# You can change the delay to 1t to compare results
schedule function firework:function2 2t

function2.mcfunction

tp @e[type=firework_rocket] ~ -100 ~

Then, call a function “function1.mcfunction“ from chat or a command block and compare results with 1 tick and 2 ticks delay. You can notice that it takes 1 additional tick before explosion that wasn't noticed in 1.20.4.

At the same time some blocks, items and particles render over the background of nametags/renamed items in item frames/scoreboard... but not over the text (I don't know if this is a bug) 

It's really easy to see if you change Text Background to Everywhere and change Text Background Opacity to 100%.

So far the blocks it happen to render over background that I know of are:

• Heads and all variants

• Glass and glass panes and all variants

• Signs and all variants

• Hanging signs and all variants

• Beds 

• Banners

• Item frames

• Bell (only the Bell)

• Decorated pots and all variants

• Minecarts and all variants

• Conduit

• Chests and all variants

• Beacon (only the ray)

• Mobs (only the ones spawned with spawn eggs, weird!)

• Dropped items

• Particles ❓

• Others ❓

There is another thing, when a player is sneaking near other players/nametags, it kinda blinks other nametags at the same time, but I was on a third party server, so it need further testing.

also see https://minecraft.wiki/Commands/permission

fixed in 24w35a

After testing, I found that:
As with the comments (by kmb and user-01fa9) described, Mojang had tried to fixed this.

Currently, in bedrock edition, if there's no other scheduled tile tick in the same gametick, the behaviors are THE SAME with the attached image for Java (JAVA.png).

However, the image for Java Edition (JAVA.png) is outdated. In 1.18.2, the damage in Java Edition was changed. There is another issue for the new inconsistence after java 1.18.2: MCPE-184329.

So, the two images should be updated to:

The videa shows the behavior when there's no other scheduled tile tick in the same gametick.

However, if there're other blocks having scheduled tile ticks in the same game time, it works not as the image. Due to MCPE-16371, the game cannot make sure that the tip block is ticked first. As a result, when the tip checks the amount of pointed dripstone blocks, some of them has been a falling block entity, which happens when the total amount of scheduled tile ticks in the same gametick is greater than 4.

So, now this is an issue caused by MCPE-16371.