Krishna Kokatay

Can confirm in 1.20.3.

Can confirm in 1.20.3.

Some syntax must've changed between pre 1.20.X and now. Because I was facing a similar issue where I had:

scoreboard objectives add VDhealth health
execute store result score @s VDhealth run data get entity @s Health

This would give the read only error in the most recent version. To fix the issue, all I had to do was change the objective from health to dummy.

Still affects modern minecraft up through 1.19.4-pre1.

effect give @s minecraft:saturation 1200 0 true

Will only give 60 seconds of saturation.

Confirmed in 1.18,1, 1.18,2, 1.19, 1.19.2, 1.19.3, and 1.19.4-pre1.

Is this ever going to be resolved? Since 

execute as @a[nbt={ActiveEffects:[{Id:23}]}] run say I have saturation.

doesn't trigger on any ticks, I'm currently using a work around by using an amplified luck potion to trigger the effect command. 

Bug is still present in 1.19.3.

This has been partially fixed in 1.16.3. The block still goes through the breaking animation, and freezes the animation if you stop prematurely, however the actual block breaking upon completion of the break block animation (the cracks through the block), does not result in a broken block. I cannot find the bugfix that directly solved this issue.

Though I'm weary to call this issue completely fixed. There is still the problem of the block breaking animation occuring. And the fact that it remains until the block is interacted with again.

Reproduced in 1.16.1

It doesn't matter if the effect is only obtainable with commands, the matter of fact is that this behavior is unintended, and has been subsequently identified as a bug.

Personally, I use the effect in datapacks/mapmaking, and it has a very notable impact on player experience.

Confirmed for 1.14.4