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

Because it will cause more problems

 

No one has given me any stop-dead problems yet, especially none that are worse than the problem of being completely unable to login.

 

Er.. okay, but... then y did u suggest it if u say no1 understands? Its like buying a dog a $50 dollar steak, u might as well not do it.
That being said, you should add a poll.
(Don't mean this in a rude way, i mean that if you posted the thread already, y would u stop at a poll?)


*by the steak thing, i meant "y give a big suggestion if they wont care"/"y give a dog a $50 dollar steak when they'd eat a $2 steak?"

 

The feature prevents you getting stuck each time you log in.
Your problem can be solved by this but it can also be solved by using better internet

 

Using better internet is not an option in 100% of cases where people have bad internet.

Wynncraft has to compensate for this.

 

But then assassins can't get into the detlas airship rip

 

The best an algorithm to spawn you on the ground can do is... Exactly what the current system does.

 

if you stand in the correct spots this can also make it so you can bug out of bound and e.g. see the new area early (happened to me on accident)

 

Yes, and I know people who have spawned on top of the barrier blocks that cover the world because logging in teleports you higher.

________________________________

This is not. True.

 

You dont know how MC servers work. Thats all there is too it

 

You're the one who doesn't know how mc servers work. Have you ever coded one? No? So try before telling other more experienced people that what they are suggesting is completely retarded.

 

Alright since minecraft is written in Java I'll let you tell me what this means because I coded it:

Code:

public class onJoin extends JavaPlugin implements Listener{
    @Override
    public void onEnable(){
        Bukkit.getPluginManager().registerEvents(this, this);
    }
Rank non = Rank.DEFAULT;
Rank warrior = Rank.WARRIOR;
Rank challenger = Rank.CHALLENGER;
Rank champion = Rank.CHAMPION;
Rank builder = Rank.BUILDER;
Rank gamemaster = Rank.GM;
Rank moderator = Rank.MODERATOR;
Rank admin = Rank.ADMIN;
Rank owner = Rank.OWNER;

@EventHandler
public void onPlayerJoin(PlayerJoinEvent e){
    String pname = playerRankColor() + e.getPlayer().getName();
    e.getPlayer().setDisplayName(pname);
}
}

Not giving you the pdata class, but you should know what this means.

Go on, tell me what most of this does.

 

I don't want this raging arguing going further. It looks to be on the brinks of hostility, and that has never been good for anyone. So I suggest you all calm down and think about what you are going into for a minute.

For the actual suggestion, I don't see a problem with the current system. I have experienced it with friends that were kicked for flying several times, just like the issue you are trying to fight.
But I see issues with letting players spawn/teleport in another way than the way it works now. Players getting stuck in blocks, falling through the floor, etc.

So my suggestion is not to spawn differently, but to redo the arguements for the anti-flying-kick. Could be to not kick anyone before moving in a direction while in the air, set the limit for flying higher, or something similar.

 

I have never had any problem with the current system, and I only have really basic coding knowlegde but here's what I think,
Your computer is a potato, and if you get stuck just do /class and then switch back and you'll be fine

 

No, it's not about being stuck. It's about being kicked for flying and being unable to play.

________________________________

[REMOVED]

You have called your main plugin class onJoin, which makes no sense because the main class is not supposed to be a listener (ever heard of modularisation?), which is what your name implies. Also, Java class names should be Pascal case, not camel case. Also, the class' type signature is wrong, it should be final. Then you forgot the space after Listener.

I don't understand why you've assigned all your own Rank variables if you already had them as (what I am assuming are) static properties of another class, however you've gone and misspelled "none", and you've been inconsistent between naming your constants and your local properties. (e.g. gamemaster -> GM.) This is bad.

Then you get around to defining the player join event handler, but you call your "new" player name pname instead of something more sensible like playerDisplayName. Also, do all ranks have the same color? You are not passing any arguments to your playerRankColor function, so they must all have the same color which is kind of boring. If this is the case anyway you should have just defined a local property called playerRankColor, why is it a function? Then you set the player's name as it will appear in chat (and only in chat, which again is kinda boring.)
[REMOVED]

For all that I know, you may be right in your comments, or you may be wrong. What I DO now, is that you don't need to be rude, aggressive, or sarcastic when you are teaching someone. And, if your comments are true, you ARE teaching him. So, don't be rude about it. Drop the hostility. - Moe

 

So you know your shit. And Im kinda new to java.

Anyways, cases dont actually matter, as long as you dont name a variable "this", and Im not giving my code to people, so it doesnt matter.

Same goes with naming classes.

Rank color is a method I created that returns a chat color after it does some stuff, which I actually forgot (I didn't test this part out yet).

Now, how do I cancel this from a server?

Edit: No Im not proud of this, its code I copy and pasted which is like a year old

 

This argument will lead us no where.

Next time you're in game try to /toggle autojoin off if you have it on. It should help

 

This whole argument is confusing ._.

So, from what I understand, the whole "up one block thing" is a Minecraft thing. This can or cannot be fixed through the use of coding.
But if it's a Minecraft thing, wouldn't changing it be changing the source code? You can do that for your personal game, but for the games of 2,000 other people? I have no idea if you can do that. I don't even know if the source code thing I mentioned is right.

Also, Wynncraft does not have to compensate for people's bad internet and potato computers.
But it could. Maybe (I have no idea what the limitations are).
And if it can, it should.

 

yep you got it.

 

If it's such an issue then do /toggle autojoin. Theres literally 0 need to start an entire flame war because other people don't agree with your opinions.

This exists for a reason, whatever it may be. You do have to trust the developers (seeing as you're playing on THEIR server) that this feature still existing, changeable or not, means it's doing more good than harm. If players have an issue with it, there's "/toggle autojoin" which pretty much fixes it completely.

TL;DR suggestions aren't needed for something with a solution already in place