mirror of
https://github.com/mcMMO-Dev/mcMMO.git
synced 2024-11-25 22:56:45 +01:00
Fixed an error where Greater Impact was confused with Armor Impact
This commit is contained in:
parent
7f16339bd9
commit
de93b11c25
@ -57,9 +57,10 @@ public class AdvancedConfig extends ConfigLoader {
|
||||
public int getAxesCriticalPVEModifier() { return config.getInt("Skills.Axes.AxesCritical_PVE_Modifier", 2); }
|
||||
|
||||
public int getGreaterImpactChance() { return config.getInt("Skills.Axes.GreaterImpact_Chance", 25); }
|
||||
public int getGreaterImpactIncreaseLevel() { return config.getInt("Skills.Axes.GreaterImpact_IncreaseLevel", 50); }
|
||||
public double getGreaterImpactModifier() { return config.getDouble("Skills.Axes.GreaterImpact_KnockbackModifier", 1.5); }
|
||||
public int getGreaterImpactBonusDamage() { return config.getInt("Skills.Axes.GreaterImpact_BonusDamage", 2); }
|
||||
|
||||
public int getArmorImpactIncreaseLevel() { return config.getInt("Skills.Axes.ArmorImpact_IncreaseLevel", 50); }
|
||||
|
||||
/* EXCAVATION */
|
||||
//Nothing to configure, everything is already configurable in config.yml
|
||||
|
@ -129,7 +129,7 @@ public class Axes {
|
||||
short durabilityDamage = 1; //Start with 1 durability damage
|
||||
|
||||
/* Every 30 Skill Levels you gain 1 durability damage */
|
||||
int impactIncreaseLevel = advancedConfig.getGreaterImpactIncreaseLevel();
|
||||
int impactIncreaseLevel = advancedConfig.getArmorImpactIncreaseLevel();
|
||||
durabilityDamage += (int) ((double) Users.getProfile(attacker).getSkillLevel(SkillType.AXES) / (double) impactIncreaseLevel);
|
||||
|
||||
if (!hasArmor(targetPlayer)) {
|
||||
|
@ -42,9 +42,9 @@ Skills:
|
||||
AxesCritical_PVP_Modifier: 1.5
|
||||
AxesCritical_PVE_Modifier: 2
|
||||
GreaterImpact_Chance: 25
|
||||
GreaterImpact_IncreaseLevel: 50
|
||||
GreaterImpact_KnockbackModifier: 1.5
|
||||
GreaterImpact_BonusDamage: 2
|
||||
ArmorImpact_IncreaseLevel: 50
|
||||
Fishing:
|
||||
Shake_UnlockLevel: 150
|
||||
Enchantment_Chance: 10
|
||||
|
Loading…
Reference in New Issue
Block a user