Softcode

Today I managed to finalize some ideas and get some work done on paper for my new character system that will become the backbone of Last Bastion MUSH. I took concepts from several systems I enjoy and think work well in this sort of environment and applied some new logic to them. I don't want to give away all of the concepts now, so I will hold off until things are more finalized, but I do intend to release the code eventually for wide distribution by anyone who likes the system. It will require SQL but I plan to build the table creation etc into the installer.

Looking for coder(s) who are willing to build a Jusenkyo curse system in softcode for PennMUSH.

I am looking for a good or at least easy to implement +nom system. Our current one depends on the SQL_Platform (@config/list net) being disabled, thus SQL() is disabled. I do wonder if this has been fixed since 2005?

We've attempted to enable it, it shows enabled, though it is not.

My thanks in advance.

In my last post, I mentioned working on queue process ids, and ways to manipulate individual queue entries. It's now checked into svn and being tested on M*U*S*H.

Credit first: Rhost did this a long time ago, and I'm basing what I'm doing on their help files.

The object of this challenge is to create a function system that uses a stopwatch style timer similar to standard wait() command.

However, it should be universal (Accepting any input for either of the styles of running the system shown below), cleanly repeatable in a looping fashion, and finish cleanly.

Thus, you should be able to do either:
---
Repeat '[pemit(%#,[time()])]' every 15 minutes for the next 2 hours, then stopping the loop cleanly.
---
or:
---
After running '@eval [setq(1,0)]'

Whenever I release code, I always make the help-files suitable for a hardcoded help/+help command added through mush.cnf. Lately, though, I've had several people ask me for copies of them suitable for a softcoded +help system, so I've written a little tool for converting them. You can use it for any helpfile - I've lightly tested it with a few off my site, and a couple out of the PennMUSH distro.

Keeping track of code and all the modifications that have been done to it is an important part of maintaining any large system. I cannot overstress the importance of using a revision management system like RCS or SCCS for both the server and all important MUSHcode systems you have. The ability to easily undo a change can save you days of painful bughunting.

Editor's note: Or CVS, or prcs, or svn...

As anyone who's read Amberyl's MUSH manual knows, there's much more to writing MUSHcode than @create. Large MUSHcoded systems like combat, economy, and dynamic space systems pose particular problems for MUSH Gods. These tips offer suggestions for tackling MUSHcode.

Editor's note: Many of these tips may be dated! MUSH servers have changed in several ways since these tips were first posted. Always doublecheck this information with someone knowledgeable about the server you're using!

Queue and CPU efficiency (Javelin)

Or, Calculating

The previous part looked at an ictime ufun / @function that can handle arbitrary dates with correct day of the week. Now to put that in a nice-looking calendar.

The model for ths is the cal program on unix/linux - a month calendar.

The first thing we want is for players to be able to type +cal and get the calendar for the current month, with the header that looks like this:

Mo Tu We Th Fr Sa Su