The champion select chat sucks

Millibyte·1/11/2015, 9:41:07 PM·2 votes·454 views

The champion select chat thoroughly sucks. In almost every single blind pick champion select, some idiots who don't understand latency get into a fight over who called what lane. The said idiots usually copy and paste their chat log, autolock, and/or rage. Majority rule will definitely not solve this problem, because anyone who is too dumb to realize that his chat isn't necessarily accurate will refuse to listen to others. The chat is obviously multithreaded, which is fine, but it is not fine for both the reception and printing of inputted messages to be multithreaded. Any contradiction between players' chat logs could be eliminated by a very simple change in the code: rather than concurrently printing the inputted strings, they should be stored in one dynamic array (i.e. ArrayList, vector, etc.), and then sequentially printed to each player's chat in the exact order they were received. I'm very seriously surprised that nobody has ever requested this (to my knowledge). Unless I'm missing something, this is an extremely small project that would greatly benefit everyone in blind pick at the expense of just a few hours of a few developers' time. If I am missing something, I apologize.

0 Comments