Spring RTS Engine

It's annoying when you're speccing and attempting to read chat messages and the player you're viewing has a lot of units getting stuck, spamming the console with "can't reach destination" messages. It'd be best if spectators didn't get any messages like that.

Just remove the message altogether imho.

Actually, it helps when something stupid happens, like my Commander getting stuck inside an unfolding solar at minute 1.7 - I was helping out an ally and might not have noticed my Commander's stall so soon if the messages hadn't started spamming...

Removing the message would be really bad: unit x cannot blah blah -> f3 camera snaps to that unit and you manually resolve it.

Really, the only problem with the "can't X" message is the frequency. If it were written such that it would only complain once every 20 seconds, that would be fine.

Seperating the consoles to player chat and unit events would help. Also grouping the same events together would be useful and less spammy, like:

Flea: can't reach destination. (10)
Construction KBot: build space occupied. (2)
...

Anyone up to that?

rattle wrote:Seperating the consoles to player chat and unit events would help. Also grouping the same events together would be useful and less spammy, like:

Flea: can't reach destination. (10)
Construction KBot: build space occupied. (2)
...

Anyone up to that?

Even better, make the console messages clickable, so that if you miss to press f3 in time in the heat of the battle, you could still view the event through the console!

Warcraft3 lets you press spacebar up to 8 times to jump to/cycle between the last 8 events. And yes, I remapped it on my controls from f3 to spacebar