5 Commits

Author	SHA1	Message	Date
mattsc	8689543d9a	Lua dummy engine: do not load debug_ai functions ... Besides them being unnecessary, a warning message is otherwise also displayed when external CAs are used and the game is not in debug mode.	2013-10-30 18:23:48 -07:00
mattsc	d5b994c0bb	Lua AI: make persistent data variable work with external CAs ... It was previously being set correctly by the engine, but was not accessible from the Lua AI.	2013-10-23 18:39:26 -07:00
mattsc	78f753e4dc	Revert "LuaAI: (1) persistent storage mechanism now available and working properly (2) old/incomplete mechanism not removed, subject to future deprecation" ... This reverts commit 754f2c2b3d5e4645453bc4a129e9c7f92f1390c0.	2013-05-13 13:15:22 -07:00
Dmitry K	754f2c2b3d	LuaAI: (1) persistent storage mechanism now available and working properly (2) old/incomplete mechanism not removed, subject to future deprecation	2013-05-12 01:12:45 +03:00
Dmitry Kovalenko	b207a1b1ca	LuaAI: the need to define an engine is now deprecated. ... All CAs can be store in external .lua files. If the scenario config lacks an [engine] tag for the Lua AI engine, but still tries to use CA with engine=lua, a dummy engine will be automatically generated, providing the needed functionality	2012-06-12 12:36:06 +00:00