ID:1903689
 
(See the best response by Ter13.)
The only way I'm able to see error messages anymore is under Options & Messages.

Has this been changed or is this an error?

~ Happens in every project I run including projects from others.
It's working for me. Maybe you have multiple default outputs?
Indeed, outputs need to be marked default.

You can deliberately output to the Options & Messages menu using world.log as the left hand argument to the output operator.
Thanks but I actually already have my output set to default.

try running:

world.log << winget(usr,"output","is-default")


right after the world has loaded to see whether another control is taking precedence.
In response to Ter13
Output in Options & Messages was 'true'
In response to Ter13
Oh hey, it did actually output that world.log to the output. It put 'true' in the output.

But when an error happens it only outputs to Options & Messages.

Strangeness...


Huh... That's odd... I don't use outputs in my projects, but this might be related to the error changes lummox made in the most recent builds of BYOND.
In response to Ter13
I'm thinking so. One more piece of information. Errors actually start coming onto the output when I do this:

mob
Login()
world.log << winget(usr,"output","is-default")
var/list/L = new/list()
L[0] = 5




But not when I do this:

mob
Login()
var/list/L = new/list()
L[0] = 5
In response to Zecronious
It's clearly a quantum mechanical effect; you're changing the result by observing it.
Best response
Ah. These errors might be popping up because the client hasn't initialized by the time they occur.
In response to Ter13
Yep that was it.

Outputs errors fine:
mob
verb
test()
var/list/L = new/list()
L[0] = 5