It appears that the issue arises from joining the server under a 1.7.2 profile. When connected through a 1.7.4 client everything works perfectly...
I've seen ghost items come about from this ever since I can remember. However, now it seems the items are not just ghost item. Using the...
I've decided not to go ahead with this for now. I'm just short on time, so if anyone else wants to do this go for it. It's a good idea if you ask me.
Try replacing test = rawr--; to test = rawr - 1; -- is the same as -= so you've been reducing the value of rawr by 1 each time you run the for...
What tech said would probably work fine. I've had issues like this before I think what's going on here is that you're creating new instances of...
http://wiki.bukkit.org/Scheduler_Programming
You are using if statements instead of if else statements. Since you update the value and then check what it is right after that, you're passing...
I like it. I'll pick it up when I fill my last plugin commissions, in about a week.:)
Make the plugin dependent on VanishNoPacket so it gets initialized after it? In the plugin.yml: depend: [VanishNoPacket]
ItemStack melon = event.getPlayer().getItemInHand().clone(); melon.setAmount(1);...
...what. Green's idea is more or less exactly what you just said.
Replace event.getPlayer().getItemInHand().setType(Material.AIR); with ItemStack melon = event.getPlayer().getItemInHand();...
You should not be storing the actual player.. This is a perfect situation to cause memory leaks. You should be storing their name instead, it...
I did something like this once. There is no Bukkit method or anything to do this, but it has been done. This is all based off of someone else's...
Why use a database? There are plenty of other options.. Bukkit has a very nice FileConfiguration for YAML. No SQL knowledge needed. Unless of...
Separate names with a comma.
