<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 11:59:00 UTC 2025

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[MC-2773] [ballance issue] Material Cost For Repair can Exceed Initial Construction</title>
                <link>https://bugs.mojang.com/browse/MC-2773</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;i encountered a bug today that i believe to be a flaw in how the anvil calculates repair costs. i had a pick fortune 1 eff 3 i am not sure exactly what the initial enchantment cost was but i believe it was between 25 - 30 levels plus the 3 diamonds for the head of the pick.&lt;/p&gt;

&lt;p&gt;the cost to repair the damaged pick to full was 6 diamonds plus 30 xp levels far in excess of the initial cost of creation of the item. this cannot possible be intended and is a serious flaw in the repair system. material cost should NEVER EXCEED the cost to create the item and the XP cost for repair should be a percentage of the initial enchantment cost and NEVER UNDER ANY CIRCUMSTANCES EXCEED THIS&lt;/p&gt;

&lt;p&gt;the development team needs to pick either material focus or XP level focus for repair because the current system requires excessive amounts of both XP and Materials the current system doesn&apos;t work properly due to the excessive amount of both XP and Materials made far worse by the fact that these numbers can easily exceed initial crafting costs. in my opinion the new anvil mechanics were not properly tested or balanced prior to release and as a result are impractical and useless to the average player&lt;/p&gt;</description>
                <environment></environment>
        <key id="14553">MC-2773</key>
            <summary>[ballance issue] Material Cost For Repair can Exceed Initial Construction</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="5" iconUrl="https://bugs.mojang.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="3">Duplicate</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="corinanth">mike loeven</reporter>
                        <labels>
                    </labels>
                <created>Sun, 11 Nov 2012 10:00:40 +0100</created>
                <updated>Fri, 7 Jun 2013 22:57:24 +0200</updated>
                            <resolved>Fri, 7 Jun 2013 22:57:24 +0200</resolved>
                                    <version>Minecraft 1.4.2</version>
                                                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="22899" author="mentalmouse" created="Sun, 18 Nov 2012 15:02:26 +0100"  >&lt;p&gt;I&apos;m currently working on figuring out the anvil over on the wiki...  Diamonds &lt;b&gt;are&lt;/b&gt; particularly expensive to repair, but it&apos;s not unbalanced.&lt;/p&gt;

&lt;p&gt;For starters, &lt;b&gt;anything&lt;/b&gt; you do starts with the base cost of the item, which depends on the enchantments and is &lt;b&gt;not&lt;/b&gt; what you paid for it on the enchanting table.  When doing unit repair of an enchanted item, &lt;b&gt;each&lt;/b&gt; unit costs at least 1 per enchantment, plus 1 for most materials, but 3 for diamonds (you can get a bargain on the last/only diamond, depending how much durability it covered).  Sacrifice repair is similarly expensive &amp;#8211; repairing an diamond sword with a plain one, costs up to 17 levels (over the target&apos;s base cost) depending on the sacrifice&apos;s durability (worn costs less), and if you&apos;re adding enchantments, that gets added on too.  And then there&apos;s prior-repair penalties....&lt;/p&gt;

&lt;p&gt;Mike Loeven:  First, what&apos;s on it?  Remember, you pay the base cost first, and if you&apos;ve got Looting 3, Smite V, and Fire Aspect, that&apos;s gonna add up.  Second, have you repaired it (small penalty) or renamed it (bigger penalty) before?  We haven&apos;t really figured out renaming costs, but second and sometimes third renames definitely get an increasing penalty.&lt;/p&gt;

&lt;p&gt;ETA:  Also, nowadays, enchantments are cheaper and levels themselves are pretty cheap, between fighting, mining/smelting, and breeding.  I haven&apos;t even bothered rebuilding my big XP farm, I just build minifarms around local spawners.&lt;/p&gt;</comment>
                            <comment id="21198" author="corinanth" created="Tue, 13 Nov 2012 07:53:47 +0100"  >&lt;p&gt;that may be intended but if you can justify 39 level for naming a weapon i would love to hear it&lt;/p&gt;</comment>
                            <comment id="20564" author="kumasasa" created="Sun, 11 Nov 2012 10:29:42 +0100"  >&lt;p&gt;... the repairing cost will also increase with each repairing, also to prevent &#220;bertools.&lt;/p&gt;</comment>
                            <comment id="20563" author="kumasasa" created="Sun, 11 Nov 2012 10:28:10 +0100"  >&lt;p&gt;The goal of the expensive cost is to prevent creating &#220;bertools which will last the rest of your Minecraft life. Of course is the sum of XP and diamonds higher than the initial cost, but you get what you pay for. When you create &amp;amp; enchant a new tool, it would be cheaper, but you might get a pick with &quot;Silk Touch&quot; and nothing else for 30 xp.&lt;br/&gt;
So either you play lottery or you have to pay for it.&lt;/p&gt;

&lt;p&gt;Invalid for now, because not a bug. For feature suggestions/changes please use the &lt;a href=&quot;http://www.minecraftforum.net/forum/1-suggestions/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;MineCraft Forums: Suggestions&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="13814">MC-2307</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Unconfirmed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_11100" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Linked</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i058hb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>