Game Events

**Bunni** · 12-18-08, 05:37 PM

How are we getting them? Do we have a list of all the events any where, or a place i could go look?

**Ewok** · 12-18-08, 06:15 PM

hl2sdk.addGameEventListener (or something like it, check out the map voting manager in daemons.py, it uses it)

The list of game events isn't officially published anywhere i've found, but the metamod team put together a list of the ones their aware of. Unfortunately, it's poorly documented.
http://wiki.alliedmods.net/Game_Events_%28Source%29

I'm not sure if you've worked with events before, so if you haven't, here's the basics:
All events have string names, and you register/unregister for them at any time. When an even comes in, it's passed with a set of parameters in the form of a map/hashtable. Keys are always strings, but values can be strings/numbers/etc. You need to know what type the value is, and then you use the appropriate "getter" to access it. So for instance for round win events, there is a key/value pair called "team_id", which stores an int. So you would get that value by doing event.getInt("team_id");

Other than that, the real trick to working with game events is (1) finding the event you're looking for, and (2) understanding the parameters that are passed with it, as there is little documentation on them.

**timikoy** · 12-19-08, 06:22 PM

A word of warning: some events don't seem to fire exactly when you'd expect them too.

**Bunni** · 12-22-08, 01:40 PM

few more questions:
im not quite sure i understand how we are monitoring the events.

for example matti passes all defined events to the addon.

how does lonestar see and manage events?

Let me make sure what i believe i understand so far is correct:

Originally Posted by daemons.py

events.addListener(events.EVENT_MAP_STARTED, mapVotingDaemon._mapStarted)
events.addListener(events.EVENT_MAP_ENDED, mapVotingDaemon._mapEnded)
events.addListener(events.EVENT_PLAYER_DISCONNECTE D, mapVotingDaemon._playerDisconnected)

This registers the event and when occurs passes relevent information to the assigned function, right?
But then my understanding cannot be right as there is an event broadcasting function:

Originally Posted by client.py

def _purgePlayer(self, p):
try:
self.players.remove(p)
except ValueError:
logger.error("Player %d (%s) doesn't exist in player list during purge" % (p.pid, p.address))
try:
del self.edictMap[ p.edict ]
except KeyError:
logger.error("Player %d (%s) doesn't exist in edict map during purge" % (p.pid, p.address))
self._removeSteamIdCheck(p)
if logger.logTarget is p:
logger.logTarget = None
events.broadcast(events.EVENT_PLAYER_DISCONNECTED, p)
p.dispose()

Whats the difference between addlistener and broadcast? Why one here and not the other?

To who is the even being broadcasted to? The listeners? Then who listens for the broadcast? Perhaps i am over complicating this but id rather have a full understanding...

**Ewok** · 12-22-08, 05:09 PM

To clarify there are two origins of events, and each has it's own way to listen to those events

To listen to SDK-originating events, you call hl2sdk.addGameEventListener("eventname", someFunction), and when the SDK broadcasts the "eventname" event, LoneStar will make sure someFunction is called.

The MapVotingDaemon class of daemons.py has an example of using the above:

Code:

sdk.addGameEventListener("round_end", self._handleRoundEnd)

With the above line its going to be listening for game-generated round_end events.

In addition to those events, LoneStar broadcasts LoneStar-specific events that do not originate from the game engine. The event module is what handles those events. So events.addListener is how you register to listen to the events, and events.broadcast is how LoneStar fires off an event to those listeners.

The quotes you have above are of this event system.