Wednesday, February 29, 2012

i33

i32 to i33

New Features

[#1111] Implemented google/friends call

Note that this requires the developer have access to the gplus games api, and the user to have granted the right permissions.

[#1114] Player create functions return an auth_token

This removes some of the duplication of the old create/login workflow, as once a player is created the application will have an auth_token ready to use.

Bug Fixes

[#1121] Facebook offerwall was not granting currency

No currency was getting awarded on completion of the offer, even though the offer seemed to succeed.

[#1120] gplus information was potentially uninitialised in some cases

No live example of tis kind of data corruption has been noted.

[#1112,#1113] Scripts (and some other calls) can no longer use old auth_tokens

Scripts and some other functions were using an internal cache for auth_tokens that was not getting refreshed at an appropriate time. The cache is now update any time a players auth_token may have changed.

Posted by at No comments:

Tuesday, February 21, 2012

i32

i31 to i32

New Features

[1090] Now supporrts google login functions using oauth2 tokens

These functions are google/create_user_token, google/bind_user_token and google/login_user_token. These functions accept an oauth2 token, which are often exposed by the google APIs. The functions are equivalent to the oauth2 code functions google/create_user, google/bind_user and google/login_user.

[1054] Google chrome web store support added

Roar now support integration with the google chrome web store. To use this:

  1. Obtain google checkout and webstore accounts.
  2. Configure the webstore account callback to be http://api.roar.io/GAME_NAME/chrome_web_store/callback/
  3. Enter the details in the roar configuration page.
  4. Add entries to the google web store from the roar UI.
  5. Client will call chrome_web_store/list/ to obtain the list of items that can be purchased. Each of these contains a jwt field, which will be passed to the google web store API for purchase.

More details can be found here http://support.roarengine.com/kb/building-blocks/google-chrome-webstore-integration. A full example with of the UI integration can be found at https://github.com/mikeando/roar_minimal

Bug Fixes

[1103] Deleted achievements were crashing the server

Posted by at No comments:

Tuesday, February 14, 2012

i31

i30 to i31

There are no user facing changes in this version

Posted by at No comments:

Monday, February 13, 2012

i30

i29 to i30

New Features

[#1031] Roar now supports the Facebook Offer Wall

To integrate the Facebook in-app currency offer wall into your application you must follow these steps:

  • From the Facebook configuration UI: et the currency that you wish to use; and set the Facebook credits callback to api.roar.io/gamename/admin/fb/ (using the correct game name and server for your game).

  • Serve a currency icon and a currency info file from one of your servers. The content of the info file should look like this:

<html>
 <head prefix="og: http://ogp.me/ns#
    fb: http://ogp.me/ns/fb#
    fbpayment:http://ogp.me/ns/fb/fbpayment#">
   <meta property="fb:app_id"      content="[YOUR APP ID]" >
   <meta property="og:type"        content="fbpayment:currency" >
   <meta property="og:url"         content="[URL OF THIS FILE]" >
   <meta property="og:title"       content="[NAME OF YOUR CURRENCY]" >
   <meta property="og:description" content="[DESCRIPTION OF THIS CURRENCY]" >
   <meta property="og:image"       content="[URL TO AN IMAGE]" >
   <meta property="fbpayment:rate" content="[CONVERSION RATE OF FB INTO YOUR CURRENCY]" >
 </head>
</html>
  • Display the offerwall from your app, like this: (this example uses jQuery)
$('#YOUR_BUTTON').click( function(){  var obj = {    method: 'pay',    action: 'earn_currency',    product: '[URL OF CURRENCY INFO PAGE]'  };  FB.ui(obj, function(data) { /* handle response */ } );});

Bug Fixes

[#1087,1086] Saving old games configuration no longer generates a warning/error

Some old games that had not been updated were generating an error or warning when saving their configuration. In most cases the configuration was getting saved correctly, so this was mostly a cosmetic issue.

[1084,1083] Improved Facebook credits handling

The Facebook credits handling code relied on some Facebook features that were soon to be deprecated. The handling code has been updated to behave in compliance with the latest Facebook API.

Posted by at No comments:

i29

i28 to i29

New Features

Bug Fixes

[#1080] Friends lists are saving correctly again.

Some previous versions (i25, i26) were not saving friends back to the database correctly. These versions had only been rolled out to a few users, so this will not affect most users.

Posted by at No comments:

i28

i27 to i28

New Features

[#1033] Added support for tracking XP in leaderboards

XP can now be tracked as a leaderboard by enabling the XP leaderboard from the main page of the Roar Engine configuration UI. XP leaderboards function the same way as leaderboards for other stats. The XP leaderboard has a hardcoded id of 5001.

[#1044] Listing the available leaderboards now returns the resource_id

While this is mostly for internal tools, some developers may find it useful for use from their game client.

Bug Fixes

[#1041] Configuration UI no longer generates a large number of event warnings

[#970] Fixed some potential server crashes when reading configuration files.

Posted by at No comments:
Subscribe to: Comments (Atom)