Numbered Steps to Reproduce Problem:
Set trusted mode to "safe"
Hit GO, watch it give you an error.
Hit Abort.
Expected Results:
Server aborts startup, returns to normal.
Actual Results:
The green button goes red, as if the server had started.
Does the problem occur:
Every time? Or how often?
Always.
Workarounds:
Just hit the stop button, wait a second, and go on your way. It's not really a big issue, but I'd guess it's still a bug worth reporting.
ID:1593288
 Jun 7 2014, 3:26 am
|
|||||||||||||
| |||||||||||||
|
Jun 8 2014, 12:04 pm
|
|
Lummox JR
  |
To reproduce this problem, I would necessarily need to know something about the error you're getting at startup or how to reproduce that. A regular server won't have such an issue.
|
Actually it will, unless you told BYOND to disable it.
On a windows machine, launch a server using safe mode. You are given a warning about that setting. If you hit OK, server will boot. If you hit "Abort", the green icon turns red. But the console says "Startup aborted" | |
I launch servers in safe mode all the time. It's the default mode I test in. You're not given a warning about it unless there's some reason for a warning, like mismatching the .dmb name with the dir it's in. What warning are you getting and what's triggering it?
| |
Should've looked at the warning better.
This is the warning: http://puu.sh/9kWze/6feeb87da0.png And this is what happens when I hit "Abort": http://puu.sh/9kWDV/5eee9f2936.png Timer on the top right keeps running, button is red, but it says it's aborted. | |
