[01:59] *** GLaDOS has quit IRC (Read error: Operation timed out)
[01:59] *** phuzion has quit IRC (Read error: Operation timed out)
[02:00] *** phuzion has joined #warrior
[02:00] *** GLaDOS has joined #warrior
[02:00] *** svchfoo3 sets mode: +o GLaDOS
[02:11] *** Coderjoe has quit IRC (hub.se irc.efnet.pl)
[02:13] *** Coderjoe_ has joined #warrior
[02:25] *** JesseW has joined #warrior
[03:02] *** midas has quit IRC (Read error: Operation timed out)
[03:02] *** midas has joined #warrior
[06:52] *** JetBalsa has quit IRC (Ping timeout: 311 seconds)
[07:12] *** phuzion has quit IRC (Remote host closed the connection)
[07:12] *** phuzion has joined #warrior
[07:27] *** cechk01 has quit IRC (Read error: Connection reset by peer)
[07:35] *** JesseW has quit IRC (Leaving.)
[13:40] *** nertzy has joined #warrior
[14:22] *** nertzy has quit IRC (This computer has gone to sleep)
[17:53] *** JesseW has joined #warrior
[18:29] *** JesseW has quit IRC (Leaving.)
[19:22] *** JesseW has joined #warrior
[19:39] *** toad2 has joined #warrior
[19:43] *** toad1 has quit IRC (Read error: Operation timed out)
[20:54] *** Coderjoe_ has quit IRC (Read error: Operation timed out)
[20:55] *** Coderjoe has joined #warrior
[21:08] <Coderjoe> How difficult would it be to add the ability to have the "team choice" option be like a list, and have it start at the top and move down if the top one is throttled?
[21:09] <Coderjoe> like, if it gets throttle responses for a lengthy time
[21:15] <JesseW> Coderjoe: that was my first suggestion/thought when I arrived, too.
[21:15] <JesseW> I haven't taken the time to code it up (or even understand the Warrior code enough to accurately estimate it), but I still think it's a good idea.
[21:18] <Coderjoe> I've poked around in the code a bit, but it has been awhile. (no commits, though)
[21:56] *** JesseW has quit IRC (Leaving.)
[22:02] *** JesseW has joined #warrior
[23:07] *** nertzy has joined #warrior
[23:49] *** nertzy has quit IRC (This computer has gone to sleep)