Changes between Version 3 and Version 4 of Scenarios
- Timestamp:
- Jul 14, 2011 4:10:44 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Scenarios
v3 v4 19 19 There are currently two implementations of the CTF scenario implemented in Quagents - one clientside and one serverside: 20 20 * The clientside scenario is implemented using only the Quagents3 Java API. In it, the player controls a Quagent using Java swing listeners. A simple GUI is provided, which provides experiment control. Additionally, audio recording is automatically handled within the client code, so the user need only attach a microphone. For a more detailed description, see [[Quagents Capture the Flag]]. 21 * The serverside scenario is implemented from within the Quake VM. Enabled using [[Quagents Configuration Options]], it automatically records all player's data (as described above) and uses a trap function to write the data to a logfile within the [[ioquake ]] private filesystem. The user must, however, start up an external voice recorder to record audio tags. The Quagents team has provided one of these for general use, located in quagents/client/auxquagents.21 * The serverside scenario is implemented from within the Quake VM. Enabled using [[Quagents Configuration Options]], it automatically records all player's data (as described above) and uses a trap function to write the data to a logfile within the [[ioquake3]] private filesystem. The user must, however, start up an external voice recorder to record audio tags. The Quagents team has provided one of these for general use, located in quagents/client/auxquagents. 22 22 23 23 It is important to note that this scenario is distinct from the native Quake 3 Capture the Flag mode. The goal of the scenario is to produce usable data for further research, not to "win" the game and get the highest score.