The reason the pearls work is because they teleport your feet to the place the pearl lands. (If they teleported your eyes, or any other part of the player you would end up inside of the ground when the pearl lands) Normally when you throw a pearl straight up into a block, it will teleport your feet into that block, but not above it so the block below your feet is still air. If you throw it at the corner, it will still teleport your feet to that position, but it makes it so about half of your hitbox is standing on top of a block, and the other half is not. Since you can stand on that block, you won't fall back down. So no, I would not consider this a glitch since it's intended behaviour that it teleports your feet. (even though it's often called pearl glitching) about 8:30 you can actually go as far up as you want with this, you just need multiple ender pearls (there is also a way to go 2 blocks up with 1 pearl that not many people know about, but the setup for that isn't useful for rsg speedrunning I think)
I think a oneshotless category could be beneficial to ssg. Doing a one cycle vs one shot is such a different meta because of the resources needed. The current status of 1.9-1.12 and 1.16+ ssg is so much more rng dependent than it used to be(which it was already enough). It’s not the funnest grind yet blows old times out of the water even with slightly above mediocre execution.
So for the ender pearls one, ender peals teleport your feet to the pearl's location so when you throw one on a roof your head and pretty much your whole body clips into it. Same with a wall were almost half of the hitbox will clip into the block
Here is one that I think should never have been allowed - boat breaking in a single block. Although boat breaking from 12/13 block heights can be done accidentally and is perhaps more on the edge of what a glitch should be defined as, boat breaking within a single block requires pixel perfect precision (never done accidentally) and has nothing to do with the former method of boat breaking, making it obviously a glitch, at least to me.
I didn't even realize this video only had 455 views until I looked at the comments and saw it, you definitely have the style and production to be a more popular so hopefully the algorithm gives you that
very cool . on next vidio of glitches , say this puting a soul sand on half of the block to get soul speed effect for running with out lossing that is glitch or not ( i'm not good at english so excuse me)❤
The one shot is easily a glitch. The velocity given by the dragon wasn't intended to be used to instantly kill the dragon, nor is one shot killing the dragon with an arrow intended behavior.
Right conclusion IMO, wrong explanation. It's an exploit of a single-tick server-client desync where the game server incorrectly thinks the player has that high velocity which is then added to the arrow's velocity, which I would consider a glitch. I can't imagine anyone would consider server-client desyncs not glitches, consistent or not. But it makes for fun set-seed-glitchless runs so it should be a sole exception. The rules being consistent is more important than word definitions.
"The velocity given by the dragon wasn't intended to be used to instantly kill the dragon" this doesn't really justify calling it a glitch, you can say this about many other aspects of the game "nor is one shot killing the dragon with an arrow intended behavior." technically it is, the game calculates your velocity from the dragon by dividing 8 by the distance between you and the dragon, everything works intended to create an unintended result. nothing malfunctioned, everything worked as normal
The crawl probably works because you dont get unsprinted when you crawl or sneak. You can't start sprinting but since you are currently sprinting they just forgot to implement that check. Not sure why they dont do it but it's kind of better this way.
I do to, since it is abusing a server-client desync (the same cause of ghost blocks). For the uninitiated, Minecraft always runs a game "server" which your client connects to, even when all offline. Both the server and your game client keep track of your player position and velocity, and when you fire an arrow, the server calculates the arrow's velocity from a sum of bow charge & stuff and the player's velocity it has on record. When the player gets hit by the dragon, for a single gametick, the server thinks the player's velocity is really really high, before being quickly corrected. So, shooting the arrow when the server is confused like this gives the one-shot arrow.
The game thinks that you sprint but then it puts you in crawl
The reason the pearls work is because they teleport your feet to the place the pearl lands. (If they teleported your eyes, or any other part of the player you would end up inside of the ground when the pearl lands)
Normally when you throw a pearl straight up into a block, it will teleport your feet into that block, but not above it so the block below your feet is still air.
If you throw it at the corner, it will still teleport your feet to that position, but it makes it so about half of your hitbox is standing on top of a block, and the other half is not. Since you can stand on that block, you won't fall back down.
So no, I would not consider this a glitch since it's intended behaviour that it teleports your feet. (even though it's often called pearl glitching)
about 8:30 you can actually go as far up as you want with this, you just need multiple ender pearls (there is also a way to go 2 blocks up with 1 pearl that not many people know about, but the setup for that isn't useful for rsg speedrunning I think)
The setup is really precise but some runners do it on the obsiddian platform in the end to save mining one block
velocity = distance / time, except when doing Minecraft oneshot 🤪
props to you for
putting so much effort into replying to these comments
mom im famous
I think a oneshotless category could be beneficial to ssg. Doing a one cycle vs one shot is such a different meta because of the resources needed. The current status of 1.9-1.12 and 1.16+ ssg is so much more rng dependent than it used to be(which it was already enough). It’s not the funnest grind yet blows old times out of the water even with slightly above mediocre execution.
TL;DR: unintended consequences of game mechanics
I only clicked that one cuz of the thumbnail, well done
So for the ender pearls one, ender peals teleport your feet to the pearl's location so when you throw one on a roof your head
and pretty much your whole body clips into it. Same with a wall were almost half of the hitbox will clip into the block
1:38
geometry dash players: "easy"
How did you even find my old sprint crawling video lmfao
I spent a long time and found many videos trying to figure out how it works 💀
What are those advancements
ChloeBorpa oneshot
Among us spotted 3:47
Here is one that I think should never have been allowed - boat breaking in a single block. Although boat breaking from 12/13 block heights can be done accidentally and is perhaps more on the edge of what a glitch should be defined as, boat breaking within a single block requires pixel perfect precision (never done accidentally) and has nothing to do with the former method of boat breaking, making it obviously a glitch, at least to me.
I didn't even realize this video only had 455 views until I looked at the comments and saw it, you definitely have the style and production to be a more popular so hopefully the algorithm gives you that
very cool . on next vidio of glitches , say this puting a soul sand on half of the block to get soul speed effect for running with out lossing that is glitch or not ( i'm not good at english so excuse me)❤
The one shot is easily a glitch. The velocity given by the dragon wasn't intended to be used to instantly kill the dragon, nor is one shot killing the dragon with an arrow intended behavior.
but thats just using the mechanic
@@BuiSinhHung Not in its intended way,, someone below me explained it well, "velocity = distance / time, except when doing oneshot"
by that definition killing the dragon with beds is also a glitch...
Right conclusion IMO, wrong explanation. It's an exploit of a single-tick server-client desync where the game server incorrectly thinks the player has that high velocity which is then added to the arrow's velocity, which I would consider a glitch. I can't imagine anyone would consider server-client desyncs not glitches, consistent or not.
But it makes for fun set-seed-glitchless runs so it should be a sole exception. The rules being consistent is more important than word definitions.
"The velocity given by the dragon wasn't intended to be used to instantly kill the dragon" this doesn't really justify calling it a glitch, you can say this about many other aspects of the game
"nor is one shot killing the dragon with an arrow intended behavior." technically it is, the game calculates your velocity from the dragon by dividing 8 by the distance between you and the dragon, everything works intended to create an unintended result. nothing malfunctioned, everything worked as normal
The crawl probably works because you dont get unsprinted when you crawl or sneak. You can't start sprinting but since you are currently sprinting they just forgot to implement that check. Not sure why they dont do it but it's kind of better this way.
awesome
Cool video
Underresearched
cool vid
I deserve pin for not saying first
No you fucking don’t, delete your comment it’s so fucking embarrassing
No you don't.
i feel like one shot is a glich but idk im to dumb for that
Did you watch the video?
I do to, since it is abusing a server-client desync (the same cause of ghost blocks).
For the uninitiated, Minecraft always runs a game "server" which your client connects to, even when all offline. Both the server and your game client keep track of your player position and velocity, and when you fire an arrow, the server calculates the arrow's velocity from a sum of bow charge & stuff and the player's velocity it has on record.
When the player gets hit by the dragon, for a single gametick, the server thinks the player's velocity is really really high, before being quickly corrected. So, shooting the arrow when the server is confused like this gives the one-shot arrow.