Closed muhammedesadcomert closed 1 year ago
Why did you split ItemRepairType into two classes?
Why did you split ItemRepairType into two classes?
Because the same logic was used in 2 different classes (FabricShieldItem and FabricBannerShieldItem), I reduced code duplication by converting it to a single static function.
FabricShieldItem, line 167, FabricBannerShieldItem, line 178.
@CringeStar All the variables I marked as final were assigned only once in their constructor. Since they are not assigned in a different place, they can be final. You can of course remove the final keyword if you ever want to change them later.
@CringeStar All the variables I marked as final were assigned only once in their constructor. Since they are not assigned in a different place, they can be final. You can of course remove the final keyword if you ever want to change them later.
Oh, I thought that there were setter methods for cooldownticks and enchantibility. Ill merge this PR and add those setters tommorow and make CoolDownTicks and enchantibility non final again
Contains;