I realize I'm the FNG here but looking through the code I'm seeing a lot of string1 = "blah" + something + "blah" + something;

I'm not trying to stir up some kind of shitstorm but I've seen that kind of code be a huge resource hog when you start scaling up in concurrent users.  Nothing will bring down a CPU/RAM like C# string manipulation.  I humbly suggest the use of String.Format() instead.  It uses the StringBuilder underneath which does create another Object but overall you use less memory and resource than the + string concat.  It will save memory and I think it makes the code more readable.  Not to mention this makes your application orders of magnitude easier to localize and read strings from a string table location in a resource file.

Just something to think about.

We discussed localization amongst other things here.  Localization is not, and IMO should not be, on our v1 roadmap.  In summary, my points of note are:

* Proper generic localization of a MUD would be a massive undertaking.

* We need to keep a sane scope to make it through v1.

* We don't have any bilingual team members who are begging to implement this functionality all the way through.  Our stance may certainly change if something like that changes.

* Small loc-friendly changes are fine.  However, anything like pulling the text out of their code context and into separate resource files or whatnot would be quite detrimental at this time.

I could definitely get behind moving towards a standard of using string.Format over '+' or string.Concat.