Two new releases in the usual places.
1.8.0p10 is nearly all bugfixes, and highly recommended. The most important fix is a double-evaluation bug in sql(). As a bonus, the fix allows for row and field separators to more than one character.
1.8.1p5 includes those bugfixes as well as a fix for a 1.8.1-specific crash bug, and several feature improvements, including the nsearch() family of functions, @list/locks, two new @search classes, and other feature and portability enhancements.
1.8.1p5 introduces one incompatibility: @attrib/access now requires a space-separated list of full flag n
This is the formal lesson plan I submitted to my administrator. It's probably worth noting I've spoken at length with our math teacher, who is very curious about this. I've also connected with parents and gotten their permission.
The conversation and issues raised with the wizcore on the MUSH is worth an entry of it's own!
Getting to Z. Text-based multiplayer games and the 3-dimensional cartesian coordinate plane.
This lesson is designed for grades 7 and 8 (ages 13 and 14). This lesson is currently designed for small groups (no more than 5 students).
This lesson is designed to last 2 months, meeting once a week for about 40 minutes.
For a few years, I have been increasingly interested in how COTS (commercial, off the shelf games) can be successfully used in the education space.
For a basic introduction to games and education please click here. This covers a teachers perspective of the games in education movement.
As a long time fan of text-based games, bringing a MUSH into my classroom seems a logical and natural progression of my interest in games in education.
This is an introduction to a multi-part series in which I hope to detail my successes and challenges using a Star Trek MUSH to help 8th graders (14 years old) understand XY and Z on a cartesian coordinate plane.
Two new Penn releases, in the usual place. 1.8.0p9 is just portability tweaks (for amd64 and installations with openssl 0.9.8)
1.8.1p4 provides several useful changes and features. Errors in matching switches to commands are ignored when the command is hook/ignored or hook/overriden, so you can now override a built-in command and provide your own switches. The @mailfilter attribute allows for automated filing of incoming @mail. New @prompt/@nsprompt commands allow creating "prompts" for clients that support them (tf).
There are also several new functions including: namegrab, namegraball, t
Take a look at the new Wiki and make your mark. It's not just about TinyMUX.
Answering detailed questions on a regular basis? Rereading parts of the code that you just looked at 3 months ago? Need to spend 45 minutes to elaborate on an important point to answer a question, but you don't have 45 minutes to spare? Studying an unfamiliar codebase to nail down a behavior the help files left ambiguous? A Wiki is the answer.
Already, it has paid dividends to me by keeping conversations short and efficient. Already, it has enabled information to flow sideways around me instead of through me. Already, the answers there are typically fuller than the answers I could afford to retype in 45 minutes.
Well, the recent 1.8.1p2 release revealed that several important Configure units from 1.7.7 were missing in the 1.8.x series, including the one for detecting mysql. These new releases fix Configure, and are highly recommended.
PennMUSH 1.8.1p2 has been released in the usual place. This release contains several minor improvements and bugfixes, along with the new sortkey() function, and some portability improvements for 64-bit systems. It also incorporates all of the bugfixes in 1.8.0p7.
PennMUSH 1.8.0p7 has been released in the usual place. This release is entirely bugfixes, and is highly recommended.
We are in need of an econ system coder. Our wiz knows what is he wants, but needs someone to implement it. If you know of someone, we would most appreciative. Please contact me, firstname.lastname@example.org or email@example.com.
Ours is Fort Bloodshed, a Western MUSH and we've been up for nearly six years. My thanks in advance.
Further proof of the value of reality testing for code comes in the form of PennMUSH 1.8.1p1, now available in the usual place, which fixes a problem in the new attribute setting code that made it possible to set attributes "internal", and thus make them inaccessible.
If you have made an object's attribute internal by mistake, there are two ways to fix the problem:
- A wizard can use @attrib/access/retroactive to reset the permissions on all attributes of that name (possibly followed by @attrib/delete or @shutdown/reboot if you don't want those permissions to continue to apply to new attributes).