Difference between revisions of "Stacked-a Condition"

From AgentCubes
Jump to navigation Jump to search
imported>Mike
imported>Mike
Line 1: Line 1:
[[image:Stacked a.png|150px]]
+
[[image:Stacked a.png|200px]]
  
 
<table cellpadding="10" cellspacing="0" border="0" width="100%">
 
<table cellpadding="10" cellspacing="0" border="0" width="100%">

Revision as of 22:09, 17 April 2012

Stacked a.png

Definition: The Stacked-a condition checks if the agent's location in relation to the agent specified by the agent class matches the adjacency choice; that is, the condition checks whether the agent is immediately above, somewhere above, immediately below, somewhere below, or above or below the agent that is specified by the class. If the agent is adjacent to the chosen class as specified with the adjacency parameter, the condition is true. Otherwise, the condition is false.

The difference between the Stacked and the Stacked-A conditions is that the Stacked condition checks for a specific shape/look and is true only if the agent has that exact depiction, whereas Stacked-A checks for any depiction of the given agent and is true regardless of how the agent looks.

Parameters: adjacency, shape
Example: The Frog agent in the Frogger game checks to see if it is stacked immediately on above a tunnel, no matter what the tunnel looks like, in which case it gives a message that walking over the tunnel to cross the road is not permitted (it's cheating!), erases the Frog, and stops the simulation. The same happens when the user tries to navigate the Frog on top of a Log Maker. 500px