Bukkit

@6y7t8h

Thank you! The next version will be uploaded in just a few minutes, I have all the new features completed and I'm just testing the Armor as I type this (waiting for my test server to start up) :)

EDIT:

Version 1.2 is now up!

@TheFlannelBeard

Thanks a lot guys! Sorry I didn't end up finishing it last night or today, I was gonna work on it but I was too worn out last night and just went to sleep instead. And today I've just been laying around not feeling too well :/

I really appreciate your support. Ill try to get that update finished as soon as I feel a little better.

And yeah Qwahchees, longboarding is great :) Except when this stuff happens. But its totally worth it.

@_InnoKo_

Glad I could help buddy :), and get well soon! I like longboarding too, haa.

@Qwahchees

That's a really good way to do it. Instead of two arrays, i could just use a HashMap. I'll definitely do something like that though!

@_InnoKo_

I just had a brilliant idea. For damage changing, have one node named all and have the option to add extra items into the list of editing the damage. Like this.

• DamageConfiguration: #Nodes available - All, Swords, Axes, Tools, NoItem, and ALL MINECRAFT DATA VALUES
• All: 2 #add 2 damage to all items
• Swords: 1 #add 1 damage to swords
• IRON_AXE: -2 #reduce damage by 2
• STONE_AXE: 1-2 #Ranged Damage setting, does 1 to 2 damage (randomized by 50/50), if higher randomized evenly

This is probably the simplest way to change damage.

Also, programming wise you'd probably load an array based on whatever weapons are set in the config, then have the system call the numbers from the array whenever the weapon is used. The system would also need to know what items were listed, so possibly another array for item ID's. Ranged weapons would check the lowest and highest number of the range (for example 1-5) and do a math.Random between 1 and 5. I think this makes sense, in theory.

@TheFlannelBeard

Well, I had a lot of plans that would've pushed back the release date.

BUT, fortunately for you guys, I broke my knee today while longboarding. So plans are now cancelled and I'm just gonna be laying down all week healing and programming :)

ETA would be hopefully sometime within the next few hours, since i'll be working pretty hard on it.

@Qwahchees

Yeah, I think that what I'm gonna end up doing is have a default damage, then you can add your own item names with their damages for special ones. Like this:

default damage: 3

item damages:

IRON_SWORD: 5

DIAMOND_PICKAXE: 8

STICK: 1337

And all items will have a damage of 3, except the specific items you added to the list. Does that make sense to you?

@_InnoKo_

Doesn't seem to be an easy way to set that up, individually that is. All I can think of is:

DIAMOND_SWORD:
Damage: 1-10

IRON_SWORD:
Damage: 1-10

etc. But that's pretty sloppy. I'll keep thinking :P

@Qwahchees

The next update (not finished yet, please be patient) includes two ways of doing that:

First of all, there is a new configuration option called "Normal Items Enabled." If this option is set to FALSE, then all items other then weapons, tools, and armor will be disabled. This is a quick way of getting rid of levels for items like Iron Ore.

Also, there is a configuration section called "Disabled Items" in which you can set individual items that you do not wish to use with this plugin. So, if you only wanted to disable the ores, you could add the IDs of all the ores in the game and they will no longer be effected by this plugin.

The next update will be uploaded in a couple days so keep checking back!

EDIT: About the damage thing, I'm still working on finding out a way to make it configurable for each item without cluttering up the config file. If you have any ideas on how you think it should be, please let me know.

Looks SICK.

Edit: New idea, how about add a configuration for what items can be leveled? Not a lot of people want a level 20 Iron Ore, lol.
Also, for my sake could you change weapon damage?

1. 
   
2. onDamage() {
   if (weapon == DIAMOND_SWORD) {
   damage = get.config("DIAMOND_SWORD_DAMAGE");
   set.damage(damage);
   }
   }
   

Something like that?

@dickwick

Both of those problems have already been fixed for v1.2, I just have to finish a couple more things and I'll upload the update.

@6y7t8h

I was actually already working on adding that, it'll be in the next update. Stay tuned!

@vicente947

That's not the full error, it doesn't show a stacktrace...