| 03:17.20 | *** join/#riftuidev fewyn (~fewyn@fewyn.net) |
| 03:17.21 | *** mode/#riftuidev [+v fewyn] by ChanServ |
| 05:45.03 | *** join/#riftuidev dolby (~dolby-wow@MMOI/Administrator/pdpc.silver.dolby) |
| 05:45.03 | *** mode/#riftuidev [+o dolby] by ChanServ |
| 05:49.09 | *** join/#riftuidev seebs_ (~seebs@home.seebs.net) |
| 05:49.09 | *** mode/#riftuidev [+o seebs_] by ChanServ |
| 07:21.18 | *** join/#riftuidev seebs (~seebs@home.seebs.net) |
| 07:21.18 | *** mode/#riftuidev [+o seebs] by ChanServ |
| 09:34.50 | Thorarin | Hmmz, there's an alarming increase in a specific error occurring in KaruulAlert.. A couple of days ago, the most common error was at 3% |
| 09:34.53 | Thorarin | Now 21% |
| 09:35.27 | Thorarin | I haven't noticed anything myself, there haven't been any major patches and there have been no new releases.. weird |
| 09:51.17 | Ivnedar | Unless there's been a post on how to track some mechanic that triggers a bug |
| 09:51.54 | Ivnedar | Not that I know of one, trying to think of a reason for a jump like that |
| 14:57.59 | *** join/#riftuidev seebs (~seebs@home.seebs.net) |
| 14:57.59 | *** mode/#riftuidev [+o seebs] by ChanServ |
| 17:00.59 | *** join/#riftuidev seebs (~seebs@home.seebs.net) |
| 17:00.59 | *** mode/#riftuidev [+o seebs] by ChanServ |
| 19:23.04 | *** join/#riftuidev Imhothar (miranda@ppp-93-104-190-8.dynamic.mnet-online.de) |
| 22:55.56 | *** join/#riftuidev Noshei (~quassel@c-24-9-171-99.hsd1.co.comcast.net) |