Gnosis

  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

8 Neutral

About Gnosis

  • Rank
    Junior Member
...

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Enable
  1. So, it appears that the people who posted in this bug report: encountered the same issue I did with a different quest. There is however, 1 similarity, I don't know if it is arbitrary or not, but the WX Quest is also in the same quest slot (lower right), and also it has occurred on the same day as my bug.
  2. The quest, "Cry Mercy", with the description, "WX-78's Personal Quest" "Achieve the Merciless card at the end of the match" was not rewarded after I received the merciless card as WX-78. This is not a joke, I had to actually go into a server with new people, and beg them not to use the fire staff so I could do this quest, and after I got the merciless card on the end screen, I didn't even finish the quest. I have screenshots if that is necessary. Beyond just the quest being bugged, it's also entirely insensible. WX-78 will Never, ever, get the merciless card if any player uses the fire staff in the game. The merciless card should, and is, always given to the character using the fire staff or sometimes webber. Please fix and also change/remove this quest. If you are not going to change the quest, please at the very least fix it so that it is rewarded properly. Thank you. In my honest opinion, the quest system is broken for multiple reasons that I won't go in to here because I doubt anyone would even care since it's already been implemented.
  3. Thanks for the response. I'm not sure what fixed it, but the crash has stopped occurring since about a day after I posted the bug report.
  4. This has only started occurring after the latest update at the time of writing this bug report. When I click "Exit Game" (and then confirm that I want to exit the game) on both the login screen and the menu screen, my game crashes (APPCRASH) with the associated DLL being MSVCR90.dll. This crash occurs consistently and is unrelated to mods (all mods disabled). My operating system is Windows 7 and I have the latest version of Net Framework installed. I have attached my client log. I am unable to attach a screenshot of my window crash details so I will copy it here. Problem signature: Problem Event Name: APPCRASH Application Name: dontstarve_steam.exe Application Version: 0.0.0.0 Application Timestamp: 5b493128 Fault Module Name: MSVCR90.dll Fault Module Version: 9.0.30729.6161 Fault Module Timestamp: 4dace5b9 Exception Code: 40000015 Exception Offset: 0005beae Additional Information 1: c9a1 Additional Information 2: c9a111b7ad606d391694568733a9932c Additional Information 3: e595 Additional Information 4: e595c7dc48a77bb33460ed296b0657fb
  5. Since the latest update at the time of writing this bug report, having Astrill VPN installed on my windows machine has prevented me from being able to connect to the Klei Login servers for Don't Starve Together. Upon uninstalling Astrill VPN, I can successfully connect to the login servers. This issue has only occurred in the latest update. Because I have prior experience with a similar incompatibility with Steam, I knew immediately what to do. Steam previously was also incompatible with Astrill VPN after an update. I shared the issue with Steam, and in another update they added a message which displays upon detecting Astrill's Dll that it injects. The message states the relevant Dll and it's related application (Astrill VPN), and starts Steam with different settings that are compatible with Astrill VPN. I have also found a solution to this issue. The portable version of Astrill VPN does not have this incompatibility issue as it only works with popular browsers (Chrome, Firefox, Internet Explorer) unless one manually configures proxy settings on another browser, because of this, the portable version of Astrill does not inject its proxy-related Dll into processes. If anyone else is having this problem, simply uninstall Astrill VPN, restart your computer, then download and use the portable version of Astrill VPN. I have attached my client log when the associated issue occurred.