I found the solution! You need to do the command in others dimensions too. For example if you want the gamerule to be false in the nether, go in the nether write /gamerule NaturalRegeneration false and it’ll we be false in the nether only. If you want to add others dimensions go in them!
Hi, thanks for your interest on this even though I made this ticket quite a long time ago. I'm not sure why it was put in the resolved state, I hope I don't do this for nothing...
I made another video in vanilla 1.19.2 as you suggested, showing my keybinds and my video settings, and in F3 mode :
https://www.youtube.com/watch?v=8Q1ctCdeOfk
(I have an AZERTY keyboard which is why my key binds don't match the overlay at the top right of the video)
Steps :
1) Place yourself anywhere in a 1.19.2 vanilla Minecraft world, preferably facing a particular object to be able to notice the movement flaw. In my video the referential object is a tree.
2) Face the object with one of the angles in my original post.
3) Alternatively press the backwards key and the forwards key while sprinting, around 10 times (like I do in my video). Don't move the mouse or press a strafe key.
At the end you should have deviated a little to the right or to the left from your original position, while you would expect to have stayed on the same line, since neither the mouse or any strafe key were used.
A few days after I made this ticket last year I asked someone who knows the Minecraft movement code very well, and he told me this :
"When you move a direction (X or Z), you normally keep a part of your speed in that direction (54.6% on ground), but only if it's over a certain threshold (|v| > 0.003).
In that video you're moving towards Z, and slightly towards X.
What's happening here is that when you sprint forward, you have enough speed to surpass the 0.003 threshold in the X axis, but not when you're walking. Therefore, over time, you move slightly to the right.
It's a bit stupid, but that's the way it works. Other games normally apply a threshold on the entire velocity, rather than just its individual components."
It's not particularly clear for me but if it can help...
I am pretty sure I did but I did go look on marketplace but I didn’t find it
NVM this is supposed to be like that ,but i don’t know how to remove this report
This is intentional, you should use hoppers, dispensers, or droppers to transport it into shulker boxes.
Yes, the fire was spreading very slowly though
this also happened when i tested it on realms
Try using the realm tomorrow. Currently realms are unstable and basically unusable
Did you try clicking cancel?
Currently realms are very unstable and unusable, try again in 24 hrs.
The same thing happend to me except it crashes whenever I load it a second time. Crash Report Looked Like This:
Minecraft Crash Report ----
// Shall we play a game?
Time: 6/23/20 11:39 AM
Description: Rendering screen
java.lang.NullPointerException: Rendering screen
at nd.a(SourceFile:27)
at mr.b(SourceFile:109)
at mr.a(SourceFile:76)
at dmh.a(SourceFile:134)
at dmi.a(SourceFile:42)
at dmt.a(SourceFile:317)
at dmv.a(SourceFile:117)
at djv.a(SourceFile:67)
at ebs.a(SourceFile:603)
at dlx.e(SourceFile:1021)
at dlx.e(SourceFile:654)
at net.minecraft.client.main.Main.main(SourceFile:215)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
– Head –
Thread: Render thread
Stacktrace:
at nd.a(SourceFile:27)
at mr.b(SourceFile:109)
at mr.a(SourceFile:76)
at dmh.a(SourceFile:134)
at dmi.a(SourceFile:42)
at dmt.a(SourceFile:317)
at dmv.a(SourceFile:117)
at djv.a(SourceFile:67)
– Screen render details –
Details:
Screen name: djv
Mouse location: Scaled: (352, 172). Absolute: (1057.000000, 517.000000)
Screen size: Scaled: (534, 300). Absolute: (1600, 900). Scale factor of 3.000000
Stacktrace:
at ebs.a(SourceFile:603)
at dlx.e(SourceFile:1021)
at dlx.e(SourceFile:654)
at net.minecraft.client.main.Main.main(SourceFile:215)
– System Details –
Details:
Minecraft Version: 1.16
Minecraft Version ID: 1.16
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_51, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 1174969080 bytes (1120 MB) / 2147483648 bytes (2048 MB) up to 2147483648 bytes (2048 MB)
CPUs: 4
JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
Launched Version: 1.16
Backend library: LWJGL version 3.2.2 build 10
Backend API: GeForce GT 710/PCIe/SSE2 GL version 4.6.0 NVIDIA 442.59, NVIDIA Corporation
GL Caps: Using framebuffer using OpenGL 3.0
Using VBOs: Yes
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: vanilla, file/Dramatic+Sky+for+1.14+.zip
Current Language: English (US)
CPU: 4x Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz
Edit: The realm does not even appear on minecraft.net, I don't think its an internet error, its a bug with 1.16's release on java
This is not a bug, the game is designed to be this way.
no, what do I do for older versions?
This issue seems to have reappeared in the 1.14 update. Only now, it just affects players and is working correctly for other mobs.
Jhjhhjjjhggyhhnnhkfdv ojhgghjjn edrtt Kuhn
Hhf
Egyptians are in minecraft
Players blow up when they spawn
Players for sight loosening not are illagers
Sorry realised my mistake after I sent it. I feel stupid now......
This is only on peacefull (duh 😛)
a Spigot server!