The "bad setting" kinda puzzles me - especially if it's a graphical setting or something similar. Can't that just be detected and get reverted to a lower detail setting that should work?

Zero K Lobby offers to set graphics settings to low if it detects a crash. Maybe other lobbies can do this as well?

Main complaint seems to be getting very large logs on lua error causes performance problems?

Basically an issue only for engine and game devs, and game devs overwhelmingly want it back as it was.

error log causing performance problems are the least of my worries...
when there's "that much" error you might want to fix it

jK mentioned saving SSDs in a lobby conversation as well. Which is all well and good, but this isn't a concern for many if not most of us and an option to disable buffering would still be nice.

Yes, bring back non-buffered infologs please.

thanks abma!
https://github.com/spring/spring/commit ... e088b1cad8

instant infolog by adding
LogFlush = 1
in springsettings.cfg or spring.exe - edit settings.

http://springrts.com/dl/buildbot/defaul ... -gc80432d/
I tried two minutes or so and it always flushed and never clogged.

@koshi
main reason (in my eyes) why auto upload of infolog died was, cause SL (nearly always?/for most users?) crashed while doing it.

as koshi said, the site that zydox did for browsing/managing the automatic reports existed, and in my eyes it was/is finnished and usable. it parses infolog (and a few other fiels fro mthe reports), stores lots of values per report into a DB and then allows to browse, order, filter by and create custom views of these values through a web-interface. so you could for example search for all reports that crash on adress 0x123456, and display the GFX card string.