Updated from @unknown
The bug
The regeneration on the beacons works at only 5/8 the normal regeneration speed. Beacon regeneration applies every 80 ticks instead of every 50, so the reduction in healing rate compared to a potion is 37.5%.
How to reproduce
To test, run the following commands:
/gamerule naturalRegeneration false
/gamerule commandBlockOutput false
/scoreboard objectives add health health
/scoreboard objectives add prev_health dummy
/scoreboard objectives add time minecraft.custom:minecraft.play_time
/scoreboard objectives add time_since_healed dummy
/scoreboard objectives setdisplay sidebar time_since_healedAnd then set up command block chain with the following commands (in order, with the first block being a repeating block, and all three blocks being unconditional and always active):
execute as @p if score @s prev_health < @s health run scoreboard players operation @s time_since_healed = @s time
execute as @p if score @s prev_health < @s health run scoreboard players set @s time 0
scoreboard players operation @p prev_health = @p healthAnd then run the following to damage yourself:
/teleport @s ~ ~20 ~Linked issues
is blocked by 1
is duplicated by 1
testing discovered 1
Comments 21
Duplicates or at least related to MC-62103
You need to keep the report up-to-date, if you do not, the report wil be handed over to someone elsewho will, even if you're still following the issue. You hadn't done anything in over 10 years.
Honestly, clam should keep the report as they actually improve it and add information.
Letting a report wither is not helpful to anyone.
I created the report. I don't have knowledge on how to go about fixing it. I can only further report that the bug is still present. People with further knowledge can test more in depth and share their results. That's the point. But it doesn't mean the report itself needs to be passed around like a game of tag. Those who have more information to share will share it either way without introducing that unnecessary complication. If the report goes inactive it is not my fault alone, nor should the reporter be expected to be held responsible for keeping the information up to date. It is a community effort. I brought attention to it, others confirmed its existence, etc. You can't actually expect me to have spent more than ten years doing... something here with this when the developers behind the code haven't even gotten to it during that amount of time. That's absurd.
If it works differently here somehow and being the reporter grants me some sort of tools I haven't been using then by all means hand it to someone who's better equipped. But if I'm supposed to be occasionally updating the OP with the information in the comments and it is on me to keep it up to date then I wasn't aware that responsibility was mine, I apologize, and I'll get right on that after work today.
The reporter is expected to keep affected versions up to date (by adding new versions that are tested), modify title and description to add info where needed, etc.
If the reporter fails to do so, there's no point in that person being the reporter, and adds unnecessary work for mods/helpers to take that on too. That's why the reporter gets changed to a more active user on reports where the reporter is inactive.
This is probably because the regenerate timer resets when the effect does, which happens every three seconds or so.
You can observe the same behavior if you apply regeneration constantly on a repeating command block, for instance – the effect will not appear to work. You'll notice that after leaving the beacon's range, the rate will continue at the normal speed.