Curcuit Store | 37.7 Second End Fight (RTA Dragon Insta-Kill) @CurcuitStore | Uploaded 1 year ago | Updated 3 hours ago
(igt is 37.6 cuz turns out 1000m/t velocity is laggy)
Last video I showed myself attempting a dragon insta-kill RTA(youtu.be/czgSR9Z6U3M). Basically a trick involving accelerating an arrow to extreme speeds using an odd quirk of dragon knockback. And since arrows deal damage proportional to their speed, this can be used to kill the dragon instantly. If you want more information on how it works/how I make it work, I'd suggest these videos:
Original Dragon Knockback Exploration: (youtu.be/DBYgB2sESmM)
Initial Insta-Kill Test: (youtu.be/ON8c6IhE7-E)
Lamer Insta-Kill Test with Misc Info: (youtu.be/OaIesw4T7YE)
However, my last video wasn't particularly fast. So I looked back at my graphs and chose some new points to hit, about two swings above those first ones. Every other swing the dragon does is kinda similar tho, so it's pretty much the same thing from before, just with less time to go further up. I also wrote a crude thing to actually find the points to stand at, so ig there's that. I'll give the points in a sec, but if you want to try this I'd suggest using a real dragon fight/a better map. idk if the map I'm using is the standard or even up to date, but there's a few miiiinor discrepancies that maybe don't matter for zero cycle, but that I tried to correct here cuz I'm paranoid
1: the map dragon spawns immediately. This prolly shouldn't happen though, unless you're running glitched, or somehow enter end in like 15 seconds. So I made it offset by 20 ticks, which is what happens normally (and makes it easier lol). 2: they made map dragon spawn at 0.5 128 0.5 instead of 0.0 128 0.0 for whatever reason. Not a huge difference since the dragon will try to correct itself, but it made my numbers silly so I changed it. Technically it also only spawns dragons at integer degree yaws, which can make super specific coords better/worse, but I was too lazy to change that. (+ my 1 test said it shouldn't really matter and I went with it, esp w/ human error)
Anyway! the numbers. The dragon swoops by at ~y110, so I build up to just below there. And if the dragon was coming in from the x, I would go to 27.9375 -27.125, or 26.125 -28.875 for the Z. These aren't the /most/ optimal (26.132 -28.879 is good for z dragon, idr for x), but they lined up with the block pixels and it doesn't really make a difference(I'm just selfish). Not like I had time to position myself anyway, which I can really only do while building up. Combining air sneak acceleration with ground friction is super nice for small movements ig, so I just (try to) do a tiny input right before landing while pillaring.
If you can hit those exact positions and shoot your arrow perfectly, my dubious math says you should hit the dragon about 2.5% of the time. idk how that translates into real attempts, but it def took me than 40 tries(another like 6 hours- but I also miss like 50% of my bridges/pearls). I feel like the more velocity you have the harder it is to hit the dragon, but idk if that's true. My only explanation would be that I don't shoot the arrow at the right height, and so the stretching out of the vertical velocity over hundreds of blocks is tricking me. Since the dragon gives you a fair amount of upwards velocity(like 1.5m/t), if you're too low then at lower speeds then the arrows might be be able to make up some height by the time they reach the tail/wing hitboxes. But then at high speeds that 1.5m gets stretched out across 400+m, so it only raises like .01m by the time it passes them. If this is true then building up higher/the little jump I do/unsneaking might be important, but also maybe I made it all up.
otherwise yeaaaaa. tbh the 2.5% number scares me cuz it like. borders on feasible. Obviously the big obstacle is just the speed of the dragon, which is just too fast to reliably line up with your own position. Frankly in isolation isn't even hard to solve, I just can't figure out how to make it work. It's literally just relative too so you could just run along with the dragon you to increase your chance. Or even just punch the dragon! which would basically just zero out/reverse its velocity(normal punch would be like .9 / 2 - .4, sprint punch would be like (.9 / 2 - .4) / 2 - .5). Or you could even catch the dragon on one of its turns, since it'll slow to like 1/3 speed there. The only issue is that you only have abt 10 ticks to reach the tickle spot after entering the knockback hitbox, else your damage tick runs out and you get launched. and if you slow down the dragon you increase the time it takes to get there- making the timing either super tight or impossible. Which is why I propose we accept crafterdark owns src into the rules and allow peaceful mode. Or just find a better way to stop yourself from getting launched. Or just get a power 5 bow. idk. gneurshk. maybe worth noting that dragon won't give knockback if /it's/ in a damage tick, but that still doesn't give enough time afaik.
(igt is 37.6 cuz turns out 1000m/t velocity is laggy)
Last video I showed myself attempting a dragon insta-kill RTA(youtu.be/czgSR9Z6U3M). Basically a trick involving accelerating an arrow to extreme speeds using an odd quirk of dragon knockback. And since arrows deal damage proportional to their speed, this can be used to kill the dragon instantly. If you want more information on how it works/how I make it work, I'd suggest these videos:
Original Dragon Knockback Exploration: (youtu.be/DBYgB2sESmM)
Initial Insta-Kill Test: (youtu.be/ON8c6IhE7-E)
Lamer Insta-Kill Test with Misc Info: (youtu.be/OaIesw4T7YE)
However, my last video wasn't particularly fast. So I looked back at my graphs and chose some new points to hit, about two swings above those first ones. Every other swing the dragon does is kinda similar tho, so it's pretty much the same thing from before, just with less time to go further up. I also wrote a crude thing to actually find the points to stand at, so ig there's that. I'll give the points in a sec, but if you want to try this I'd suggest using a real dragon fight/a better map. idk if the map I'm using is the standard or even up to date, but there's a few miiiinor discrepancies that maybe don't matter for zero cycle, but that I tried to correct here cuz I'm paranoid
1: the map dragon spawns immediately. This prolly shouldn't happen though, unless you're running glitched, or somehow enter end in like 15 seconds. So I made it offset by 20 ticks, which is what happens normally (and makes it easier lol). 2: they made map dragon spawn at 0.5 128 0.5 instead of 0.0 128 0.0 for whatever reason. Not a huge difference since the dragon will try to correct itself, but it made my numbers silly so I changed it. Technically it also only spawns dragons at integer degree yaws, which can make super specific coords better/worse, but I was too lazy to change that. (+ my 1 test said it shouldn't really matter and I went with it, esp w/ human error)
Anyway! the numbers. The dragon swoops by at ~y110, so I build up to just below there. And if the dragon was coming in from the x, I would go to 27.9375 -27.125, or 26.125 -28.875 for the Z. These aren't the /most/ optimal (26.132 -28.879 is good for z dragon, idr for x), but they lined up with the block pixels and it doesn't really make a difference(I'm just selfish). Not like I had time to position myself anyway, which I can really only do while building up. Combining air sneak acceleration with ground friction is super nice for small movements ig, so I just (try to) do a tiny input right before landing while pillaring.
If you can hit those exact positions and shoot your arrow perfectly, my dubious math says you should hit the dragon about 2.5% of the time. idk how that translates into real attempts, but it def took me than 40 tries(another like 6 hours- but I also miss like 50% of my bridges/pearls). I feel like the more velocity you have the harder it is to hit the dragon, but idk if that's true. My only explanation would be that I don't shoot the arrow at the right height, and so the stretching out of the vertical velocity over hundreds of blocks is tricking me. Since the dragon gives you a fair amount of upwards velocity(like 1.5m/t), if you're too low then at lower speeds then the arrows might be be able to make up some height by the time they reach the tail/wing hitboxes. But then at high speeds that 1.5m gets stretched out across 400+m, so it only raises like .01m by the time it passes them. If this is true then building up higher/the little jump I do/unsneaking might be important, but also maybe I made it all up.
otherwise yeaaaaa. tbh the 2.5% number scares me cuz it like. borders on feasible. Obviously the big obstacle is just the speed of the dragon, which is just too fast to reliably line up with your own position. Frankly in isolation isn't even hard to solve, I just can't figure out how to make it work. It's literally just relative too so you could just run along with the dragon you to increase your chance. Or even just punch the dragon! which would basically just zero out/reverse its velocity(normal punch would be like .9 / 2 - .4, sprint punch would be like (.9 / 2 - .4) / 2 - .5). Or you could even catch the dragon on one of its turns, since it'll slow to like 1/3 speed there. The only issue is that you only have abt 10 ticks to reach the tickle spot after entering the knockback hitbox, else your damage tick runs out and you get launched. and if you slow down the dragon you increase the time it takes to get there- making the timing either super tight or impossible. Which is why I propose we accept crafterdark owns src into the rules and allow peaceful mode. Or just find a better way to stop yourself from getting launched. Or just get a power 5 bow. idk. gneurshk. maybe worth noting that dragon won't give knockback if /it's/ in a damage tick, but that still doesn't give enough time afaik.
