Howdy, folks. At some point in the future, I'm sure I'll actually get around to posting some interesting code here for you to look at, use, whatever. Probably.

PHP

I found myself wanting a super simple, lightweight templating system. Something like Perl's Template Toolkit. This is my attempt at it. At some point, I want to expand this to a super lightweight framework.

MOO code

Does anyone still use MOOs any more? I honestly have no idea. I spent a lot of time back in the day writing various code for them. Here's some of the good stuff. (NOTE: If you're actually going to use any of this, look it over first. I tried to make each file completely independent, but there might be some stuff that can cause problems.)

• traceback.moo This sets up some $prog_options that, when set, let you see the offending lines of code in the error stack when a traceback shows.
• exitless.moo Exitless rooms were my solution to not wanting room exits to be separate objects. I've never liked the idea of littering the database with hundreds of objects that do nothing but say "this room leads to this other room". This also has a second room parent, which is where I put all of my custom room code so that it doesn't get lost in all the $room basic code.
• channel.moo This is code for a MUSH-style channel system. There isn't a lot of control on these kinds of channels. Players can define them pretty much at will. Prefixing a channel name with * will keep non-wizards from adding it, though. This one definitely needs some editing. We had a non-wizard staff group, and there's some stuff that references that in it, and a specific object number for a help desk object. There's also a my_huh that needs to get inserted into the $player huh stack. We used a $player2 parent class, but you can adapt it into the stack somewhere else, if you don't want another parent class in the standard hierarchy.