Griatch 4d9081d710 Various cleanups in the recent modifications, and improvements to how time is handled and displayed. ... . Griatch		2009-11-25 19:27:32 +00:00
..
__init__.py	Even more death and destruction. A lot more stuff moved to src/. A lot more bugs probably introduced.	2008-06-15 19:38:39 +00:00
batchprocess.py	* Implemented a non-persistent cache in src/cache.py. The cache is lost when restarting the server but it has the advantage of not hitting the database, and so is useful for implementing things that should be remembered over time but does not need to be persistently saved in the database at every point, like fast-updating combat systems, timers etc. Using the cache can substantially cut down on database access at the cost of memory comsumption. It is easiest accessed through the object model using normal dot notation. So to store a variable in volatile memory e.g. from your script parent, you can do things like self.scripted_obj.cache.myvariable = variable and be sure that later (unless there was a reboot) doing self.scripted_obj.cache.myvariable will return the value you stored there.	2009-11-01 15:12:38 +00:00
comsys.py	Many small but useful bug fixes in various modules.	2009-10-20 20:38:24 +00:00
general.py	Various cleanups in the recent modifications, and improvements to how time is handled and displayed.	2009-11-25 19:27:32 +00:00
imc2.py	Largely rewrote and refactored the help system.	2009-10-14 18:15:15 +00:00
info.py	Various cleanups in the recent modifications, and improvements to how time is handled and displayed.	2009-11-25 19:27:32 +00:00
irc.py	Largely rewrote and refactored the help system.	2009-10-14 18:15:15 +00:00
objmanip.py	* Implemented a non-persistent cache in src/cache.py. The cache is lost when restarting the server but it has the advantage of not hitting the database, and so is useful for implementing things that should be remembered over time but does not need to be persistently saved in the database at every point, like fast-updating combat systems, timers etc. Using the cache can substantially cut down on database access at the cost of memory comsumption. It is easiest accessed through the object model using normal dot notation. So to store a variable in volatile memory e.g. from your script parent, you can do things like self.scripted_obj.cache.myvariable = variable and be sure that later (unless there was a reboot) doing self.scripted_obj.cache.myvariable will return the value you stored there.	2009-11-01 15:12:38 +00:00
paging.py	Largely rewrote and refactored the help system.	2009-10-14 18:15:15 +00:00
parents.py	Largely rewrote and refactored the help system.	2009-10-14 18:15:15 +00:00
privileged.py	Added more stable events.	2009-11-18 20:10:35 +00:00
search.py	Largely rewrote and refactored the help system.	2009-10-14 18:15:15 +00:00
unloggedin.py	Largely rewrote and refactored the help system.	2009-10-14 18:15:15 +00:00