| 00:02.33 | *** join/#bzflag linuxclub (~linuxclub@62-101-126-217.fastres.net) |
| 00:08.34 | linuxclub | hi JB |
| 00:09.05 | JBdiGriz | hi |
| 00:09.44 | linuxclub | any news on your failing SDL? |
| 00:10.14 | JBdiGriz | ??? It's working so far, only a couple of small bugs. |
| 00:10.45 | Tupone | so no news then |
| 00:11.10 | JBdiGriz | I have been working on taxes and voting so far this weekend. |
| 00:11.36 | Tupone | ah OK |
| 00:12.35 | Tupone | do you know if learner is experiencing the same? |
| 00:12.45 | Tupone | brb |
| 00:13.26 | *** join/#bzflag Adam9` (adam@134.53.120.136) |
| 00:14.06 | Adam9` | anyone know what a communication error would mean when connecting to a bzflag server? |
| 00:14.29 | JBdiGriz | It might mean you lost a packet |
| 00:16.17 | Adam9` | hmm |
| 00:16.33 | Adam9` | the problem is that the server won't allow more than 1 person to join |
| 00:16.45 | Adam9` | after the first person, a comm. error is shown for everyone else |
| 00:17.40 | Adam9` | ok, maybe after the second person then |
| 00:17.49 | Adam9` | weird |
| 00:18.51 | *** join/#bzflag Death_Barrel (~Death@cs2427126-62.houston.rr.com) |