<title>James' MOOP Site</title>

<title>James' MOOP Site</title>
</head>
<body>
<h1>James' MOOP Site</h1>
<div id="breadcrumb">
<a href="../">Home Page</a> > Moop Site
</div>
<h2>Multi User Domain Object-Oriented Pythonic</h2>
<div id="page">

<div id="content">
<p>Welcome to my page about the MOOP codebase and my MOOP-based project. MOOP is a MOO written in <a href="http://www.python.org/">Python</a>; a MOO is an object-oriented MUD; a MUD is a multi-user dungeon/domain. In order to add functionality to a traditional MUD, a server restart is required. However, in a MOO, all code (except for the very basic code to get the thing running) is accessable / editable from within the MOO.</p>
<p>This is where I will post my notes and files concerning my experieces with MOOP. I can be contacted at <a href="mailto:[email protected]">[email protected]</a>. Please be sure to include "[moop]" in the subject header.</p>
<p>Any hardcode enhancements that I make will be submitted back to the maintainers for possible inclusion in an upcoming release. Softcode will only be available here. Softcode will only be submitted to the maintainers if I deem a specific snippet widely useful (e.g., <a href="http://groups.yahoo.com/group/moop-imps/message/251">my new in-game editor</a>).</p>
<p>I also hope to have a running game up within the next couple of months. I'm still working on code enhancement while I develop a theme. Watch this space for more information.</p>
<h4>My Links:</h4>
<ul>
<li><a href="http://moop.sourceforge.net/">MOOP Home Page</a></li>
<li><a href="http://groups.yahoo.com/group/moop-imps/">moop-imps group at Yahoo Groups</a></li>
</ul>
<h4>My Features & Enhancements:</h4>
<ul>
<li><b>Password Entry Suppression</b>: Complete. See below for hardcode patch.</li>
<li><b>New In-Game Editor</b>: Complete and slated to be included in the next release. See below for hardcode patch and softcode bootstrap file.</li>
<li><b>ANSI Colorization</b>: I am working on a way of adding ANSI colorization easily to output. The player should be able to setup whether he/she wants it on.</li>
<li><b>In-Game Help Editing</b>: Complete. See below for hardcode patch, softcode bootstrap, and help entries.</li>
</ul>
<h4>My Files:</h4>
<ul>
<li><a href="moop2.2.tgz">MOOP 2.2 Distribution</a></li>
<li><a href="password.patch">Password patch</a> - patches moopsock.py to use TELNET option codes to properly suppress password echoing</li>
<li>New Editor - "ed" style editor (see bootstrap file for implementation)
<ul>
<li><a href="neweditor.patch">Source patch</a> - patches moop.py to (1) add an additional property to all users to track current line and (2) enable editing of simple string properties</li>
<li><a href="neweditor.txt">Bootstrap file</a> - adds new function "editor" under current user which will be called as the preferred editor by @edit</li>
</ul></li>
<li>In-Game Help Editing
<ul>
<li><a href="moophelp.patch">Source patch</a> - patches moop.py and moophelp.py to enable access to help database functions within a running MOOP</li>
<li><a href="moophelp-code.txt">Bootstrap file</a> - adds new object under current user with replacement printHelp function for $user and new functions and commands for adding and deleting help entries (be sure the user is using the original MOOP editor, not the new one)</li>
<li><a href="moophelp-help.txt">Help import file</a> - adds new help entries explaining the new commands</li>
</ul>
</li>
</ul>

</div>
</div>