World When Player Logs In, Spawn At Same Y Value They Logged Out At

If this is a thing we can change, I see no reason why we souldn't do it,
btw add a poll!
+1 support

 

The words of someone who's never coded before.

________________________________

It's not something we can change.

 

Lol, I have extensive coding experience. I'll grant you, not so much in Java, but I have coded large plugins for bukkit and bungeecord (the technology wynncraft runs on) and I know that it is possible to change this.

It is something you can change, very easily. Literally one statement (plus perhaps one conditional if you want to prevent the possiblity of teleporting the player into the ground)

 

I want you to think long and hard about what you just said.

 

I'm not going to add a poll because the general attitude of people on these suggestions forums seems to be "reject any new idea that we don't understand." Most people don't understand how frustrating this is because they haven't experienced it, they don't understand how easy it is to implement because they haven't coded server plugins before, and they don't understand how much of an improvement a small usability improvement like this can make because they have never studied UX.

 

You think we don't understand it? It just doesn't work coding wise. A: We teleport the player directly to the location, and by default having them spawn 1 block up, B: Spawn them 1 block down and get them stuck in a block.

We clearly understand it. It's very simple. It's not possible.

 

^^^^^^^^^^^^^^
It's not possible, and its not a huge problem. So for both reasons, NO

 

You do realize, all of Minecraft, plugins, and the original game, is Java?

________________________________

I've experienced it, and really it's not a huge problem unless you have severe lag, and if your latency is that bad, Wynn is unplayable for you anyways.

 

Guys, you are all wrong.

Yes, I realise Minecraft and plugins are primarily Java, and I have coded large plugins, I was just stating that my experience with Java is not as great as my experience with programming in general.

It does work coding-wise, and there are numerous possible implementations: teleport player so that they are touching the ground, put a barrier block under the player that only persists until the player becomes active (and is only sent to that player), disable kick-for-flying for players that have not yet turned their heads or moved in a x/z direction, if you are worried about the player being stuck in the ground spawn them on the ground, wait for the player to send some movements to the server and then teleport them one block up.

It is a huge problem, even the tiniest things can be huge problems if they are detrimental to the server's playability. However, this is bigger than a small problem, the frustration accompanied with being kicked for flying from more than 20 servers in a row is a big problem, and the fact that wynncraft is kicking players for flying the vanilla way exposes their poor cheat-detection systems, in solving this they may also move closer to implementing an anti-cheat (finally.)

"It's not a huge problem unless you have severe lag" - even players with poor internet connections need to be considered, as they make up the largest proportion of minecraft's playerbase. Howver, I know that this problem affects even players with 100Mbps internet, it's not just an internet problem, and even if it were it's still easily solvable server-side.

 

Doing what you are saying would add nothing but more lag for the player trying to connect.

 

At least they can connect. And additional lag would be negligible as it's processed server-side, and the servers are faster than the user's internet connection.

 

Ha. Ha.

 

Being able to log in and potentially having to /class sounds better to me than being completely unable to log in. And I don't think changing this behaviour would get many people stuck in blocks, if at all.

 

If you log out on a 1 block tall thing, you'll drop down to below that. Potentially making you permanently stuck.

 

Obviously not if

 

You honestly don't know how the tp / hitbox algorithm works, do you?

 

I feel like this thread is going to lead to a flame war..

Either way, I would not mind if there was less of a chance to get kicked from the server upon logging in, regardless of whether or not it is possible...

 

:)

Do you? Please explain why this idea is not possible.

 

That isn't an option you'll have to /kill every time you get stuck in a block.
The problem lies in your connection

 

But is solvable by the server. So why not?