Skip to content

Main game developer

Jump to bottom
Cristina Alonso edited this page Feb 5, 2019 · 18 revisions

RAGE Analytics Wiki for Game Developers

Game Developers Guidelines

The first step to use RAGE Analytics is to correctly install: Docker and Docker-Compose if needed, and RAGE Analytics.

To access the front-end, game developers first need to log in through a POSTrequest to http://your-ip:3000/api/# with both the username and password on the request body. The response code will be 200 in case of successfully finding the user, or 401 otherwise. In case of success, the response will contain the username, email and registered roles of the user, as well as a token needed for back-end requests. An example success-response is:

HTTP/1.1 200 OK
       {
           "user": {
               "_id": "559a447831b7acec185bf513",
               "username": "root",
               "email": "yourmail@ucm.es",
               "roles" : ["admin"],
               "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIU..."
           }
       }

After login, you need to register the game in the front-end. This will provide a Tracking code for the game, used to link players with a particular game version. See further information on these steps in the QuickStart page, or an example on how to set up the tracking code.

You also want to connect the game model to the actual game through a link, adding a game link in the front-end.

To generate traces from your game, you can integrate one of the available tracker implementations. To send the traces to an analysis server, you need to configure the Host parameter (usually will be: /api/proxy/gleaner/collector) and the Tracking code parameter (obtained from the previous set-up). See further information on the tracker.

Figure 1.: Game developers can integrate different trackers in their games to send traces to RAGE Analytics.

Selected table of contents

Table of Contents

Clone this wiki locally