wxMUD is a MUD client written with the wxWidgets GUI library to support many platforms (win32, POSIX, etc) with native speed. Currently it supports ANSI colors, multiple connections, MCCP, MSP, full MXP specification, advanced pattern matching and more.
First, I'm not a 'tester' but a mud enthusiast with some programming experience. My review of this Alpha release. First run, upon connect, the window is -very- small, should default to 640x480 or bigger. Does send terminal type as wxmud A couple of looks in game, and it crashed Relogged in to my mud... Checked MCCP, which was working Colors aren't working (yet?) MXP is enabled server side, but menu items (where they work in ahem, another client) do not appear to be functioning Right click reaches the wxmud system menu Changing the default color doesn't change it immediately, have to left click the screen Appears to have support for MCCP... and CMud protocol? Appears to be -some- input lag, which I find quite noticable Setting in game terminal type to 'network' it is supposed to negotiate terminal options, but doesn't enable colors or mxp Setting in game terminal type to 'ansi' enables colors and disables MCCP Going through various in game terminal types does NOT enable mxp in any setting Settings versus RightClick/Edit on the characters in Character selection is counter intuitive Overall, not a bad start. According to the web page, development is stalled due to real life issues of developers, but I see plenty of minor changes to code in svn updates. The client has potential, but still has a lot of elbow work needed to get it into shape. How I built my package... Obtained 996 (latest) via SVN. Converted workspace to VS2008 (9.0) Obtained and built wxWindows 2.8.10 Release, latest stable Built fl contrib project from wxWindows in Release mode Obtained binary distribution of Audiere 1.9.4, latest stable Used existing Pytion 2.6 x86 install Set project to Release mode Updated library, rc, includes, etc to account for different versions and locations Build succeeds Right to character selection! Do -not- convert to VS2008 format and attempt to build the Debug version. The manifest will fail, with the error: Error 1 fatal error CVT1100: duplicate resource. type:MANIFEST The only means to correct the error is to not embed the manifest Downside is, you can't run a debug exe built without the manifest The workaround is to build Release mode