[MC-2653] repairing functionality possibly unbalanced. Created: 09/Nov/12  Updated: 06/Sep/15  Resolved: 10/Nov/12

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2
Fix Version/s: None

Type: Bug
Reporter: chad trate Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: None
Environment:

Windows 7


Confirmation Status: Unconfirmed
Game Mode: Survival

 Description   

The repairing ability in the anvil seems to be unbalanced between tools. I realize its not supposed to be a perfect system, its meant to have diminishing returns and not make the game super easy, however certain things I think could be tooled around with in order to make it a little more incentivized. In its current state, except to repair enchanted items whose enchantment i wish to preserve, its fairly useless to me. If I have a normal iron shovel which is nearly depleted; I have to spend 4 iron to fix it. That seems excessive for something that takes 1 iron to craft. When fixing an iron pick, that is more reasonable since that is closer to the material cost to make it but still not as efficient as just crafting another. obviously fixing either item (enchanted or no) also has an enchantment cost, so if i have an enchanted shovel my material costs are far more excessive than just making a new one and enchanting it again. Iron while a pretty abundant mineral in the game, is still a chore to have boat loads of it for repairing things. also being able to repair bows with wood is kind of annoying, even if i had to use planks instead of sticks would be reasonable to me with wood being infinitely plentiful. I like the addition of this content I just have no use for it. I want to use it, but its just not cost efficient to do so.



 Comments   
Comment by chad trate [ 10/Nov/12 ]

appreciate it thank you. didnt know where that was.

Comment by Tails [ 10/Nov/12 ]

This is not a bug, but a feature request, please post it in http://www.minecraftforum.net/forum/1-suggestions/

Generated at Sun Jan 12 11:58:36 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.