AI-team wrote:epsy wrote:That's a fine eye you have there!

Is there any way to disable this "layer"?
Nope. It's there so the text stays readable no matter what the background is. Remember how we were limited in the choice for rim wall textures because the console needs to be visible when rendered on top? We don't have to do that any more.
Lacka: yeah, a fixed number of rows would be easily possible and should probably be the default, with the default camera settings adapted so the console doesn't obscure the action. Cockpit integration may be more difficult. It was talked about, but never done; I'll see what I can do.
AI-team wrote:
epsy wrote:Too sleepy right now to be sure if this is the right decision.
It definitely isn't the right decision. A lot of people have invalid color codes in their instant chats and it's pretty annoying to see the code instead of the colored text ( sometimes, when people have color codes like "0xLOLLOLDef Down" or whatever, I takes some seconds until I realize what they are talking about

)
They are INVALID codes. They should not render. I'm personally not putting any work in re-establishing a bug in a system that was never intended to be used by players in the first place. Tell people to fix their codes. What we CAN do is add code to the 0.2.8 branch that 'corrects' the codes as they are received from old clients. It should make it to enough servers by the time 0.4 gets released that it's no longer a problem.
Edit: actually, no, we shouldn't do that. It'd be just another weird thing we do to strings in the pipeline that may bite us in the back later. People should fix their codes.