To debug your behaviours use GameView.addLines() and GameView.addPoints() methods. Here you can see an example:

    public MOVE getMove(Game game, long timeDue) {    
    	//Show lines to PPills
	    int[] activePowerPills=game.getActivePowerPillsIndices();
	    for(int i=0;i<activePowerPills.length;i++)
	      GameView.addLines(game,Color.CYAN,game.getPacmanCurrentNodeIndex(),activePowerPills[i]);
	   
	    //Show way to ghosts
	    for(Constants.GHOST g: Constants.GHOST.values()) {
	    	int ghost = game.getGhostCurrentNodeIndex(g);
	        int mspacman = game.getPacmanCurrentNodeIndex();
	        if(game.getGhostLairTime(g)<=0)
	    		GameView.addPoints(game,colours[g.ordinal()],game.getShortestPath(ghost,mspacman));
	    }  
	    return allMoves[rnd.nextInt(allMoves.length)];
    }

The extension allows to implement, by a CLIPS program, the behaviour of the MsPacMan and the Ghosts. It includes a plugable graphical interface to inspect the facts, and example to debug rules.

• Input. Abstract class to encapsulate the input variables required for logic process. Subclasses must implement the abstract method parseInput(). The data should be prepared for the input variables of the .clp file, the objects templates with attributes slot. The variables are been offered in getFacts() method in a Collection<String> variable.
rules.clp. CLIPS file program, which has two blocks, the templeantes and the rules. In templates we define the input variables, the output variable (the action) and auxiliary variables. The logic that has to be applied it is defined by the rules and those are been described in the facts that have to converge so the rule can be executed.
• RuleEngine. This class manage the execution of the CLIPS program. It does the insertion of the facts to the application with the method assertFacts(Collection<String> facts) and the reset of the cases. Execute the CLIPS program with run(), waiting for finishing of the application of all posible rules. If someone asserts a solution, the method returns the action to release in the game.

The extension allows to implement Case-based reasoning (CBR) to define the behaviour of the MsPacMan and the Ghosts.

• Input. Abstract class to encapsulate the input variables contemplated for the state of the game. Subclasses must implement the abstract method parseInput() in which one must to configure/set the values of variables of description of the case. The data should prepare the input variables of the .clp file, the objects templates with attributes slot. It should have the same variables which are defined in the correspond Description class and it must be set in the the CBRQuery that returns in method getQuery().
• CachedLinearCaseBase. It can be find the cbr cases cached which improve the management efficient of getting the cases. There are 3 differents sets of cases, the working cases which are the ones applied in this game, the original cases which are the cases loaded from the CBR database, and the cases pending to remove, which are the ones that can add cases to eliminate them.
  In adition, when there are lots of cases, the working cases can be divided and be treated with sets indexed. For example, defining a new struct with cases by juctions, by mazes or by pair <juction, maze>.
• CBREngine. Class that implements StandarCBR and forces to implement some methods that manage important functionalities.
  The principal variables this class have are the following: the CustomPlainConnector, the CachedLinearCaseBase, the StorageManager and the ActionSelector.
  First, in method configure() with connector, this class loads the data from general database by the plaintextconfig.xml configuration and with it configures the StorageManager and the CachedLinearCaseBase.As soon as we start the game, it executes the precycle() which initialize the CachedLinearCaseBase.
  For each uptade of the game, it executes the method cycle(CBRQuery). This method implements the principal process of cbr cicle and it gets the similar cases to the actual one. From those cases the method will get the "best" Solution and configure it in a global variable. We create and insert a new CBRCase in the StorageManager in the method cycle(CBRQuery).
  Lastly, when the game is over, it will execute the postcycle() and close the database of the cases.
• Solution. Class, part of the CBRCases, which one contains the String that represents the action that was applied in the case.
• Result. Class, part of the CBRCases, which one contains how "good" or "bad" the solution was in the case associated.
• plaintextconfig.xml. XML file that descrives the variables to process into Description, Result and Solution of a CBRCase.