[camlorn]

I can get you a link, if you can't find it, or haven't already...it's actually really good. Outlines the entire language, from start to finish. Then it goes on and tells you everything you ever wanted to know about how the server works and what it wants from you (not for c coders, from the perspective of moo core writers). The last sections are what you want: info on what happens when someone connects, how to set out of band prefixes and stuff, how to fix the game if you can't connect via telnet, what the game needs to see for the world's most minimal core, etc. Basically, it's what I wish lpc drivers had.

You can find it through this page:

Along with a bunch of other documentation and servers and such. I should look at the moo environment again, and see if anyone's made the features I wanted yet...I thought it was pretty much not being updated anymore (I only really looked at stunt).

A thought for you: the name variable is really misleading in this case. Those values can be whatever you want. Obviously, there's a lot of standards and such for KaVir's stuff, but nothing says you *have* to always bind to a variable. It should, from what I remember from my looking about, be completely possible to implement this in moocode. You are computing a string to send to the client, that is all, and you're already doing that.

Note: the name I'm looking for may not be moocode...it's been a while.