v1.3.1

This release is just two minor changes - updating the default "version" config to v1.3.0, and making the DEBUG flag in helpers.php false in order to protect new users.

Cheers!

v1.3.0 - No more mysql_!

Howdy! This release is a big one. We made a lot of significant changes than you can read about in the v1.3.0 portion of the changelog, but the main gist is this;

• All old mysql_ based DB functions depending on the mysql_ shim have been replaced with the new PDO-based DB functions
• Almost all the codebase has been refactored, more details in the changelog
• Content that's entered by users is now escaped on output
• Forms no longer die with errors and will instead (usually) show you the form again, with errors displayed
• Lots (but not all) of the repetitive code in the game has been replaced by easy-to-use helpers

This release should be compatible with most database setups still around, so feel free to just pull the repo down and use it!

As usual, report any issues or ideas to the Issues tab.

Cheers!

v1.2.0

Hey there! It's time for another release, which hopefully comes once a week; preferably every Thursday. If we can keep on that schedule, we should make great progress on making this game great again.

Anywho, this release brings about a bunch of security updates, especially in how passwords are handled and stored. We're also beginning to deprecate the charname user field and replacing it with username as we go.

I've started writing all relevant release changes into the changelog file, so give that a read if you're interested in all the details.

In the meantime, enjoy!

v1.1.11 "Revival"

This release presents to you a functional, mostly-unchanged version of the game as it was when Jamin left it! We've made a few nice modifications to it, including...

• A mysql_ shim so the game will actually work
• Updated and improved helper functions, such as the template parser
• A new config structure that's easier to use and more flexible
• Error-free operation!

This is still an unsafe build, simply because our content sanitization and password hashing are still infantile. We're working on some big framework changes before we address those issues, though, so just keep a lookout for it.