Fix command prompt issues on dedicated build on Windows
So, this is what I get for not testing the Windows build properly. Turns out that Windows handle stuff differently from everything else, particularly in that it defaults to not listening to input and instead requiring a flag to enable said behavior, while everything else has the opposite behavior. On top of that, it also had a special case for -dedicated which controlled if it would enable console output or not. After getting rid of that and just always assuming both to be true (a dedicated server is kinda useless without these features) it behaved as you'd expect.
Fixes #1290 (closed)
