mirror of
https://github.com/evennia/evennia.git
synced 2026-03-20 14:56:30 +01:00
Python MUD/MUX/MUSH/MU* development system
http://www.evennia.com
baseddjangoenginegame-developmentgame-enginegamedevhacktoberfestmoomudmultiplayermushmuxpythontexttext-basedtext-based-adventuretwistedwebclientwebserver
ad009e20ab
---------------
- Checks for NULL description on objects- if Null, it doesn't print the extra line any more.
- Made the checks for contents a little less ambiguous
cmdhandler.py
--------------
- Added new method 'parse_command' which takes a command string and tries to break it up based on common command parsing rules. Mostly complete, but could use some work on the edge cases. Check out the docstring on the function- I tried to make it fairly well documented.
- Changed the check for 'non-standard characters' to just return, rather than throw an Exception. Not sure if this causes any issues, but I noticed that when you hit enter without entering a command it would trigger this code. Now it just fails silently.
- The handle function now calls the parse_command function now and stores the results in parsed_input['parsed_command']. This then gets put into cdat['uinput'] at the end of handle() like before. The old data in parsed_input is still there, this is just a new field.
- Added cdat['raw_input'] to pass the full, untouched command string on. This is also stored in parsed_input['parsed_command']['raw_command'] so not sure fi this is necessary any longer, probably not.
cmdtable.py
------------
- Just cleaned it up a bit and straightened out the columns after changing 3-4 space indentation.
apps/objects/models.py
-----------------------
- set_description now sets the description attribute to 'None' (or Null in the db) when given a blank description. This is used for the change mentioned above in basicobject.py
- get_description now returns None if self.description is None
- used defines_global in the comparison methods like is_player
functions_db.py
----------------
- Changed import defines_global as defines_global to just 'import defines_global'- wasn't sure why this was this way, if I broke something (I didn't seem to) let me know.
- renamed player_search to player_name_search. Removed the use of local_and_global_search inside of it. local_and_global_search now calls it when it receives a search_string that starts with *.
- alias_search now only looks at attributes with attr_name == ALIAS. It used to just look at attr_value, which could match anything, it seemed.
- added 'dbref_search'
- local_and_global_search changes:
- Now uses dbref_search & player_search if the string starts with "#" or "*" respectively
- Changed when it uses dbref_search to whenever the search_string is a dbref. It used to check that it was a dbref, and that search_contents & search_location were set, but I *believe* in most MU*'s when you supply a dbref it never fails to find the object.
commands/unloggedin.py
-----------------------
- removed hardcoded object type #'s and started using defines_global instead
- when creating a new account, made sure that no object with an alias matching the player name requested exists. This is behavior from TinyMUSH, and I think most MUSHs follow this, but if not this is easy enough to change back.
commands/general.py
--------------------
- Rewrote cmd_page:
- New Features
- Page by dbref
- Page multiple people
- pose (:) and no space pose (;) pages
- When someone hits page without a target or data, it now will tell the player who they last paged, or say they haven't paged anyone if they don't have a LASTPAGED
- uses parse_command, made it a lot easier to work through the extra functionality added above
- When there are multiple words in a page target, it first tries to find a player that matches the entire string. If that fails, then it goes through each word, assuming each is a separate target, and works out paging them.
commands/objmanip.py
---------------------
- I started to muck with cmd_name & cmd_page, but decided to hold off for now. Largely, if everyone is cool with the idea that names & aliases should be totally unique, then we need to go ahead and re-write these. I'll do that if everyone is cool with it.
|
||
|---|---|---|
| apps | ||
| commands | ||
| doxygen | ||
| media/css | ||
| reload | ||
| scripts | ||
| webtemplates/prosimii | ||
| __init__.py | ||
| ABOUT | ||
| ansi.py | ||
| cmdhandler.py | ||
| cmdtable.py | ||
| defines_global.py | ||
| evennia.vhost.apache | ||
| events.py | ||
| functions_comsys.py | ||
| functions_db.py | ||
| functions_general.py | ||
| functions_help.py | ||
| gameconf.py | ||
| initial_setup.py | ||
| INSTALL | ||
| LICENSE | ||
| manage.py | ||
| mixins.py | ||
| README | ||
| scheduler.py | ||
| scripthandler.py | ||
| server.py | ||
| session.py | ||
| session_mgr.py | ||
| settings.py.dist | ||
| startup.bat | ||
| startup.sh | ||
| TODO | ||
| urls.py | ||
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 * Evennia Test Game evennia.com port 4000