The Setup Wizard - Integration & Monitoring In 3 Easy Steps

Step 1: Game Setup:

The first step after registering at the Devlounge should be creating your own game. Just enter some information about the game and you get the chance to upload some content for your Portal Landing Page that will appear on the Bigpoint portal.

Basic Data > General

Please enter some basic information about your game here. To improve the positioning of your game in the portal, the classification of your game is important, as well as the selection of languages it will be available in. Last but not least, you need to enter the URLs your game's API endpoint will be reachable at during development (dev URL) and when it's been published on the portal (live URL).

Game Name

Please enter a name for your game here. This does not need to be the final name of your game, as it won't appear publicly. Instead, it will be used in the Devlounge for display of your integrated games only and is treated like a working title.

The final name of your game can be entered at a later point using the Wizard Step 1: Game Setup > Portaltexts.

Example: Game Name: Testgame

Version Number

Please enter the current version number of your game here. Example: MyGame Version 1.0

Your Personal Subdomain

You can select a subdomain at the Bigpoint portal for your Portal Landing Page. You can enter alphabetical characters and numbers only, special characters are not allowed.

Example: testgame.bigpoint.com

Languages

Please select the languages your game supports. Be aware though, that your game needs to be fully localized if you intend to publish it at Bigpoint, as we need to be able to test the quality and integrity of each version. You can select as many languages as you like, of course, and in turn distribute your instances across the languages selected here.

Genre

You can classify your game's character by selecting up to three genres here. You can select between:

  • Action Game
  • Adventure/RPG
  • Casino/Cards
  • Logic
  • Fighting
  • Skill
  • Jump and Run
  • Classics/Retro
  • Racing Game
  • Shooter
  • Sports Game
  • Strategy Game

Minimum Age

Please enter the minimum age for your game here. In general, your game must be in line with German laws, especially section 3, article 14 of the German JuSchG and its regulations regarding the rating of online games.

Do you intend to use Bigpoint's payment system?

If you intend to use a microtransaction-system in your game, you should answer “yes” to this question. In any case, you don't need to integrate Bigpoint's payment system in your game if you don't intend to do microtransactions or purchases. If you choose to do so, you can choose between several payment models:

  • Item Selling (currency and game items can be sold using the payment system) OR
  • Subscriptions (premium accounts or premium packages which will grant an user advantages in the game).

You can choose whether or not to use any or both of these payment models.

Content Data > Portaltexts

These texts will represent your game on the Bigpoint portal. The better these texts, the more chances it has becoming a smash-hit. The goal should be generating interest and buzz for your game. These texts can be added seperately for each language your game is available in.

Game Title

Please enter the name of your game. 25 characters UPPERCASE. Example: TESTGAME.

Game Description Headline

Actual game tagline. Restrictions: 1 line @ 30 characters UPPERCASE (optimum), 2 lines @ 30 characters UPPERCASE (maximum). !! Please make sure that your texts meet the requirements. You need to enter line breaks manually and mustn't exceed given character restrictions. !!

Game Description

Unique text description. The first two paragraphs (or 10 lines) will always be visible. These should describe and sell the game to the user (landing page / conversion optimized text). The rest of the text on the page will be hidden and can be displayed to the user. This text should go into more detail about the game (first steps of gameplay, questing, world description etc.) and be keyword rich (seo). Restrictions: 4 paragraphs with 4 lines each @ 76 characters, first two paragraphs are always visible (optimum). 10 lines @ 76 characters visible and an additional 20 lines @ 76 characters viewable (maximum). !! Please make sure that your texts meet the requirements. You need to enter line breaks manually and mustn't exceed given character restrictions. !!

Content Data > Marketing Texts

These texts are part of the marketing for your game, the advertisements and the search engine optimization (SEO). They should make your game sound as appealing as possible and make it detectable by search engines.

Portal Home

Game Name & Tag

Actual game name and tagline. Restrictions: 2 lines @ 32 characters UPPERCASE (optimum). Example: GAMETITLE: JOIN THE QUEST AND EXPERIENCE AN AWESOME ADVENTURE !! Please make sure that your texts meet the requirements. You need to enter line breaks manually and mustn't exceed given character restrictions. !!

Game Name & Tag Promo

Actual game name and tagline (shorter), separated by colon. Restrictions: 2 lines @ 21 characters UPPERCASE. Example: GAMETITLE:EXPERIENCE THIS NEW ADVENTURE !! Please make sure that your texts meet the requirements. You need to enter line breaks manually and mustn't exceed given character restrictions. !!

Game Name & Tag Description (visible)

Unique text description. Should entice to play and describe the game accurately. Restrictions: 2 lines @ 32 characters. !! Please make sure that your texts meet the requirements. You need to enter line breaks manually and mustn't exceed given character restrictions. !!

Game Name & Tag Description (viewable)

Full description, visible after mouse-over. Please complete description above with an additonal 5 lines @ 32 characters (maximum). !! Please make sure that your texts meet the requirements. You need to enter line breaks manually and mustn't exceed given character restrictions. !!

Special Pages

Short Game Description

Unique text. This description will appear in the search results. Restrictions: 1 line @ 66 characters (minimum). 2 lines @ 66 characters (maximum). !! Please make sure that your texts meet the requirements. You need to enter line breaks manually and mustn't exceed given character restrictions. !!

Game Description Category

Unique text description. Should entice to play the game and describe it accurately. Restrictions: 5 lines @ 46 characters (optimum). !! Please make sure that your texts meet the requirements. You need to enter line breaks manually and mustn't exceed given character restrictions. !!

SEO

Further information about the search engine optimization can be found here.

Meta Title

When composing your meta title, please make sure that your keyword is put in first place (e.g. your game's name) - this text may not be longer than 65 characters.

Meta Description

The meta description does as the name suggests: It describes your game. You can put whatever the player can expect from your game right here, as long as it fits in 180 characters (90 characters MINIMUM). Your keyword should appear in here as well.

Content Data > System Mails

System Mails are e-mails that you wish to have automatically sent to specifically targeted users. You can use this method to supply your users with newsletters or welcome mails. Please note, that it is not possible to send HTML-mails currently. You need to create these mails in the content-area of the Devlounge first, as you need an existing sysmail-ID for this call to work.

The system doesn't differentiate between mails containing only text and those composed using HTML, as the sending of mails is handled by Bigpoint's own mailing systems.

However, if you want to send an email to a bulk of users, you might be better off using the newsletter-feature in the Livecare-area of the devlounge, which does not require you to send any calls at all. A detailed documentation covering all aspects of the “sendUserMail”-call can be found here.

Content Data > Teaser

Teaser-Icon (Big)

Here you can upload an image that will be used as a big icon on the portal. Valid picture formats are:

  • jpg
  • gif
  • png

The image must have a dimension of 96×96 pixels and will be displayed in the portal's “News Ticker” among other places:

Teaser-Icon (Small)

Here you can upload an image that will be used as an small icon on the portal. Valid picture formats are:

  • jpg
  • gif
  • png

The image must have a dimension of 58×58 pixels and will be display in the portal's “Game Ticker” among other places:

Teaser-Graphic used in games lists

This picture will be used in the teaser lists on the portal. Valid image formats are:

  • jpg
  • gif
  • png

The required dimensions for this image are 239×78 pixels and will be used to display your game inside the portal's game charts:

Big Top-Teaser

The most successful games will be presented very prominently with big teaser images. You can upload your biggest promotion image here with an allowed dimension of 570×330 pixels. Available image formats are:

  • jpg
  • gif
  • png

This image will be used on your Portal Landing Page among other places:

Promotion-Graphic (Big)

This picture may contain special elements like texts and claims and is the second biggest image in use on the portal. Valid image formats are:

  • jpg
  • gif
  • png

The image must have a dimension of 446×130 pixels and will be used in the portal as an advertisement for your game:

Promotion-Graphic (Small)

Here you can upload a small teaser image for your game. As always, the valid image formats are:

  • jpg
  • gif
  • png

The image must have a dimension of 104×86 pixels and will be used in the slider-area of teaser boxes:

Example-screenshot

Please upload at least one and a maximum of six screenshots for your game here. Valid image formats are:

  • jpg
  • gif
  • png

The screenshots must have a minimum width of 600 pixels and will be displayed on the right side of your Portal Landing Page:

Big wallpaper-image

Here you can upload a wallpaper for your game, which will be used as a background for the portal when it's displaying your Portal Landing Page. Use an artwork with the highest resolution available here and maybe shift some elements around, so that the best parts aren't covered by the portal's interface. Valid image formats are:

  • jpg
  • gif
  • png

Your wallpaper must have a dimensions of 1600 x 920 pixels:

Content Data > Support

Good support is an integral part of every successful game. Please enter the languages in which you intend to provide support, a support e-mail address and the URL for your forum.

This subdomain can contain characters from A to Z and digits from 0 to 9. Special characters are unfortunately not allowed.

Payment Data > Configuration

In this section you can set up the payment system such as the different currencies or a transction limit.

First of all you have to set up your main currency in the field “1st currency”. This is the currency that gamers can recieve or reload via payment (real currency). In addition you have the option to set up a “2nd currency” which gamers can recieve during the gameplay (virtual currency). If you intend to only use one currency, this field can be left blank.

Example:

1st currency: gold

2nd currency: silver

Furthermore you have the possibility to set up a limit for transactions in this wizzard-step, the so-called User Limit. This is the maximum amount in euro (or any other accepted currency) that the user is allowed to spend per day. This limit helps keep your in-game economy balanced. Bigpoint accepts the following currencies: dollars, British pounds, euro and zloty. Enter a sum in euro, and your users will be able to spend the equivalent in the relevant game currency.

Example:

User limit: 50 Euro

Payment Data > Wallpaper File

This is where you can upload al wallpaper to customize the appearance of your payment window. We recommend a resolution of 1080 x 680 (or comparable).

Payment Data > Item Configuration

In the item configuration you can create all the elements, you want to generate a revenue with → Your Payment Items. This might for example be visual items, such as virtual goods or a game currency. You can choose if you either want to offer the items with the classical payment system (credit-card, Paypal, bank-transfer) or via SMS and phone-banking.

Classical Payment Items

These Payment Items are understood as all items that can be payed with the classical payment method (no SMS and Phone-Banking). You can set a price for the items and the number of items the user can buy. You can divide your items into three categories, which can be further subdivided into different item types: game currency, item packs and premium pack.

Please note that you have to configure the different categories in different ways.

Game Currency

The so called game currency can be offered in two different types.Would you like to offer your 1st currency (real currency) in a item package or do you like to sell your 2nd currency (virtual currency)?

After that, you enter the euro amount for which your users can receive the item package.Additional currencies can be added based on this amount. Please note: The non-euro currencies will be automatically converted according to the current exchange rate. This is a service provided Bigpoint. In case of sharp fluctuations in exchange rates you should keep in mind to adapt the item costs if necessary. The user payment interface will only display the currency that is applicable to the country in which they are found.

Handle Content

Here you can handle your game content data. At first you can send your game content data to our QA by clicking on the “Send to QA” button. After the QA verification has been completed, you will receive our QA feedback.

If all entries are correct and your content meets our Terms and Conditions, it will be released for a portal launch. Afterwards it is your turn again to decide, when the game should be published on the Gaming portal by giving the “go-ahead” for the launch.

Of course you will also be able to do modifications to your content data again, but any changes made need to be verified by Bigpoint QA again, before they will become active. While these changes are being checked, your current game version will stay online of course.

Note: Please keep in mind that turning off a language will disable its content for all instances automatically. If the affected language is the only one available on this instance, the whole instance will be deactivated!

Furthermore you won’t be able to modify any content-related data, as long as our QA is checking it.

Step 2: Tech Setup

General > Instances

Here you can find a list of all your available instances. You can add a new instance here and also change settings of an already configured instance.

To create a new instance, you must enter a name, which will be used in the instance selection on the portal, and an development- and live-URL to your API-endpoints. If you don't need to enter an development-URL here, as your game is already available, you can just enter your API URL (live) here.

API URL (Live)

Here you can enter the URL to your API-endpoint, that will be used when the game has been made available in the live environment. Example: API URL (Live): http://www.yourgame.com/xmlrpc.php

API URL (Dev)

Here you can enter the URL to your API-endpoint that will be used as long as the game is in its development at the Devlounge. Example: API URL (Dev): http://www.dev.yourgame.com/xmlrpc.php

Instanz-Languages

Here you can select the languages the instance should be made available in. If you miss a language in this selection, head back to the Game Setup Wizard and add the missing language there.

APIs > Game

A detailed documentation covering all aspects of the Game-API can be found here.

APIs > Portal

A detailed documentation covering all aspects of the Portal-API can be found here.

APIs > Payment

A detailed documentation covering all aspects of the Payment-API can be found here.

iFrame

If you would like to integrate the registration- or login-process as used by Bigpoint in your own sites, you can use iFrames to integrate them.

The forms are hosted on Bigpoint's servers and will communicate closely with the account systems in place and will handle all validation of usernames, e-mail-adresses and more. All you need to do is to make sure that you the Game-API is implemented correctly in your game.

With each registration, not only an account in your game is created - the user will receive a portal account as well and can use this account to play other games integrated using the Devlounge.

To generate valid URLs for both iFrames, different base-URLs are used: iFrame containing signup http://portal-api.bigpoint.net/unified-signup/ iFrame containing login http://portal-api.bigpoint.net/unified-login/

All necessary parameters are appended to these base-URLs as GET parameters.

A detailed documentation covering all aspects of the available iFrames can be found here.

Handle Instances

Here you can handle all instances of your game. At first you can send your implementation of your game to our QA by clicking on the “Send to QA” button. Before the data is forwarded, automatic checks will test the functionality of all API methods necessary.

After the QA verification has been completed, you will receive our QA feedback and then it’s your turn again to decide, when the game should be taken online on the Gaming Portal by giving the “go-ahead” for the launch.

Note: Your first main instance is ready for a launch if at least one corresponding language supported by this instance is verified by our QA. Otherwise the instance remains in a pending status until all required data for a first launch is completely verified.

Of course you will also be able to do modifications to your instance data again, but the instance has to be taken offline first. Any changes made need to be verified by Bigpoint QA again, before they will become active.

Furthermore you won’t be able to modify any instance-related data, as long as our QA is checking it.

Step 3: Live Care:

Monitoring > Portal

Your game’s visitor statistics are displayed here. These statistics refer to the users: who registered for your game via the portal or who visited your game’s landing page in the portal.

The general statistics for your game’s performance in the Bigpoint portal are displayed here. This is primarily traffic information, for example, how many users have registered for your game, how many active users play your game via the portal and how many clicks your game’s landing page in the portal has gotten.

  • Number of users who logged in their game accounts in a defined period of time
  • Number of users who registered for your game in a defined period of time
  • Number of visits of your Portal Landing Page on the portal
  • Numer of unique visits of your Portal Landing Page (if a user has visited your page several times in the defined period of time, he is only counted once)
  • Numer of users who have deleted their game accounts in a defined period of time

Monitoring > Payment

This part of the Wiki will follow soon.

Monitoring > SAP

Here you can monitor several statistics referring to the game itself, its payment and conversion rates. You can find information about the amount of active users as well as monetary results such as the average revenue per pay user. These statistics produce reliable data starting from June 23th, 2011.

KPI Description
Revenue (total) Cumulated revenue for this period.
Revenue (new user) Cumulated revenue of new users this period.
Registrations Cumulated new registrations this period.
Payusers Cumulated unique paying users this period.
New payusers Cumulated amount of users that have registered and paid this period.
ARPPU (total) Average revenue per paying user, cumulated.
ARPPU (new payuser) Average revenue per paying new user, cumulated.
Active users Cumulated amount of unique users that have logged in at least once this month. Newly registered users count as active if they have logged in again at least 30 seconds after their registration.
New active users Cumulated amount of unique active users that have registered this month and had at least one login after their registration.
Devshare (total) Developer share of total revenue in this period.
Devshare (new user) Developer share of all revenue produced by new users in this period.
Revenue (total) Cumulated revenue for this period.
Revenue (new user) Cumulated revenue of new users this period.
Conversion (registered to active) Percentage of users, that turned from registered into active users in this period.
Conversion (registered to payed) Percentage of users, that turned from registered into paying users in this period.

News > Portalnews

Portal News texts are short texts explaining new updates and features in your game. These texts are displayed in the portal on your game’s landing page. You can write news texts in all languages in which your game is available. If you don’t write news texts for all available languages, the news texts will only be displayed if users select a language in which the text is available.

en/wizard.txt · Last modified: 2012/08/31 10:08 (external edit)
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0