Minecraft Username:
PixelGuy75
Brief Description:
Not able to upgrade tools to netherite if they are owned by someone else.
Instructions:
Put a tool that is owned by someone else into the smithing table with netherite.
How many times did you recreate this?
I tried this 2-3 times.
Result:
I get a message saying: You cannot craft with items that are owned.
Expected Result:
Should be able to upgrade the tool to netherite version.
Thread Tools
Thread Tools
-
TankNoodle Former Soviet GameAdminPresident ⛰️⛰️ Ex-EcoLegend ⚜️⚜️⚜️⚜️ Prestige ⭐ II ⭐ Gameplay Architect Premium Upgrade
It worked for me on Parker's magic hoe.
-
@Modkiq tried it with my Eff7 pick and I also tried on some elses diamond helmet. Both didn't work for some reason.
-
TankNoodle Former Soviet GameAdminPresident ⛰️⛰️ Ex-EcoLegend ⚜️⚜️⚜️⚜️ Prestige ⭐ II ⭐ Gameplay Architect Premium Upgradethen why did it work for me?
-
HyruleanHero Admin LinkEcoMaster ⛰️⛰️⛰️⛰️ Ex-EcoLegend ⚜️⚜️⚜️⚜️ Prestige ⭐ I ⭐ Premium Upgrade
I encountered the same issue with trying to upgrade Pixel's Eff7. Maybe it's just some star+ tools?
-
Informative x 1 - List
-
-
TankNoodle Former Soviet GameAdminPresident ⛰️⛰️ Ex-EcoLegend ⚜️⚜️⚜️⚜️ Prestige ⭐ II ⭐ Gameplay Architect Premium Upgrade
I also managed to turn chefcraft’s magic jacket netherite so it seems to work fine for me. Maybe you can give the tool to me tomorrow pixel and I can try smithing it for you.
-
Informative x 1 - List
-
-
HyruleanHero Admin LinkEcoMaster ⛰️⛰️⛰️⛰️ Ex-EcoLegend ⚜️⚜️⚜️⚜️ Prestige ⭐ I ⭐ Premium Upgrade
Well, I also just tried with the God Axe that Ness gifted me, but hadn't un-owned, and it gives me that error as well.
-
Informative x 1 - List
-
-
it seems if you shift-click into a smithing table, you are able to upgrade tools that are owned by others, if you click, and drag then you get the error message stating you cannot craft with tools that are owned by others.
-
I've now added this to our development todo list for investigation/fix regarding smithing tables not upgrading tools in certain scenarios during certain conditions.
-
This should now be fixed, please confirm @PixelGuy75