1. Download & install PACS
2. The PACS-Files
3. The Interface
4. How to play a game
5. How to create a players behaviour
• File
• Behaviour procedure
• Properties
• State
6. How to test your code
7. Troubleshooting

Download & Install PACS

Install Modula-2 compiler XDS first!!

PACSfiles.exe        (2.01 bugfix: Some students found a bug (the last one...) in the GetNbrPl procedure with conf.PlElFromInput TRUE)
 
• download the PACSfiles executable to a folder. This is a self-extracting file: after downloading double click the executable, specify the folder ("Folder to unzip:", don't forget this!!) and all the PACS modula-2 files are extracted to that folder...
• open PACS.mod in XDS, push RUN (the blue runner  in toolbar) while the file PACS.mod is selected
• if you upgrade from an older version:
• replace the old files
• recompile PACSInterface.def before running PACS.mod (otherwise you get errors)
• sometimes it is good to delete all the OBJ. & .SYM-files before recompiling (otherwise XDS get mixed up between the versions)
• if you use XDS version 2.32 (in PC-rooms from the third floor):
• in file PACSGUI.mod, line 5: change  <* NEW XDS_245 + *>  into <* NEW XDS_245 - *>
• if you use XDS version 2.45:
• in file PACSGUI.mod, line 5: change  <* NEW XDS_245 - *>  into <* NEW XDS_245 + *>

Browse the code

• PACS 2.01

The PACS-Files

• here a game is started
• here you can configure a game
• it generates the PACS.exe executable

• files: PACSEngine, PACSGui, PACSbitmap
• constructed by Jan & Johan
• you don't have to know or to use these files.
• only if you are interested in the engine...
• it is forbidden to IMPORT something from one of these modules!

• these are the files where the behaviour procedures of the players are implemented (by you)
• there is one such module & file per procedure
• each file & module name starts with the prefix of your group
• our prefix is JJ: JJSimplePl is one of our behaviour procedures
• store global procedures (you want to use in different behaviour procedures) in a seperate module, with a name that also starts with your prefix.

• this is the interface between the main module, the engine and the behaviour modules.
• PACSInterface.def gives you all you need to play a game or to create a behaviour.

• here we offer you some general procedures you may use
• see StandardLib.def for explanation

The Interface

• Game
• Behaviour Procedure

How to play a game

• Set plProcs
• Set configuration of game
• parameters
• mode
• level
• Call PlayPACS() procedure

How to create a players behaviour

In detail:

• check that PACS runs (RUN in PACS.mod)
• copy JJSImplePl.def & .mod to 2 different files
• give a name with the unique prefix of your group
• change in the 2 files the name of the module to the name that you give to your file
• change in both files the name of the behaviour procedures, the init & end procedure and the team name
• give a name with the unique prefix of your group
• add an IMPORT statement in PACS.mod
• copy the line FROM JJSimplePl IMPORT JJRandoms and change it to your own module name & procedure name
• use your team to a play PACS
• push RUN in PACS.mod
• if this works, you can start changing the behaviour procedures.

Behaviour procedure

• Procedure type PlBehaviourPr (see PACSInterface.def):

IN

• view: positions of the visible players & elements
• properties: own position, #lifes, #moves, #apples, wasKilledDuringLastTurn
• OUT
• moves: LL of directions
• Information procedures (see PACSInterface.def at bottom):
• arena labyrinth: retrieve (opvragen) with IsWall()
• view of player: IsInView
• #players
• #elements
• ids of ghosts
• game configuration
• Special output procedures (see PACSInterface.def at bottom):
• addcomment()
• only for Explorers: PutMine action (give position where you want to put a mine)

 

Properties

• camp, position, #lifes, #moves, #apples

State

user defined in module with global variables

How to test your code

• Start with a simple program, test it and gradually increase the program complexity.
• I know this is not easy in the beginning! But you should learn this!
• Test procedures independently!!
• Give an arena of your own
• Put players & elements by yourself on the board
• set configuration parameter plElFromInput to TRUE.
• create test situations and see if your player behave like you expect.
• Play yourself for a player:
• set behaviour procedure to AskUserForInput
• Game Mode:
• show player by player: give more detailed explanation
• show turn by turn
• write comment to the screen
• use a global variable gDebugLevel to set the level of detail of the comment (see JJMoveInDir.mod for an example and explanation)
• use the debugger

PACS Troubleshooting

Here we list all PACS specific errors, check the XDS troubleshooting page for general errors.
Check also the FAQ.
 

Problem	Solution
compile error: Key Inconsistency in ...	compile PACSInterface.def first  run PACS.mod then
compile error: Severe Error in ....mod (1:23): INTERNAL ASSERT(17) while reading symbol file "....sym"	delete all .SYM-files (generated by XDS) and recompile
Severe Error in PACSSound.mod (4:15): file open error: "Windows.sym" no such file	The installation of your XDS went wrong, it didn't install Windows.sym (necessary for PACS with sound): copy this file from here to the SYM/x86/ folder (which is in the folder where you installed XDS):   - for XDS 2.32: Windows.sym  - for XDS 2.45: Windows.sym to download this file: rightclick on the link and select "Save link as ..."
Error in PACSGui.mod (41:17): undeclared identifier "VideoConfig"	you are using XDS version 2.32 (in PC-rooms from the third floor):   in file PACSGUI.mod, line 5: change  <* NEW XDS_245 + *>  into <* NEW XDS_245 - *>
Error in PACSGui.mod (65:1): proper procedure is expected	you are using XDS version 2.45 (in PC-rooms from the third floor):   in file PACSGUI.mod, line 5: change  <* NEW XDS_245 - *>  into <* NEW XDS_245 + *>

---

- Back to the top -