Some of you may recall a recent dbsave theme about ways to raise money for M*U*S*H. While this was, like most dbsaves, done in jest, our hosting costs are quite high - almost $600 a year.
For the last few years, the PennDevs have split the cost for Gaebolg - the machine which hosts M*U*S*H, the pennmush.org websites, and the devs' test games, among other things. However, with the economy being what it currently is, meeting these costs has become more difficult. Therefore, we'd like to invite donations from the community; if you're in a position to contribute any amount, and would like to do so, we'd be very grateful!
The PennMUSH development team is proud to announce the release of 1.8.5 patchlevel 0. As usual, lots of fixes, some new stuff, and, justifying the version bump, some major new changes in requirements to compile and run a PennMUSH (Formerly optional libraries are now mandatory.).
Changes below the cut.
Just wanted to share that I've open-sourced my latest little creation, a Sinatra web application designed to receive post-push POSTs from Github. On my latest MUSH project, we're using git and Github heavily, with multiple repositories for the game's code, softcode, etc, and this provides a handy way to not only keep the coders up to date on new pushes, but also keep everyone the game up to date on what's happening, even if they're not Git-savvy.
As a followup with Banana - I am now offering, for free, guest web accounts for anyone who would like the ability to offer a lightweight, web-based guest connection to their mush.
You can see an example here: http://client.pennmush.org/guest/bugmush - That's my development mush.
M*U*S*H and CrossroadsMUSH are also available. (But please note, you can only 'guest' to one mush at a time!)
Hey there, somehow, you've manage to find these series of articles on building on a mush. Some of these articles will be PennMush explicit (and marked as such), but there will still be various articles that'll help you in building in general.
These articles will cover good practices, and explain why they should be done as so. It'll give examples on how to use the various digging commands.
It'll cover the general guide lines on how to write a good descriptions.
Hopefully, I'll do a decent job of transcribing my experience of being a builder in order to help others in the future.
PennMUS 1.8.4p7 as been released, available from http://download.pennmush.org/Source. Lots of important bug fixes and new stuff.
Let me briefly cover two additional topics on the matter. One's about how to proceed once some ideas have trickled in. One's on, more or less, what the protocol would do as I envision it (but not yet HOW). I strongly suggest not reading this post until after you've made your suggestion on the previous one, if you're planning to do that.
Huge disclaimer to start: Nothing may come of this.
If you can live with that, let me add a redeeming thingy: If I don't actually work on this at all, at least the data will be available for future reference.
So are you ready? Okay.. Given an implementation of a new protocol to do the sort of thing Pueblo does, but isn't Pueblo, what sort of things would you require? What sort of things would you suggest avoiding?