Expert projects
Submitted by javelin on Thu, 2006-09-14 09:28.
This section includes challenges for expert softcoders. These typically reflect complex "systems-level" projects.
»
- Printer-friendly version
- Login or register to post comments

Click 

Accounting for everything...
This challenge is being presented in a somewhat vague format here, mostly because I haven't researched what all can/can't be done with reference thereto. So, I'll leave it up to those with more knowledge about what can/can't be done to contribute commentary or whatever, until such a point as this becomes a clearly defined challenge.
Basically, here's what I'm looking for (and yes, I'm looking for this for the WARPEDcore as a contrib module, if you're so inclined to write it with that in mind - which I strongly hope!)...
The end result should be a set of commands which use ONLY built-in features of Pennmush to retrieve and display as much "stuff" about one's game as possible. A simple example of one command would be to display the contents of the Master Room with relevant details about each item (e.g., flags, powers, locks, etc.). Another example of a possible command would be to display all of the config() options which deviate from the default installation (and ONLY those that deviate). Another example would be to display as much info about all of the @functions that have been added to the game (e.g., the object where the code resides, powers on the objects, etc.).
If you write something that requires a specific power (e.g., see_all) or admin flags (royalty or wizard), please include documentation about those requirements.
Likewise, if you write something which 'costs money' (e.g., uses the lsearch() family), please include documentation/notes about that, as well.
Basically, my objective is to determine 'the rest' of what the WARPEDcore should be doing, by first figuring out what Pennmush can already do (that is, the things that aren't already do-able with existing distro stuff, and would require the creation of more complex management items).
Once you get it written, I encourage you to submit it to the WARPEDcore collaborative book (located elsewhere on this website) for possible inclusion as an official module therein.