The Dreaded Dynamic Classes

I've managed to keep myself from ever using the damn "v1_5_R1" packages, and I just ran into using one. How can I stay away?

I swear, these packages make me want to puke.

I'm using the "Block" package, mandatory for "Block.<block>," like "Block.STONE."

I'm not using these packages. Not.

 

Why do you need to use craftbukkit in the first place?

 

It's in net.minecraft.server.v1_5_R1, which is changed with every recommended release, by Bukkit. Why, Bukkit?

 

It's not that bad to change a name every update...

 

I think this should explain: http://forums.bukkit.org/threads/safeguard-versioning-policy.123435/

 

Yes, but what in net.minecraft.server do you actually need to use? Most plugins don't really require CraftBukkit (net.minecraft.server) classes.

 

Bukkit has a Block enum, right? Otherwise, could you substitute for the Item or Material enum?

 

Well, why do you need the craftbukkit enum?

 

WHY for fucks sake

 

Does it matter why I'm using a package for you to tell me any alternatives?

Sounds good; I'll try it.

 

Yes it matters why.. How else would I know what alternatives to give you..

 

The only thing I need is an equivalent enum.

 

Jesus christ, you just can't help people these days..

 

And you just can't get help these days...

 

"Mechanic, I need something else to do the job that this pipe used to do."
"What did the pipe used to do?"
"Does it matter? Just give me an alternative."

 

Forget it. I just used (block).getType() == Material.(block).

Technically, it does not. You just need the same type of pipe...

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

You're not looking for the same thing, you're looking for an alternative..

 

Someone lock it? TnT?

 

AKA mom come help me he's being mean