back etc.).
events in memory for a period t
the important events during the period t
pose that game log entries (from possibly sev-
eral players) collected in that period can have
an arbitrary order as the case for web logs. The
reason for this is to avoid costly synchroniza-
tion in parallel implementations.
the player the human customer of the gaming
service.
cation mechanism in web usage mining. How-
ever, since many users can have the same IP
address (e.g. if surfing through a firewall or
proxy gateway), the IP address may not pro-
vide a unique user identification.
the user's browser which can be written to and
read by the web server), but cookies have got-
ten a lot of critics due to privacy issues. This
has resulted in that many users disable the
cookie support in their browsers.
coming uniquely identified when entering the
game (e.g. by username or by mobile phone
number) and stays identified the whole play-
ing session.
(e.g. using GPS positions obtained from the
player's wireless device). With the player
in a game usage mining context.
characteristics such as browser version and op-
erating system from the extended web log for-
mat.
formation might include the player's real-life
name, address, e-mail, connecting IP address
etc (based on manual input by the player when
registering).
of the avatar the virtual character that the
player controls in the game.
of HTTP requests, the most frequent request-
type is "GET" used to retrieve pages or ob-
jects, but also "POST" and "HEAD" occur
relatively frequently.
verbs, examples include "jump", "fire", "walk"
and "say" etc.
usually an encoded path requesting a particu-
lar HTML file, application/script or multime-
dia object. This path may contain its own pa-
rameters, e.g. if the path requests a script that
sets some variables.
sponding to action "say"), power or distance
(corresponding to action "fire").