Maybe add Wickerbottoms "on tentacles" to his crafting tab as tentacles are non-renewable, just a suggestion?

Seems to be crashing in Caves when Bunnyman is inspecting/targeting a player to see if they have meat in their inventory. Error log: http://pastebin.com/Q2qMPqCS

Thank you thank you @Deja Vu. I will get the codemonkey on it tonight.

Nevermind, I figured it out. Will update ASAP, thank you for the report!

Alright, just pushed an update. Fixed it as far as I could tell. Thanks again for the report and let me know if the fix worked!

@Plasmids
At first glance it seems it's working, thanks.

@Plasmids
Please add "version_compatible" into modinfo.lua as well so that when the mod gets updated, people can still join servers.

I'm not sure exactly how that works. Do I want the previous version with the old name to be compatible with the new update? Wouldn't that cause issues?
I figured it would be added for smaller changes that wouldn't cause crashes between the server and client running different versions.
In this case, if I were to add it currently, what would I put?

@Plasmids
It's true, if you make huge changes, it might cause crashes, but that is pretty rare and the crashes can only happen on client side.

Your current mod versions is "1.1.2". So in order for the "version_compatible" to work, you would need to set it in modinfo.lua like so:

version = 1.1.2
version_compatible = 1.1.0 (or 1.0.0 or 1.1.1... whatever is lower than the actual version of your mod)

If you feel like you have made huge changes in your mod and you fear it might cause client side crashes, you can change the "version_compatible" number to the same as your "version" number is in your update you push. So for example if you push an update for version 1.1.3 you would publish it with settings like these (taking into account that previously you had the above values):

version = 1.1.3
version_compatible = 1.1.3

This means Workshop has the version 1.1.3 now with version_compatible 1.1.3 as well and server has version_compatible 1.1.2 which means Clients can't join the server anymore without server having the newest version.
Then you can keep the version_compatible 1.1.3 and push future updates normally (by just changing the "version" value) and again if you, at some point, feel like there is a huge update, put the version_compatible value to the same as the version number is you are publishing.

I have published all my mods with basically the "version_compatible = 1.0.0" and pushing updates like mad without any problems.

Hope this helped.

@Deja Vu Thanks! The very last update causes a crash because of misnamed .xml files, but Plasmids may do this for future updates.

66666

Happened a crash whith him. Only with me?

Elzador, I've not seen any other reports of crashes. Can you post your log or a screenshot of the error message?

WTF! My English is poor ...... OMG

dodacie tę postać do dont starve bo jest bardzo fajna