Descriptive Problem Summary:When ever i boot the game server, after the server starts dream daemon crashes
Numbered Steps to Reproduce Problem:1. Open Dream Deamon
2. Select the executable file and hit go
3. Once the server boots join the server
Code Snippet (if applicable) to Reproduce Problem:
Expected Results: Ability to host without crashing
Actual Results:Dream Daemon crashes after server starts
Does the problem occur:
Every time? Or how often?: Every Time
In other games?: Yes
In other user accounts?: Yes
On other computers? : N/A
When does the problem NOT occur?: It occurs everytime
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked?: N/A (Visit http://www.byond.com/download/build to download old versions for testing.)
Workarounds:
ID:1960784
 Oct 15 2015, 4:39 pm
|
|||||||||||||
| |||||||||||||
renaming ban.txt seemed to fixed the issue
| |
Okay, if you send me the old bogus ban.txt file I can take a look.
| |
Seems like I'm having this issue as well but we have no ban.txt file in our BYOND folder. If you could help it'd be very appreciated.
https://dl.dropboxusercontent.com/u/8290505/ Crash%20Details.txt | |
Your issue is completely unrelated and should have its own report. What you posted isn't crash details, but a hang, and it doesn't contain any information I would need to diagnose the issue.
In several recent threads I mentioned how WinDbg can be used to get details from a hanging Dream Seeker instance, so you should check those out and apply the same instructions--but to dreamdaemon.exe instead. However when you get that info, you should post it in a new thread. | |
Alright, I'll do that thanks.
| |
Also Buster has been trying to contact you for a little while now I believe. Just a heads up.
| |
I have a hunch that cfg/ban.txt may be related to your issue, so I suggest renaming that to something else like ban0.txt, and you should do likewise with hostban.txt. (The cfg dir I'm referring to is in your user data directory, which is probably My Documents\BYOND.) If that fixes the issue, that's a big clue. But the crash details are absolutely vital.