Added the possibility to not use a max level for Fishing

by using a negative number, changed default
treasure.yml file accordingly
This commit is contained in:
bm01
2013-01-26 01:02:04 +01:00
parent 188ad359fe
commit a0a52a3433
4 changed files with 872 additions and 874 deletions

View File

@ -131,10 +131,8 @@ public class TreasuresConfig extends ConfigLoader{
}
int maxLevel = config.getInt("Treasures." + treasureName + ".Max_Level");
if (maxLevel < 0) {
reason.add("Invalid Max_Level: " + maxLevel);
}
if (noErrorsInTreasure(reason)) {
FishingTreasure fTreasure = new FishingTreasure(item, xp, dropChance, dropLevel, maxLevel);

View File

@ -111,7 +111,9 @@ public class Fishing {
List<FishingTreasure> rewards = new ArrayList<FishingTreasure>();
for (FishingTreasure treasure : TreasuresConfig.getInstance().fishingRewards) {
if (treasure.getDropLevel() <= skillLevel && treasure.getMaxLevel() >= skillLevel) {
int maxLevel = treasure.getMaxLevel();
if (treasure.getDropLevel() <= skillLevel && (maxLevel >= skillLevel || maxLevel <= 0)) {
rewards.add(treasure);
}
}