mirror of
https://github.com/evennia/evennia.git
synced 2026-03-22 15:56:30 +01:00
Python MUD/MUX/MUSH/MU* development system
http://www.evennia.com
baseddjangoenginegame-developmentgame-enginegamedevhacktoberfestmoomudmultiplayermushmuxpythontexttext-basedtext-based-adventuretwistedwebclientwebserver
1ea7e69821
OBS - there is a new data table (for the persistent cache) so you need to sync or restart with your database. * Persistent cache (pcache)- this works the same as the volatile cache, except it is regularly saved to disk and recovered upon restart. How often the pcache is backed up is set in preferences. This was heck of a tricky thing to get right due to the intricacies of pickle; for example it turns out there is a bug in cPickle, so only normal pickle works to store the cache objects. * Persistent events - this makes use of the pcache to re-load the scheduled events every reload. Only events with the property "persistent" will be saved this way (if not set, events will get lost upon reboot, just like now). All the main system events have been implemented as persistent events, including a new event to regularly save the pcache to disk. * In order to track persistent event timers across reboots, there is also a global "game time" defined now. This is saved in cache and counts seconds only when the server is running. Event timers are adjusted with an offset when restarting (otherwise they will be confused by the real time jumping forward after a downtime). There are also a small set of helpful routines in src/gametime.py to help convert from real time to game time (for easy creation of new events). * Various info commands have been updated to incoorporate the time stamp and the cache sync information. * There are a few test commands commented out in commands/general.py that I used for testing; I left them in if you want to test things quickly. It works here, but as always more people testing is needed. /Griatch |
||
|---|---|---|
| docs | ||
| game | ||
| src | ||
| tools | ||
| __init__.py | ||
| ABOUT | ||
| CODING_STYLE | ||
| INSTALL | ||
| LICENSE | ||
| README | ||
| sitecustomize.py | ||
| TODO | ||
About Evennia ------------- Evennia is a proof-of-concept MU* server that aims to provide a functional base for developers. While there are quite a few codebases that do the same (and very well in many cases), we are taking a unique spin on the problem. Some of our flagship features include (or will one day include): * Extensive web integration. * The ability to build/administer through a web browser. * Shared accounts between the website and the game. * Optional web-based character creation. * Extremely easy-to-manipulate SQL database back-end via Django (djangoproject.com) * Simple and easily extensible design. * Very granular permissions. Individual and group based. The essential points here are the web integration and the SQL backing via Django. The Django framework has database abstraction abilities that give us many features free, such as: * The codebase will run transparently on MySQL, SQLite, or Postgres * At the time of this document's writing, our SQL-backed application here contains 0 lines of SQL. Django's database abstraction layer is absolutely simple yet very powerful. * For any model we outline for the server's use, we have the ability to more or less automatically generate a web-based admin interface for it with two lines of code. This lets you Create, Update, or Delete entries. * On the web-based side of things, features such as automatic form validation, abstraction of sessions and cookies, and access to whatever game data you desire are all attractive. Support and Development ----------------------- Since we're so early in development, we really can't hope to offer much support. However, if you'd like to report bugs, make suggestions, or help with the code work, visit either or both of the following links: * Evennia Webpage http://evennia.com * Evennia Code Page http://code.evennia.com