Create initial orphan branch with clean history

Author: TehomCD

.gitignore

@@ -0,0 +1,76 @@
+*.py[cod]
+*.py~
+
+# cloud 9 temp files
+*c9_invoke_*.py
+
+# C extensions
+*.so
+
+# Packages
+*.egg
+*.egg-info
+dist
+build
+eggs
+parts
+var
+sdist
+develop-eggs
+.installed.cfg
+lib
+lib64
+__pycache__
+
+# Other
+*.swp
+*.log
+*.txt
+*.pid
+*.restart
+*.db3*
+
+# Installation-specific. 
+# For group efforts, comment out some or all of these.
+server/conf/secret_settings.py
+server/logs/*.log.*
+server/logs/*
+# web/static/*
+web/media/*
+
+# Installer logs
+pip-log.txt
+
+# Unit test / coverage reports
+.coverage
+.tox
+nosetests.xml
+
+# Translations
+*.mo
+
+# Mr Developer
+.mr.developer.cfg
+.project
+.pydevproject
+
+# PyCharm config
+.idea
+
+# nano .save files
+*.save
+
+# virtualenv
+venv/
+
+# generated map files
+world/dominion/map/arxmap_generated.png
+world/dominion/map/arxmap_imagemap.html
+world/dominion/map/arxmap_imagesize.cfg
+*.db3-shm
+*.db3-wal
+
+# generated fealty graph
+world/dominion/fealty/fealty_graph.png
+config.env
+settings.ini

README.md

@@ -0,0 +1,22 @@
+Arx is a game based on Evennia. I decided to make an orphan branch open source to let people 
+use code as they like for their own games and contribute if they like. In general we should 
+be compatible with any given Evennia branch, though I tend to stay on master and occasionally 
+make a branch to cherry-pick additions from develop.
+
+The basic requirements  are added in the different setup files. Evennia sets the django settings
+environmental variable at startup and looks specifically in the server/conf/ directory, so specify 
+`--settings=foo_settings` where `foo_settings` is a settings file in the server/conf/ directory. 
+The default will use production_settings unless otherwise specified.
+
+Some django packages aren't compatible with Evennia due to clashes in middleware. Silk,
+for example, will throw errors from its middleware whenever an in-game script runs.
+
+Evennia resources:
+
+From here on you might want to look at one of the beginner tutorials:
+http://github.com/evennia/evennia/wiki/Tutorials.
+
+Evennia's documentation is here:
+https://github.com/evennia/evennia/wiki.
+
+Enjoy!

__init__.py

@@ -0,0 +1,6 @@
+"""
+This sub-package holds the template for creating a new game folder.
+The new game folder (when running evennia --init) is a copy of this
+folder.
+
+"""

commands/README.md

@@ -0,0 +1,14 @@
+# commands/
+
+This folder holds modules for implementing one's own commands and
+command sets. All the modules' classes are essentially empty and just
+imports the default implementations from Evennia; so adding anything
+to them will start overloading the defaults. 
+
+You can change the organisation of this directory as you see fit, just
+remember that if you change any of the default command set classes'
+locations, you need to add the appropriate paths to
+`server/conf/settings.py` so that Evennia knows where to find them.
+Also remember that if you create new sub directories you must put
+(optionally empty) `__init__.py` files in there so that Python can
+find your modules.

commands/__init__.py

@@ -0,0 +1,4 @@
+# -*- coding: utf-8 -*-
+
+__all__ = ('death', 'home', 'market', 'rumor', 'sleep', 'standard',
+           'starting_gear')