Eros crash handler: More agressive and auto report function
There are mostly (network based) a bunch of exceptions thrown. Those exceptions should automatically be logged (depends on the amount). Network exceptions should never crash the client (or disconnect), only critical ones should (e.g. error in JoinGame packet, already implemented). All other exceptions should theoretically show (depending if it is critical or not) show the error reporter (at least in versions built versions; not on git master,…).
All those erros should be (optionally!) collected and submitted to a crash collections (on a server, ...). This service would need a ton of intelligence and pattern matching to automatically connect duplicated crashes.