Bawn djorno, I want to report a bug with the mod since wog itch update: When one leaves an area and comes back, items deleted with the hammer will reappear as if not deleted. After removing the mod, the issue was resolved.
[Edit] This looks like a critical bug, related to significant changes in the way Bog Witch handles piece rendering. Please do not use until I post an update, and uninstall if possible.
You should already be able to change the key bind in the config (easiest way is with config manager; the setting is named "UndoKey"). Yes, Ctrl+Z should have been the default!
Pretty sure your bug was related to an Ashlands change that I didn't detect, since as you mentioned, it doesn't affect functionality. This is fixed in the next release, which is already posted for testing on Discord. If you're able, it would be great if you could download and verify the error is gone: UnRemove 0.1.7
Great mod and nice to use. I am trying to use an xbox controller on PC with this mod but it doesn't work. The key setting button recognizes the button press combo but doesn't do anything. I also tried just the X button and that didn't work either. Keyboard works though. Should the controller work? If so then maybe another mod is conflicting. I use Server Dev Commands Mod so my wife and I can both use server commands. I mention it because it would be my first suspect.
It's probably just my laziness. I haven't updated any of my keyboard handling to accommodate a controller. I was going to get around to it, but don't have a controller to test. It's part of my common framework, so every mod released after I change it will be updated. Great if it works right, but bad if I break something. I'd have to retest every mod's controls. Someday.
From Tartek67: I greatly appreciate your honesty and quick reply. Is there a console command that I could bind to. Sever dev commands gives me the ability to bind buttons to commands. Like fly and env clear etc.
No console command. Sorry. I'll see if I can change over for this mod and then consider including it as the new standard for others if it goes well. Don't have a date, however, for when. Would you be willing to download from Discord to test?
Absolutely :) While we're chatting I was hoping you might be able to have a setting in config to make it so you do not have to have the resources to restore the item for the nocost mode. Or even have it happen automatically if nocost is on in server settings.
I removed the inventory check for no-cost build. Looks like the switch over to support controllers will take longer. I posted this release in #mod-beta-releases on Discord if you want to download and try it out.
Hi, I'm responding to your previous post since I didn't want to confuse folks reading it. I can understand you may not be able to play the Ashlands version. UnRemove 0.1.6 will work on previous game versions and in Ashlands, but in Ashlands it has a bug that throws a non-fatal exception when undoing a remove when you don't have the materials in inventory. You won't notice it unless you looked in the log file. The beta release you were testing, 0.1.7, fixes that bug, but as you've noticed, does not work with previous Valheim versions. Thanks for trying to test. I'll release 0.1.7 soon, but you'll need to stay on the older version for now.
Wonderful, thank you for making this. You have no idea how many times Ive needed it lol. I hate nothing more than working on a build that requires support and accidentally taking out a supporting piece. Being able to quickly hit a key and put it back before it all collapses is amazing. On top of the obvious regular irritation of removing the wrong thing, which while not always critical, is a groaning moment for me every time.
Note to others that when using it, if something the piece was supporting has already fallen, it will not replace that piece. For example, a torch on a post. Remove the post, the torch falls. Because they are separate pieces, the torch will not be replaced, only the post, unless you fix it quickly before the torch falls. So hit it fast, and nothing falls. Itll save you lots of time when you accidentally remove a critical piece and half your build is about to fall apart. Although when the piece is supporting multiple others connected to it, they will not always fall in the logical line, sometimes pieces down the line will break first, so you should be sure to undo it before any pieces fall.
Also, two bugs that often occur together; 1- The pieces sometimes come back in a completely damaged state. They still support fine, they just are very damaged and need repairing. 2- Sometimes pieces will come back in a fully grounded state when they shouldnt be.
Thanks for your comments and observations. Pieces coming back in the same damage state as when they were destroyed is actually by design. They shouldn't be in any worse state than when they were removed. Please confirm they come back 'worse' than they were when removed.
I'm not sure what you mean by "fully grounded'. Please elaborate, and thanks again for your help.
Yes, I mean they come back as fully damaged (0 yellow in the repair/damage bar) and fully visibly degraded when they were destroyed at full health. As for when I said fully grounded, I mean they are in the blue state, at 100% stability, which means they are either directly in contact with terrain (automatically 100% structural integrity) or the piece supporting them has more than or at least equal to the supported pieces max integrity. Which shouldnt be happening to wood walls stacked multiple pieces high on each other, for example.
I think the problem might be that if you press the reundo hotkey late in its timer before it falls, like right before it would fall or at the same time, it registers it as severely damaged or something. Which is still weird because when it happens, it always comes back at 0 health, but still standing, and usually at 100% stability even when it shouldnt be.
Also no problem, thanks for making a great mod. Ive used it many times already lol
I'll see if I can figure this out. I didn't see that behavior in my testing. [Edit] Bug is confirmed. Affects undamaged pieces created prior to the current player session. [Edit] Fixed in 0.1.1
Note regarding 'grounding'. UnRemove does not calculate the structural integrity of the pieces it restores, which are always restored 'blue'. Valheim eventually recalculates the pieces support automatically.
28 comments
[Edit] This looks like a critical bug, related to significant changes in the way Bog Witch handles piece rendering. Please do not use until I post an update, and uninstall if possible.
I would really enjoy the option to assign a modifier key so I could use Ctrl + Z haha
I also get a console error when removing a replaced object something like Unknown key -40000
It doesn't seem to effect the mod but it is weird
Thanks for the mod
You should already be able to change the key bind in the config (easiest way is with config manager; the setting is named "UndoKey"). Yes, Ctrl+Z should have been the default!
Pretty sure your bug was related to an Ashlands change that I didn't detect, since as you mentioned, it doesn't affect functionality. This is fixed in the next release, which is already posted for testing on Discord. If you're able, it would be great if you could download and verify the error is gone: UnRemove 0.1.7
sorry I have second account for another computer.
While we're chatting I was hoping you might be able to have a setting in config to make it so you do not have to have the resources to restore the item for the nocost mode. Or even have it happen automatically if nocost is on in server settings.
I hate nothing more than working on a build that requires support and accidentally taking out a supporting piece. Being able to quickly hit a key and put it back before it all collapses is amazing. On top of the obvious regular irritation of removing the wrong thing, which while not always critical, is a groaning moment for me every time.
Note to others that when using it, if something the piece was supporting has already fallen, it will not replace that piece. For example, a torch on a post. Remove the post, the torch falls. Because they are separate pieces, the torch will not be replaced, only the post, unless you fix it quickly before the torch falls. So hit it fast, and nothing falls. Itll save you lots of time when you accidentally remove a critical piece and half your build is about to fall apart. Although when the piece is supporting multiple others connected to it, they will not always fall in the logical line, sometimes pieces down the line will break first, so you should be sure to undo it before any pieces fall.
Also, two bugs that often occur together;
1- The pieces sometimes come back in a completely damaged state. They still support fine, they just are very damaged and need repairing.
2- Sometimes pieces will come back in a fully grounded state when they shouldnt be.
I'm not sure what you mean by "fully grounded'. Please elaborate, and thanks again for your help.
I think the problem might be that if you press the reundo hotkey late in its timer before it falls, like right before it would fall or at the same time, it registers it as severely damaged or something. Which is still weird because when it happens, it always comes back at 0 health, but still standing, and usually at 100% stability even when it shouldnt be.
Also no problem, thanks for making a great mod. Ive used it many times already lol
[Edit]
Bug is confirmed. Affects undamaged pieces created prior to the current player session.
[Edit]
Fixed in 0.1.1
Note regarding 'grounding'. UnRemove does not calculate the structural integrity of the pieces it restores, which are always restored 'blue'. Valheim eventually recalculates the pieces support automatically.