James
- jamesmuell
- jamesmuell
- Europe/Stockholm
- Yes
- No
MC-47529
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
It didn't work for me either when I used a selector, with my literal user name, it worked fine.
My command was just /spawnpoint @p. Neither inserting relative coordinates nor using other selectors worked for me.
The game is telling me I used wrong syntax.
The rate of frost walker ice disappearing seems to not be affected by lowering tick speed
sthrough the randomTickSpeed gamerule,it does however disappear more quickly with a tick speed above the default value 3. To reproduce, use tick speeds 0, 1, 100 and 1000.Other things usually affected by randomTickSpeed seem to work fine, tested with grass growth.
The rate of frost walker ice disappearing seems to not be affected by lowering tick speed through the randomTickSpeed gamerule, the ice does however disappear more quickly with a tick speed above the default value 3. To reproduce, use tick speeds 0, 1, 100 and 1000.
Other things usually affected by randomTickSpeed seem to work fine, tested with grass growth.
What does "related" exactly mean in this context? Because I don't know if it is related in the sense that it has the same cause, since changing the tick speed does affect the melting rate, just not for lower values.
I'm experiencing exactly the same problem. The slime block sometimes does launch the player into the air, sometimes it doesn't.
Slime blocks still only occasionally launch the player in 1.9.2. Maybe about a third of all times for me.
Also, whether it works or not seems to somehow be tied to the game's performance. I tried it on another, better computer and slime blocks definitely launched me more often, maybe about 80% of the time. Anyway, that may be why people get different probabilities.
To add to my previous comment, I made two very interesting observations that may be helpful.
1) Whether the player is launched or not seems to not only be related to the performance, but to the frame rate itself. Now that sounds ridiculous and it probably shouldn't work like that, but I tested it several times by limiting the frame rate. At 10 FPS and probably lower successful launching rarely happens, above maybe 30 or 40 FPS it seems to succeed almost every time. All in all however it seems more reliable than it was in 1.9.
2) Other entities (tested with items and creepers) seem to be correctly launched every single time, even at a frame rate of 10 FPS.
Apparently it does, but I'm pretty sure it shouldn't.
Still present in the 1.14.4 jar.
(Feels weird to report it, though, because it's more of a feature request to support unicode.)
That's right. Tickets can never ever be deleted.