This tutorial will present a special type of connection to UT server - ControlConnection (CC). Purpose of CC is to control UT game server and get some global information about the game. CC can get positions and scores of all players on the server, can respawn other players/bots, restart the game or change the map.
In this tutorial we will show you:
How to create your own ControlConnection to the server
How to initialize listeners for players in it
ObserverConnection tutorial.
If you are interested specifically in obtaining detailed information about other playres/bots consult thePogamut 3 has been fully mavenized. This allows you to try and run this example even without installing the Pogamut NetBeans plugin. However in that case you won't be able to use visualization as this is a part of Pogamut NetBeans plugin. To open up this example in NetBeans follow up the steps in Opening Pogamut Examples chapter. This archetype information is below.
For UT2004 example:
cz.cuni.amis.pogamut.ut2004.examples
14-custom-control-server-archetype
3.3.1
http://diana.ms.mff.cuni.cz:8081/artifactory/repo
This example should work in UDK as well.
The easiest way how to setup your custom control connection is to download and modify the example archetype above.
Control connection can be usefull when you want to get global information about the game or the players. Control connection has access to all player positions at every time. For more detailed observing of players visit ObserverConnection tutorial. Below you find example code from the archetype with listener to player messages.
/** * Control server connected to UT environment. Through this connection we get global * information about the game and can control the game. * * @author Michal Bida */ public class CustomControlServer extends UT2004Server implements IUT2004Server { private double currentUTTime; /* * BeginMessage listener - we get current server time here. */ IWorldEventListener<BeginMessage> myBeginMessageListener = new IWorldEventListener<BeginMessage>() { public void notify(BeginMessage event) { currentUTTime = event.getTime(); System.out.println("Begin: " + event.toString()); } }; /* * Player listener - we simply print out all player messages we receive. */ IWorldObjectListener<Player> myPlayerListener = new IWorldObjectListener<Player>() { public void notify(IWorldObjectEvent<Player> event) { System.out.println("Player: " + event.getObject().toString()); } }; @Inject public CustomControlServer(UT2004AgentParameters params, IAgentLogger agentLogger, IComponentBus bus, SocketConnection connection, UT2004WorldView worldView, IAct act) { super(params, agentLogger, bus, connection, worldView, act); } /* * Our custom hook, where we initialize our listeners. Note that UT2004Server class * is just stub, so no helper methods are present (no prepareBot, botInitialized, etc as with Bot classes) */ public void initialize() { getWorldView().addEventListener(BeginMessage.class, myBeginMessageListener); getWorldView().addObjectListener(Player.class, myPlayerListener); System.out.println("ControlConnection initialized."); } /** * This method is called when the server is started either from IDE or from command line. * It connects the server to the game. * @param args */ public static void main(String args[]) throws PogamutException { //creating agent parameters - setting module name and connection adress UT2004AgentParameters params = new UT2004AgentParameters(); params.setAgentId(new AgentId("ControlConnection")); params.setWorldAddress(new SocketConnectionAddress("127.0.0.1", 3001)); //create module that tells guice it should instantiate OUR (this) class CustomControlServerModule module = new CustomControlServerModule(); //creating pogamut factory UT2004ServerFactory fac = new UT2004ServerFactory(module); CustomControlServer cts = (CustomControlServer) fac.newAgent(params); //starting the connection - connecting to the server cts.start(); //launching our custom method cts.initialize(); } }