Bukkit

What steps will reproduce the problem?
1.make a jetpack see if you can fly
2.re log and sometimes this fixes it sometimes not
3.

What is the expected output? What do you see instead?
flying. can't fly.

What version of the product are you using?

4.2
Do you have an error log of what happened?

no
Please provide any additional information below.
some of my players say an additional flight hack is needed on their side for it to work
I don't know why it seems to work for some players and not all.

huh... that's wiered... how often does this happend? are you shure they had fueled their jetpack? Did you set the permissions so it could have blocked someone? are they seeing the fuel indicator when they cant fly? are some receving a message from the server (like you are not allowed to fly)? Try to reset the permissions and the config andor redownload the plugin that's the only thing I can think about fr now, because the bug does not seem to come from my plugin since there is no crash report. Maybe you sould try updating bukkit? (try to use the version for the right version of craftbukkit so it is shure it is 100% fawless in my side...)

Ok what we figured out is that for the initial flight the player has to wear only the jetpack, no other armor. After they can fly they can put the rest of their armor on. So far this has resolved the issue with 3 of the players.

ow.. but after the first time they can have any piece of armor and put the jetpack after and fly ? or is it happeneing every single time?

Hey sorry for taking so long to get back. It seems like every time they log on the server they have to go through that process of taking off all armor and having only jetpack on then flying. Once they can fly then they can put the other armor back on. I believe my bukkit is the correct version to run. It still works it is just a bit of a hassle for players each time they log in.

ok, ill put a checker in the onlogin section for next version so it checks if there is a jetpack on you and it allows flight. for the armor to put after it might be a bug from bukkit since the vetsions over 1.6.4 are betas