World [162 Supporters | ~94% Agrees ] Mage Teleport Location Should Be Calculated Through 1.13 Ray-casting

Have you ever encountered this before?


Well, fear not! Because thanks to a brand new innovative feature blessed upon us from Mojang, we may no longer have to deal with this trauma-inducing teleporting system anymore. Let me introduce: Ray-casting.

Ray-casting fixes the problem of the Mage's awkward teleportation skill. Allow me to explain how ray-casting works. Ray-casting is something Minecraft version 1.13 supports (which Wynncraft is currently running on, not 1.12), it detects the direction the player is looking at, and sends "rays" into that direction until it hits a block. This is not a flawed system unlike what Wynncraft currently uses for teleportation. It will never clip through a block, fence, or glass pane, it will, with perfect accuracy, land on the farthest block in range of the player. You can watch the video to get a better grasp of it.



Another explanation here. Ray-casting is a very good solution to the problem that Mage players recurringly chronically face as well as the Wynncraft developers themselves. It is simpler, more intuitive, easier for players to grasp (huh, my magic spell doesn't seem to like being around blocks?), uses less code, and is a more elegant system than the current teleportation system. But what if you don't want a player to teleport over 100 blocks in one teleport? Well, you can easily set parameters to prevent a player from teleporting outside a certain radius.

The benefits are obvious, it would fix mages being unable to teleport near blocks or while being submerged underwater (note: so long as there are blocks you can teleport to) and also tremendously increasing accuracy of a Teleport spell, and it will completely get rid of the mysterious cheat that causes Teleport to clip through certain edges of blocks. In fact, the current Teleport is so bad that it doesn't even need to be abused on purpose to get outside of the map, it is possible to get outside of the map completely by accident.

Edit: So if no limits are set to teleporting, you could teleport vertically as pointed out by @hppeng. So to solve that, if one were to teleport facing Y above 60 degrees, the Teleport's Y-direction would be automatically be set to 60 degrees. This prevents teleporting directly vertically upwards. Thanks @hppeng for telling me about the flaw!

The dotted line is what it would be without this fix, but with this, the angle is calculated only after it has been set to the 60 degrees limit, preventing clipping or unexpected results. Note that it is still possible to teleport vertically downwards.

milestones:

Spoiler: milestone box xdd

50 supporters - yes
100 supporters - yEEEeeE
150 supporters - ya
200 supporters - no
250 supporter - non
300 supporters - not
350 supporters - never

10 likes - ye
20 likes - double ye
30 likes - yes x3
40 likes - (yes)(2^2)
50 likes - 是的
60 likes - yes
70 likes - no
80 likes - no
90 likes - no
100 likes - definitely no

what the vote means in case its unclear
yay = + support, non = - support, wat = neutral.

 

Call me stupid, but I don't understand any of what you just said, is there any way you could explain it more clearly to people like me? Or no, I'd be fine with that as well...

 

Make TP shoot an invisible projectile with no gravity that goes theoretically infinitely fast, and tp the player to where the projectile lands OR is if it didn't hit any blocks after reaching the max tp range
Kinda like:

 

Actually, you know I really like this idea. If you implement what Seek said in his comment I feel like you might have a very strong idea here.

Additionally, spell damage could increase this max tp distance

 

THanks

 

I accidentally glitched out of tbe map three times on my mage going 1-100, and had to /kill multiple other times when i got stuck from teleport XD

 

bump~ failed teleports and accidentally teleporting out of the map is so annoying smh

 

Renamed thread title to "Mage Teleport Location should be calculated through ray-casting.", hopefully people will understand it better.

 

Oh this would be very helpful for my new mage character

 

I see no reason for this not to be implemented, unless somebody brings an argument against raycasting.

 

yes this is good

 

This is a great idea; However, I don't think it will be in the game anytime soon. Wynncraft, like Hypixel and a few other servers, is flexible with versions. The lowest version you can use to play right now is 1.9 (Might be wrong, if so plz correct me), and ray-casting would limit players to 1.13 and up.

The first solution I can think of would be to give anyone playing on 1.12 or below the non-updated spell, while 1.13 players get the version with ray-casting. Idk if this is even do-able though.

 

While this is a good idea like it would be great +1
I think (not 100%) that wynn is not coded in 1.13 format so then like everything would have to be changed and to do it just for this isn’t practical.

Someone correct me if i’m wrong

 

All the command blocks, functions, and plugins would be server-side, so it won't matter what version the client is on

jpresent has said that the server's inner workings are based on some kind of 1.7 - 1.13 command block and function hybrid, it was in an old thread from a few months ago, way before Economy Update was announced.

 

Im not sure what this means or how it works o_o

 

I mean the guy in the video was clearly able to move only 1 black in the direction he was facing. I'm sure the devs could make it teleport you a maximum distance if the target block is not within range.

 

Should I count 'wat' as support or at least a +0.5 support?

 

Just as a FYI, raycasting has existed way before 1.13. I believe it existed as old as 1.8 (armorstand raycasting), although it wasnt usually as accurate as 1.13’s raycasting using the relative directions since there needed to be a set of command blocks for each direction. By 1.9 it already became much more efficient too, since there were the 3 types of command blocks added.

 

Nah because people have already voted it so then it would be counted as +0.5 support even if the person who chose that option didn't intend it to.

 

Great idea, I mostly play mage so
I GET STUCK A LOT
Thanks, random holes. Thanks, COTL trees.

Also that art is magnificent