Jump to content

Recommended Posts

image.png.2e11dee15b3fc3eda3cc117d290fd69c.png

 

this is the format of my data folder. it has been about a month since i updated anything, so i may have forgotten something, but this looks right to me.

 

image.png.835ba554b6cd3341b7874150ef95541c.png

 

i'm not using windows, if that affects anything. i also haven't changed anything in modinfo.lua.( except the version #, which is now 1.10.1). haven't gotten this issue in the past, despite the fact that i did everything the same.

 

hoping i just made some dumb mistake. im able to upload it with "update data" disabled.

tweaked balance.zip

 

here is my data folder (obviously it needs to be extracted)

the mod itself isn't anything particularly complicated. its just modinfo.lua and modmain.lua. if the problem was related to either of the two files, i am sure the error message would be more specific.

i am using the ext4 file system, but dont starve mod tools have native linux compatibility (and i have updated using it in the past) so i don't think that is the issue. i also tried updating the data folder from an ntfs drive. same issue.

image.png.297e748a9f0fdbc430a95f1accbcbf6f.png


i could try dual-booting a different os to see if the issue persists, but i think it has something to do with the folder itself.

last thing: i tried updating a different mod of mine... it works completely fine.

image.png.320e80b8f136dac48ed367726d83da77.png

i tried copying the files of my broken folder into the working one, but that isn't working.

i then tried updating an older mod using the files from the broken one...

image.png.842648c4ef6971e6544a0101c366c96b.png

they are completely different versions. the bug could be related to the specific mod on the steam workshop. i could try making a new one.+

image.png.5542d75cb5a17c6654f27beb2ad65e9e.png

the issue seems to be resolved by making a completely new mod with the same files. no clue why this bug happened, but i seem to be the first person for it to happen to (and hopefully the last.)

 

if anyone else has the same issue as me, what seemed to fix it was completely remaking the mod on steam. this seems like a huge issue, but i don't know if it will ever affect anyone else.

Edited by Ratituee

for anyone that has the same issue, i think it was related to using the flatpak version of steam on a distro that uses a different package manager by default. flatpak apps did not have permission to my home folder, i had to change that to get it to work. i still have no clue why i was able to fix this issue by creating a new mod in the first place, though. 

 

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...