Store Page
Don't Starve Together
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Don't Starve Together

Store Page
Don't Starve Together >  Workshop > w00t's Workshop > Repair Mod v3.1 > Discussions
Repair Mod v3.1
Description Discussions4 Comments148 Change Notes
w00t  [developer] 8 Jun, 2022 @ 4:08am
Bug/Crash Reports
If you end up having any issues with this mod crashing, please follow the steps below:
  1. Right after your game crashes, before launching it again lookup your server_log.txt for the world that crashed.

    For non-dedicated worlds, the file will be located in "Documents\Klei\DoNotStarveTogether\Cluster_#"
    You'll unfortunately need to know which number world it is, which can be done by hovering your mouse over the save file in-game, but remember you have to look at the error log after it crashes so if you need to log into the game to find the number, have it crash again.

  2. In server_log.txt, use CTRL+F to find anytthing relating to a "Lua Error"

  3. If you find a Lua Error, copy the line above it and a few lines below it and post it here with a short description of what happened to cause the crash

  4. If you can't find a Lua Error in your server_log.txt file (and you're sure you're checking the right one) try checking the client_log.txt in the "DoNotStarveTogether" folder and see if there's a Lua error there. If so, repeat previous step.
Post any crash reports you may have down below and I'll try to address them asap. Thank you!
Last edited by w00t; 8 Jun, 2022 @ 4:10am
< >
Showing 1-8 of 8 comments
ventress 8 Jun, 2022 @ 12:47pm 
[00:00:03]: [string "../mods/workshop-850125165/modmain.lua"]:1717: bad argument #1 to 'pairs' (table expected, got nil) LUA ERROR stack traceback: =[C] in function 'pairs' ../mods/workshop-850125165/modmain.lua(1717,1) in main chunk =[C] in function 'xpcall' scripts/util.lua(780,1) in function 'RunInEnvironment' scripts/mods.lua(563,1) in function 'InitializeModMain' scripts/mods.lua(537,1) in function 'LoadMods' scripts/main.lua(356,1) in function 'ModSafeStartup' scripts/main.lua(477,1) in function 'callback' scripts/modindex.lua(103,1) in function 'BeginStartupSequence' scripts/main.lua(476,1) in function 'callback' scripts/modindex.lua(735,1) =[C] in function 'GetPersistentString' scripts/modindex.lua(709,1) in function 'Load' scripts/main.lua(475,1) in main chunk

-----------------------------------------------------------------------------------------------------

I think this is the error log, since 850125165 is the workshop number for this mod. I don't know if it is different for everyone. I never had a crash but I can't seem to continue any of my worlds with this mod enabled. Whenever I disable the mod, my worlds start up as normal.
#1
w00t  [developer] 8 Jun, 2022 @ 1:27pm 
@eilistrae You are correct! However, it looks like it has to do with the fact that the repairdata.lua file hasn't been properly updated. Try backing up the mod folder and having it re-download from the workshop to make sure that every file has been properly updated and see if that fixes it.
#2
Luneyl 18 Jun, 2022 @ 12:50am 
trying to make Boom Hammer from Albe's item back repairble, doing as customdata says:

CUSTOM_HAMMER_VALUES = { --Albe's item back {prefab = "boomhammer", ingredient = "gears", value = 1}, },

CUSTOM_INGREDIENTS = { {prefab = "gears", string = "a gears.", priority = 39}, },

it throws this error on launch:
[string "../mods/workshop-850125165/modmain.lua"]:1269: table index is nil LUA ERROR stack traceback: ../mods/workshop-850125165/modmain.lua(1269,1) in main chunk =[C] in function 'xpcall' scripts/util.lua(780,1) in function 'RunInEnvironment' scripts/mods.lua(563,1) in function 'old_init' ../mods/workshop-2427481232/modmain/stacktrace.lua(545,1) in function 'InitializeModMain' scripts/mods.lua(537,1) in function 'LoadMods' scripts/main.lua(356,1) in function 'ModSafeStartup' scripts/main.lua(477,1) in function 'callback' scripts/modindex.lua(103,1) in function 'BeginStartupSequence' scripts/main.lua(476,1) in function 'callback' scripts/modindex.lua(735,1) =[C] in

trying to add something other than gears or change priority number doesn't work.
Last edited by Luneyl; 18 Jun, 2022 @ 12:54am
#3
w00t  [developer] 18 Jun, 2022 @ 3:42am 
@Luneyl Thanks for the report, I just pushed an update that should fix that issue. Let me know if you run into any other problems.
#4
RCaled 19 Jun, 2022 @ 5:58pm 
Hello. I'm trying to add support for heavy hammer from Jack's Stuff and moonglass hammer from Celestial Tools using customdata.lua but it doesn't seem to be working even with this mod and only those two mods.
These are the lines I have added to customdata.lua:
CUSTOM_HAMMERS = { {prefab = "heavy_hammer", durability = 10}, {prefab = "moonglasshammer"}, },
#5
w00t  [developer] 21 Jun, 2022 @ 4:18am 
@RCaled Is it crashing your game or does it just not seem to be applying the change to the hammers? If it is crashing your game, follow the steps listed above and post whatever Lua errors you come across and I can take a look as soon as I can.

If it's not crashing and it's just not applying the change, double check that you have the correct prefab names for each of those items. Keep me posted!
#6
Luneyl 25 Jun, 2022 @ 10:53am 
Bug in custom ingridients:
-- Your "string" should fill in this blank: "It looks like I'm missing ___________."
It is false. In game it shows only the string typed by user, "It looks like I'm missing" not insertd before it.

Custom hammers section seems to not work:
CUSTOM_HAMMERS = { {prefab = "dualwrench", durability = 35}, },
Trying to add Duel Wrench from [DST] Legion but it can't repair anything. Removing durability not helping.
Last edited by Luneyl; 25 Jun, 2022 @ 10:53am
#7
w00t  [developer] 26 Jun, 2022 @ 5:58am 
@Luneyl @RCaled I just posted an update that should address both of your issues. The missing string thing was just an oversight on my part, it's been a while since I've really looked at the guts of this mod so I forgot how certain things were put together. The custom hammers, however, were mix of a few different reasons, all of which should be fixed now.

Thank you both again for posting bug reports. Sorry it took me a little longer to fix this time, I haven't been at my computer in a day or so. Let me know if you run into any more issues and I'll try to address them as soon as I can. :)
#8
< >
Showing 1-8 of 8 comments
Per page: 1530 50