v0.3.0: corrected wands needlessly bundling max charges

This commit is contained in:
Evan Debenham 2015-05-26 14:25:05 -04:00
parent 2a9d7473d0
commit 854fca08a3

View File

@ -284,7 +284,6 @@ public abstract class Wand extends Item {
}
private static final String UNFAMILIRIARITY = "unfamiliarity";
private static final String MAX_CHARGES = "maxCharges";
private static final String CUR_CHARGES = "curCharges";
private static final String CUR_CHARGE_KNOWN = "curChargeKnown";
private static final String PARTIALCHARGE = "partialCharge";
@ -293,7 +292,6 @@ public abstract class Wand extends Item {
public void storeInBundle( Bundle bundle ) {
super.storeInBundle( bundle );
bundle.put( UNFAMILIRIARITY, usagesToKnow );
bundle.put( MAX_CHARGES, maxCharges );
bundle.put( CUR_CHARGES, curCharges );
bundle.put( CUR_CHARGE_KNOWN, curChargeKnown );
bundle.put( PARTIALCHARGE , partialCharge );
@ -305,7 +303,6 @@ public abstract class Wand extends Item {
if ((usagesToKnow = bundle.getInt( UNFAMILIRIARITY )) == 0) {
usagesToKnow = USAGES_TO_KNOW;
}
maxCharges = bundle.getInt( MAX_CHARGES );
curCharges = bundle.getInt( CUR_CHARGES );
curChargeKnown = bundle.getBoolean( CUR_CHARGE_KNOWN );
partialCharge = bundle.getFloat( PARTIALCHARGE );