Yes. You read right. I've been working on a router in my spare time. Some of you no doubt know this, others may not. I've arrived at a stage where it can be tested more widely than just my group of test connections.

First off, this router is *NOT* considered production and should not be used in place of your current connection to the main one. If you wish to join in helping to test it, it's highly advisable you use a secondary port so as not to disturb your main game in case it crashes you.

Secondly, it does not support everything yet. Of note, channel-admin packets are not processed, channel exclusion lists are not yet supported, and private channels will not keep unwanted members off of them.

And finally, privacy. Expect none. The router is set to log all packets in and out to monitor for anomalies and for reasons behind crashes. Don't send anything you don't want me to see via tells and such. This is not a green light to abuse things. If you are found to be abusing the test, you will be banned from connecting. Crashes as the result of normal use are to be expected though.

So if you're willing to give this a try, you can change your I3 configuration to point to the following:

# The router information. Currently only one.
# Information below this point cannot be edited online.
router i3.arthmoor.com~
port 9900
routername *arthmoor~

Users of the Diku I3 client I distribute can paste that directly into their configs. Other clients will just have to cope

LP Muds are welcome to participate as well, though not all services you might be used to having are being supported yet.

Recommend that those using the Diku I3 client upgrade to version 2.25 since there is a great deal of data sent at initial connection that might overflow the buffers in older code.

Known issue:

Mudlist packets don't seem to be getting delivered in their entirety. There should be 146+ muds delivered after connection. For some reason most connections are only able to recieve between 120 and 135 and I haven't solved why.

AHA! Found the mudlist packet issue. Silly logic mistake. It was skipping counts, and as a result wasn't delivering a full list. Now that this is out of the way, any further muds connecting that aren't getting a full list should let me know since that might be a socket buffer issue.