• Announcements

    • JoeW

      [UPDATED] Physical Megapack Disc Issues   04/16/2018

      We are now ready to accept claims for PS4 Megapack replacements.  Once again, our deepest appologies for this entire situation. We understand that your purchase of the Megapack was a show of support by our fans, many of which already owned the game. Please know that we have done our best to push as hard as we can for a quick and fair resolution to this issue. This has taken WAY too long to be resolved but we have done everything in our power to make sure our fans get what they purchased.   We are going to use the voucher codes we have been using to provide the digital version to claim the physical replacement discs. For North America, we are handling these requests directly through our own store with help from our friends at IndieBox. Claims will be handled at no cost to you. For claims outside of North America, 505 will be taking your information and processing your claims.  Those who purchased the Megapack after 4/26/2018 should have been given a voucher at the time of purchase on your receipt.  Those who purchased before 4/26/2018 or did not get a code otherwise can contact us for a voucher code that will entitle them to the digital megapack and can be used to claim the physical replacement discs. We have been handing those out for a while now, but if you are in this category and have not requested a code, you can do so here: http://support.kleientertainment.com/customer/en/portal/articles/2935839-physical-mega-pack-disc-support-information Once you have a voucher code:
      For purchasers in Europe (SIEE). To make a claim you will need to make file a claim through 505 here: https://docs.google.com/forms/d/e/1FAIpQLSckru65CWkXH5RZ_3j2f5_h1djNiAyrl8R0PCvdKPmGwItyvA/viewform For purchasers in North America (SIEA). To make a claim you will use our support site and use the voucher code to claim a replacement here: http://support.kleientertainment.com/customer/portal/articles/2952265-ps4-faulty-disc-claim If you have any questions or concerns, please let us know here on this thread or contact us at livesupport@kleientertainment.com Thank you.   

alainmcd

  • Content count

    620
  • Joined

  • Last visited

Community Reputation

888 Excellent

About alainmcd

  • Rank
    Senior Member

Badges

Chester Kickstarter
  • Supported Chester
Don't Starve Together
  • Contributor
Oxygen Not Included
  • Alpha Contributor
  1. Bee hive, pig house crash

    I reported this bug a few months back (link), but it hasn't been addressed yet. Luckily, you'll only lose up to a day's progress, the issue is resolved when reloading your game and you'll be able to continue normally.
  2. I'm assuming the world you host that shows the ping properly isn't the same world. Go to (My) Documents\Klei\DoNotStarveTogether\Cluster_5\Master and open server.ini in any file editor, open the server.ini file for the other world you're hosting and compare the server_port from each file. Change the server_port from Cluster_5 so they match - should be OK as long as you don't try and host both worlds simultaneously.
  3. @FreyaMaluk, sorry, I have no idea. Is your ping shown when you host a server with caves? I believe it's the server_port under [NETWORK] in the server.ini file of your master server the one that should be forwarded, so make sure it is. Other than that I can't help you.
  4. Yes, c_shutdown() saves your world unless you explicitly tell it not to with c_shutdown(false).
  5. how to create about regen mod

    @orlyx, I think so.
  6. Hi @Xiellify, welcome to the forums! (And sorry for the late reply!) It does look like the port that your caves server is trying to use is already being used. Do you happen to have another server running? If not, you can manually change the port by going to (My) Documents\Klei\DoNotStarveTogether\Cluster_5\Caves and opening server.ini with a file editor, then changing server_port = 10999 under [NETWORK] to something else, for example, server_port = 11009.
  7. @lilmist, yes, you have to shut down your server first. Start the game client, go to the Host screen, open the Mods tab and deselect the mods you want to remove. You might have to briefly enter the game to confirm the changes. Exit and relaunch your server via your script.
  8. Hi @lilmist, welcome to the forums! Check the section "Help! E_INVALID_TOKEN or E_EXPIRED_TOKEN" in the OP.
  9. @Scrubberinos, yes (unless you have set up your server not to pause when empty).
  10. @Soulk, it should. @Scrubberinos, something's preventing your server from launching. Usually it's either a mod crashing (try hosting a world without mods) or the ports are already in use (could be an instance of the dedicated server tool running, for example). If you're still having issues, post your client_log.txt (Documents\Klei\DoNotStarveTogether\client_log.txt) and your master server's server_log.txt (Documents\Klei\DoNotStarveTogether\Cluster_5\Master\server_log.txt).
  11. It seems to me appeasing the volcano doesn't increase/reset the timer until the next eruption, but instead pauses the current countdown. Either way the eruption is delayed, the difference being the lack of new warnings in the current form. I don't know if it's intended, but it does feel counterintuitive.
  12. Thanks, I can't try it out right now, so I've linked your suggested script in the OP.
  13. @canada11, welcome to the forums! It doesn't matter if the Caves or Master server is started first, the server.ini file for your Master server will be set up appropriately (is_master = true) when creating the cluster. A little testing suggests E_INVALID_TOKEN is shown if there's no cluster_token.txt in the cluster folder or if the file is empty, and E_EXPIRED_TOKEN if the token is invalid. Also note that I originally wrote in the guide that the token file should be named cluster_token.ini instead of the correct cluster_token.txt, I've corrected it. If moving/copying the file to your cluster folder doesn't work, I can only suggest generating anoter code by login into the game, pressing the Account button, then the Generate Server Token button and pasting the new code into the cluster_token.txt file in your cluster folder. Other than that I can't think of anything else.
  14. [Game Update] - 233745

    Hey @Jason, it's great to see so much effort is still being put into SW! Are there any further plans for SP other than bug fixing the new content in SW (and Hamlet)? There are a couple of new cool things mentioned in the code that don't seem to be implemented yet or are simply commented out. There's also old unused code that hasn't been removed, like the fire snakes - any chance they'll be included in the future? On bug fixing, there are still old SW bugs (and vanilla and RoG) that remain unaddressed, including some crashes (Wilbur speech crash or ignited beeboxes), annoyances (krampus spawns were fixed in SW but not in vanilla or RoG, the Quacken can spawn out of reach) or several other minor issues that should be easy to fix. Should we re-report them?