AI:GameInferences - Revision history

Paulomorfeo: Section moved somewhere else

2014-10-22T22:24:59Z

Section moved somewhere else

← Older revision		Revision as of 23:24, 22 October 2014
Line 64:		Line 64:
	TODO<br>		TODO<br>
	http://springrts.com/phpbb/viewtopic.php?f=15&t=32665		http://springrts.com/phpbb/viewtopic.php?f=15&t=32665

	~~=How interface commands correlate to the source code of the engine=~~
	~~Chances are you'll have doubts about what exactly does command X(), Y() or Z(). Asking in the AI forum is a good way to clarify. The most reliable is probably to look at the source code:<br>~~
	~~https://github.com/spring/spring/blob/develop/rts/ExternalAI/AICallback.h<br>~~
	~~https://github.com/spring/spring/blob/develop/rts/ExternalAI/AICallback.cpp<br>~~
	~~TODO~~

	[[Category: AI Dev]]		[[Category: AI Dev]]

Paulomorfeo at 23:41, 19 October 2014

2014-10-19T23:41:44Z

← Older revision		Revision as of 00:41, 20 October 2014
Line 70:		Line 70:
	https://github.com/spring/spring/blob/develop/rts/ExternalAI/AICallback.cpp<br>		https://github.com/spring/spring/blob/develop/rts/ExternalAI/AICallback.cpp<br>
	TODO		TODO

			[[Category: AI Dev]]

Paulomorfeo at 23:35, 19 October 2014

2014-10-19T23:35:02Z

← Older revision		Revision as of 00:35, 20 October 2014
Line 64:		Line 64:
	TODO<br>		TODO<br>
	http://springrts.com/phpbb/viewtopic.php?f=15&t=32665		http://springrts.com/phpbb/viewtopic.php?f=15&t=32665

			=How interface commands correlate to the source code of the engine=
			Chances are you'll have doubts about what exactly does command X(), Y() or Z(). Asking in the AI forum is a good way to clarify. The most reliable is probably to look at the source code:<br>
			https://github.com/spring/spring/blob/develop/rts/ExternalAI/AICallback.h<br>
			https://github.com/spring/spring/blob/develop/rts/ExternalAI/AICallback.cpp<br>
			TODO

Paulomorfeo: Wiki TODO

2014-10-19T23:23:37Z

Wiki TODO

← Older revision		Revision as of 00:23, 20 October 2014
Line 59:		Line 59:
	<br>		<br>
	Example: if the AI starts top left, at position (250; 250), it can make a weak assumption that the opponent will have started roughly at (MaxX-250; MaxZ-250).		Example: if the AI starts top left, at position (250; 250), it can make a weak assumption that the opponent will have started roughly at (MaxX-250; MaxZ-250).

			=Infer map traversability=
			How to infer where in the map each unit can pass through. Usually a submarine won't be able to go inland and a tank won't be able to climb mountains.<br>
			TODO<br>
			http://springrts.com/phpbb/viewtopic.php?f=15&t=32665

Paulomorfeo: /* Parse the startup script */

2014-10-19T23:18:36Z

Parse the startup script

← Older revision		Revision as of 00:18, 20 October 2014
Line 30:		Line 30:

	==Parse the startup script==		==Parse the startup script==
	The lobbies create an instruction script that is passed ~~as a parameter~~ when the lobby invokes ~~the executable for SpringRTS~~. On start, the SpringRTS engine will then parse that script for instructions on what ~~mod/game~~ to load, ~~what maps to load~~, and which starting positions to use. In Linux, that script ~~will typically~~ be in: ~/.config/spring/script.txt.<br>		The lobbies create an instruction script that is passed to SpringRTS when the lobby invokes it. On start, the SpringRTS engine will then parse that script for instructions on what maps to load, etc., and which starting positions to use. In Linux, that script should be in: ~/.config/spring/script.txt.<br>
	<br>		<br>
	In the startup script you can find parameters like:		In the startup script you can find parameters like:

Paulomorfeo: /* Enable cheats */

2014-10-19T23:15:48Z

Enable cheats

← Older revision		Revision as of 00:15, 20 October 2014
Line 15:		Line 15:

	==Enable cheats==		==Enable cheats==
	The Java OOInterface allows the enabling and disabling of cheats (not sure about the other interfaces - someone update this). After cheating is enable, querying ~~the Interface~~ for all ~~opponent~~'s units will respond with all ~~enemies~~ even if they are out of sight or radar.<br>		The Java OOInterface allows the enabling and disabling of cheats (not sure about the other interfaces - someone update this). After cheating is enable, querying for all opponents' units will respond with all enemy units even if they are out of sight or radar.<br>
	<code><pre>		<code><pre>
	Cheats cheats = _OOAICallback.getCheats();		Cheats cheats = _OOAICallback.getCheats();
	cheats.setEnabled (true); //Enables cheats and sends ~~the player~~ a warning ~~that~~ the AI is cheating.		cheats.setEnabled (true); //Enables cheats and sends a message to all players warning the AI is cheating.
	cheats.setEventsEnabled (true); //Enables this AI ~~player~~ receiving events for also the other player, like the "unitFinished" ~~events~~.		cheats.setEventsEnabled (true); //Enables this AI receiving events for also the other player, like the "unitFinished" event.
	</pre></code>		</pre></code>
	<br>		<br>

Paulomorfeo: /* Description */

2014-10-19T23:12:40Z

Description

← Older revision		Revision as of 00:12, 20 October 2014
Line 2:		Line 2:

	==Description==		==Description==
	This page describes how to infer (derive logical conclusions from permisses) some useful information to get started ~~with behaving intelligentely~~. For example: try to infer where the opponent might have started.		This page describes how to infer (derive logical conclusions from permisses) some useful information to get started. For example: try to infer where the opponent might have started.

	=Infer spawn positions=		=Infer spawn positions=

Paulomorfeo: Inception

2014-10-19T23:11:32Z

Inception

New page

=Useful inferences derivable from the game's data=

==Description==
This page describes how to infer (derive logical conclusions from permisses) some useful information to get started with behaving intelligentely. For example: try to infer where the opponent might have started.

=Infer spawn positions=
An important first step right at the start of the game is to infer where the opponent(s) might have started. 
A forum thread about it: http://springrts.com/phpbb/viewtopic.php?f=15&t=32662 
 
There are a few methods of varying reliability but, unfortunately, none appears to be absolutely reliable:
* '''Enable cheats, even if only temporarily''' 
* '''Parse the startup script''' 
* '''Try to parse the map's raw data files''' 
* '''Assume symetric starting positions''' 

==Enable cheats==
The Java OOInterface allows the enabling and disabling of cheats (not sure about the other interfaces - someone update this). After cheating is enable, querying the Interface for all opponent's units will respond with all enemies even if they are out of sight or radar. 
<code><pre>
Cheats cheats = _OOAICallback.getCheats();
cheats.setEnabled (true); //Enables cheats and sends the player a warning that the AI is cheating.
cheats.setEventsEnabled (true); //Enables this AI player receiving events for also the other player, like the "unitFinished" events.
</pre></code>
 
Note - at the very beggining of the game (as in frame 0) the enemy might not yet have spawned (your initial unit might have spawned first). It's necessary to wait a few frames before trying to get this info reliably. (SpringRTS runs at 30 simulation steps per second) 
 
Note - this method does not work in all conditions. As far as I've read somewhere, cheating will only work when the AI is playing someone in the same host machine and, if any cheating is done with someone else in the game, it will desync the running simulation between the running machines. There is a method that can be used to query that:
<code><pre>
bool whetherCheatingWillDesyncTheGame = cheats.isOnlyPassive();
</pre></code>

==Parse the startup script==
The lobbies create an instruction script that is passed as a parameter when the lobby invokes the executable for SpringRTS. On start, the SpringRTS engine will then parse that script for instructions on what mod/game to load, what maps to load, and which starting positions to use. In Linux, that script will typically be in: ~/.config/spring/script.txt. 
 
In the startup script you can find parameters like:
<code><pre>
startpostype=3;

[TEAM0]
{
StartPosX=284;
StartPosZ=256;
}
</pre></code>
See the source code for a mapping of what each startpostype means: https://github.com/spring/spring/blob/64733de8b60dfba3533ed2374cc426c2bfb6addb/rts/Game/GameSetup.h#L65 
 
If "choose in game" option was chosen, the script should have a definition of a rectangle of where each player could have chosen its start position:
<code><pre>
startrecttop
startrectbottom
startrectleft
startrectright
</pre></code>

==Try to parse the map's raw data files==
According to user Silentwings, some maps have a mapinfo.lua specifications file with the information on the starting positions on the map. However, not all maps have that file, and each mod/game can override that behaviour anyway.

==Assume symetric starting positions==
As a final last resort, a weak assumption can be made that in a 1v1 match the opponent will start in the symetrical opposite position of the map. 
 
Example: if the AI starts top left, at position (250; 250), it can make a weak assumption that the opponent will have started roughly at (MaxX-250; MaxZ-250).