jamesmoton

Applying /effect give @s minecraft:poison 34 repeatedly results in no damage taken regardless of the player's current health.
Applying /effect give @s minecraft:poison 30 repeatedly results in taking damage up to twice a second, instead of once every 1.25 seconds.
Applying /effect give @s minecraft:regeneration 30 repeatedly results in healing every time the effect is applied, instead of once every 2.5 seconds.
Applying /effect give @s minecraft:regeneration 31 repeatedly results in no healing actually being applied.

jamesmoton on MC-30946 2021-11-14T04:13:57Z

Can confirm in 1.17.1. However, the regeneration applies at 1 HP every 3 seconds instead of 1 HP every 2.5 seconds, a 16.667% reduction (1 in 1.2) instead of 66.667% reduction (1 in 3).

jamesmoton on MC-136147 2020-08-09T11:40:44Z

You actually don't need the offhand slot to reproduce this bug. If you throw a trident with Riptide III and switch to another item in your mainhand (such as a golden sword), that sword will still take durability damage and it will be as if you attacked with the sword instead of the trident.

jamesmoton on MC-92867 2020-07-01T18:02:35Z

Can confirm for 1.16.1, but crashes with a different error:

com.google.gson.JsonSyntaxException: Expected text to be a string, was null (json)

jamesmoton on MC-187158 2020-06-19T12:25:14Z

Sounds like you may be short on RAM. How much RAM do you have? What other programs did you have open on your computer at the time of the crash? Have you tried other Minecraft versions? Given that the crash report mentioned 32-bit Java, have you tried 64-bit Java?

jamesmoton on MC-114240 2020-03-29T20:38:36Z

Can confirm for 1.15.2

To reproduce:

/tp @p 0 128 0
/setblock 0 126 0 grass_path
/clone 0 126 0 0 127 0 0 126 0 replace move

Or (when standing on a grass path block):

/clone ~ ~ ~ ~ ~1 ~ ~ ~ ~ replace force

jamesmoton on MC-40949 2020-03-24T03:09:08Z

Confirmed for 1.15.2 with the above command, and also with the following command:

/effect give @e[type=ghast,limit=1,sort=nearest] slowness 30 7

jamesmoton on MC-156856 2019-07-18T17:55:57Z

Workaround: Run the following command every X seconds:

/data merge entity @e[type=minecraft:ravager] {Patrolling:0b}

jamesmoton on MC-121855 2019-07-16T03:06:51Z

Can reproduce in 1.14.3. When you press F3+C to get your coordinates (including rotation) as a /tp command, the x rotation value can fall outside the intended range of [0°,360°). This means that in order to get within that range, I need to spin clockwise or counterclockwise accordingly, sometimes a lot, or otherwise manually compute the value module 360° every time.

jamesmoton on MC-147586 2019-07-12T15:31:02Z

From the description of https://www.youtube.com/watch?v=DECKDy8gu1Y:

In 1.13.2, collidedHorizontally is randomly set to true due to floating point inaccuracies when your position is very close to a integer or half integer. This makes sprinting stop. Thanks mojang. So we can't walk at exactly +0.50000 on blocks, we need to randomize a bit. I found that 2° of range (±1°) randomly applied every tick is good enough. In this video it was 1° of range (aka ±0.5°) which is why it stopped sprinting for a tick a handful of times. You can see in the video that when I set randomlooking to 0, the Z coordinate quickly settles on 0.500, then sprinting stops. When it goes back to 1, the Z coordinate moves around 0.500, which lets sprinting continue. Also it's less detectable overall tbh. (randomlooking 10 was an exaggeration dont ever do that lol)

In short: In Minecraft 1.13.2, you can't sprint while being exactly in the middle or on the edge of a block for more than a few ticks due to some floating-point errors. This is despite not actually colliding with any non-floor blocks.