Mochi FAQ's & Documentation

Game Distribution Feeds

Below you will find documentation on our recently updated game distribution feed structure. If you are currently using or looking for documentation on the old feed structure, please click here.

1.0 Overview

Mochi provides publishers with feeds of our Games Catalog, which simplify your content collection process considerably. The new Games Catalog gives the user the ability to create custom game feeds based on any search you perform (including searches with multiple filters).

Feeds are updated once a day after 12:00AM PST (UTC-8). Each update will add new distribution enabled games to the feed, as well as indicate if any existing game was updated by the developer.

Feed Types

Feeds come in two flavors, Atom and JSON. When you create your custom feed in the new Games Catalog, you have the option of selecting either “JSON” or “XML “ (atom). The following is an example of all games in JSON format:

http://feedmonger.mochimedia.com/feeds/query/?q=recommendation%3A%3E%3D0&partner_id=XXXX

And here is an example of all games in atom (XML) format:

http://feedmonger.mochimedia.com/feeds/query/?q=recommendation%3A%3E%3D0&partner_id=XXXX&format=atom

2.0 Creating Custom Feeds

The all-new Mochi Media Games Catalog gives you the ability to create your own custom game feeds as you browse. This feed will reflect any and all filters you apply to your search, but you will need to request a new feed URL each time you change your search and click “Submit”. Here is how you do it:

  • Perform a search
  • Look for “Results feed” just above your results, and click on either the “JSON” or “XML” button
  • You will get a pop-up box with a URL- copy it
  • Plug that URL into your website or arcade script, and you will get the results from the search you just performed

3.0 Augmenting Feed URL Structure

You can augment your game feeds by following a standard URL structure, but the best way to create custom URL’s is to use the Advanced Search in the Games Catalog and click on ‘Results Feed”. In all cases, the games delivered via feeds are sorted by most recent (i.e. the newest games will be first).

All games

This is the root feed url and will contain the entire catalog of Mochi enabled games:

http://feedmonger.mochimedia.com/feeds/query/partner_id=XXXX

NOTE: You must include your own publisher ID in the feed URL. For purposes of these examples XXXX will represent your publisher ID

Limiting the amount of games

You can limit the number of games returned in the feed. This is useful for feed readers or widgets in which you want to pull a smaller, faster, feed for real-time display. The default limit is set to all games currently pulled from your feed.

http://feedmonger.mochimedia.com/feeds/query/?q=&limit=25

You can also use the offset parameter to fetch older games in smaller chunks. Note that the feed can change at any moment so iterating over the feed with the offset parameter is not guaranteed to be reliable. If you are doing this, you must make sure to increment your offset in quantities sufficiently smaller than your limit so that you do not miss any games. offset must be combined with limit.

http://feedmonger.mochimedia.com/feeds/query/?q=&limit=25&offset=10

Limiting to a single category of games

You may place the slug of any category after your publisher ID to limit the type of games in the feed. Games may contain more than one category, so you may see the same game show up across different categories.

http://feedmonger.mochimedia.com/feeds/query/?q=(recommendation%3A%3E%3D0)%20and%20category%3Aaction&partner_id=XXXX

Limiting games to a content rating

If you want to restrict the game feed to only contain a particular content rating, you may place the slug of the content rating as a second parameter after your publisher ID.

http://feedmonger.mochimedia.com/feeds/query/?q=rating%3Ateen

NOTE: This is not inclusive of wider content ratings. The above example will return only teen rated games.

List of available rating slugs:

  • all
  • everyone
  • teen
  • mature

Limiting by both category and ratings

You may combine URL parameters to limit by both a category and a rating.

http://feedmonger.mochimedia.com/feeds/query/?q=(category%3Aaction)%20and%20rating%3Amature

Limiting by game tag

You may choose to include games that include or exclude a tag

http://feedmonger.mochimedia.com/feeds/query/?q=tags%3atag

To exclude a tag you must preface it with the ‘not’ operator. For example:

http://feedmonger.mochimedia.com/feeds/query/?q=not%20tags%3atag

Note:

Chinese games within the Mochi Feed System are tagged with 'zh-cn'. To omit Chinese games you would use the url parameter 'q=not%20tags%3azh-cn'

Limiting by game developer

You may choose to include only games by a single developer.

http://feedmonger.mochimedia.com/feeds/query/?q=developer%3aname

Note:

You can get the author name from the author field of the feed, or from their community URL

https://www.mochimedia.com/community/profile/developer

4.0 Field Description

The following fields are available in both the ATOM and JSON versions of our feeds.

  • name
    The game's name as given by the developer

  • tag / game_tag
    Unique 16 character key identifying this game in the Mochi system

  • author
    Name of the developer of this game

  • author_link
    Link to Mochi Community profile for this game's author

  • description
    Text description of this game

  • updated
    Most recent date the game was updated

  • slug
    Unique text slug

  • width
    Game width, in pixels

  • height
    Game height, in pixels

  • resolution
    Text representation of {width}x{height}

  • media:thumbnail / thumbnail_url
    Path to game's 100x100 thumbnail

  • thumbnail_large_url
    Path to game's 200x200 thumbnail

  • screen1_url, screen2_url, screen3_url, screen4_url
    Path to game's screenshots. 1-4. No standard size.

  • screen1_thumb, screen2_thumb, screen3_thumb, screen4_thumb
    Path to game's screenshot thumbnails. 1-4. Clamped to 350px in width.

  • video_url
    Path to game's gameplay video. Hosted on Vimeo, YouTube or WeGame.

  • uuid
    Universally Unique Identifier for this game

  • control_scheme
    JSON encoded key-value mapping of the games controls.

  • instructions
    How to play the game, provided by the developer

  • control_scheme / key_mappings
    JSON encoded key-value mappings of the keys used in this game

  • rating
    Content rating, one of everyone, teen or mature

  • game_url
    A URL where the game is located, either on the Mochi site or the developer's site.

  • swf_url
    A URL where the game is hosted on Mochi servers

  • categories
    Comma-delimited list of game categories

  • keywords / tags
    Comma-delimited list of game tags, provided by the developer

  • created
    When the game was added to the Mochi system

  • leaderboards / leaderboard_enabled
    True or False value if the game uses Mochi Scores

  • achievements_enabled (available in JSON feed only)
    True or False value if the game uses Mochi Achievements

  • coins_enabled
    True or False value if the game uses MochiCoins

  • coins_revshare_enabled
    True or False value if the game uses MochiCoins and the developer has opted to share coins revenue with publishers

  • feed_approval_created
    Date the game was added to the feed

  • zip_url
    URL of a zip package containing the thumb, game SWF, and meta data

  • featured / recommended
    Value of true or false indicating if this game is featured by Mochi staff.

  • stage3d
    If game is tagged with "stage3d", value will be "true". Otherwise, it will be "false".

Bridge

For game developers, Mochi offers simple drop-in solutions for creating leaderboards to track high scores in their games. The Mochi Game Distribution catalog contains hundreds of Mochi Scores enabled games with more being added everyday. As a service to publishers, Mochi allows site owners to integrate and customize leaderboards data directly into their sites.

Leaderboards are a way each game can track user performance on a variety of metrics. The leaderboards are defined and created by the game developer, and there can be multiple leaderboards for each game. Leaderboards can track numbers or time, and can be sorted by highest or lowest scores. Each leaderboard can also have a scoring label to determine what kind of score it is tracking. (such as 'jewels', 'monsters killed', or 'lap times').

1.1 Overview

The Bridge is a feature that allows communication between a Mochi Scores game and the publisher.

Benefits of using the Bridge:

  • Leverage hundreds of Mochi Scores enabled games to attract new players.
  • Build exciting site features – Save player scoring info for all Mochi Scores games.
  • Encourage competition – In-game scores are listed for your community only.
  • Maintain consistency – Display your own community usernames when players post scores.
  • Promote your brand – Put your site logo directly in the game.

Bridge integration is great for:

  • Show top scores and gaming history in your player profiles.
  • Show friend scores to players and let them invite others to compete.
  • Get players hooked with points or prizes for obtaining top rankings.

1.2 Installing the Bridge

The Bridge is implemented as a simple JavaScript embed you can place on your game pages. This code acts as a secure connection to the publisher site, sending any relevant information it receives from the game, and giving the game any relevant information it requires. This provides a layer of separation between the game developer's code and the publisher site.

The embed code and settings for the Bridge can be found on your publisher settings page.

Note: You don't need to worry if the game is a Mochi game or if it is Mochi Scores enabled. The Bridge will sit quietly if it can't communicate with a game.



IMPORTANT: Cross Domain Policy

You must add x.mochiads.com, www.mochiads.com and www.mochimedia.com to your site's crossdomain policy file in order for the Bridge to be able to communicate with your server. You should do this in all cases no matter which integrations features you use. You can learn more about crossdomain policies here.


Note: Please note that the Bridge will not display an on size leaderboard. To do this, you must implement one using the gateway callback, or by using the Leaderboards Widget





1.3 Embed Example

The following example demonstrates a typical Bridge embed with JavaScript.

<div id="leaderboard_bridge"></div>
<script src="http://xs.mochiads.com/static/pub/swf/leaderboard.js" type="text/javascript"></script>
<script type="text/javascript">
// Mochi Bridge
var options = {partnerID: "[[Publisher ID provided by Mochi Media]]", id: "leaderboard_bridge"};
options.userID = "29281";
options.username = "rockstar";
// optional
options.sessionID = "sf908uw098urerjw3948";
// optional
options.gateway = "http://www.example.com/bridge/";
// optional
options.profileURL = "http://www.example.com/profile/${name}";
// optional
options.logoURL = "http://www.example.com/images/icon_16x16.jpg";
// optional
options.siteURL = "http://www.example.com/";
// optional
options.siteName = "Example.com";
// optional
options.callback = function (params) { alert(params.name + " (" + params.username + ") just scored " + params.score + "!"); }
// uncomment this to display global scores
// options.globalScores = "true";

// optional
// options.denyScores = "Login to Example to submit scores!";

// optional
// options.denyFriends = "true";
/*
// uncomment this block for debug mode
options.width = 320;
options.height = 240;
options.debug = "true";
*/
Mochi.addLeaderboardIntegration(options);
</script>

You can find your unique publisher ID in your publisher settings page.

1.4 Embed Parameter Descriptions

Certain publisher information is required in order to take advantage of various Bridge features. This metadata is provided as variables passed to the JavaScript function that initiates the Bridge.

  • partnerID
    Your unique publisher ID. This can be found in your publisher settings page.

  • id
    The id of the HTML element you want to place the Bridge SWF into. If this parameter is NOT set, the Bridge will write a new DIV element to the page with the id of 'mochi_leaderboard_bridge'. This DIV will be written in the same location the Bridge JavaScript call is made.

  • userID (optional)
    The unique id for the user on the site. This is a string which must be unique for each user. This ID is passed back you if you are providing a gateway URL for scores.
    Please note in Leaderboard 3.0: this value is now used to determine if a user is logged into your portal. You may specify any value you wish here, it should however be unique to individual users. Please do not specify userIDs for guest accounts.

  • userPrefix (optional)
    Deprecated in Leaderboard 3.0: See profileURL for alternative.

  • gateway (optional)
    A fully qualified URL on which will receive posted leaderboards data. ('http://' is required).

  • username (optional)
    The display username for the player for your site. The game will check to see if the Bridge SWF has received a username from the publisher site. If it has, then it will use that username instead of allowing the user to enter one. For guests, you can either supply a generated guest name yourself (such as 'guest1234') or allow them to enter their own names.

  • sessionID (optional)
    The unique identifier for the current logged in user session on your own site. If you supply this session variable, it will be passed through to your gateway for authentication.

  • logoURL (optional)
    A URL to an 16x16 JPG icon for your site. This will display on the leaderboard within the game. This will not be used unless a siteName has been specified.
    Please note: For compatibility with older games, our services are designed to run in flash player 7 and higher. As a result, we are only able to support JPG images at this time.

  • siteURL (optional)
    The URL of your site. Used as a link on the 16x16 JPG icon.

  • siteName (optional)
    The name of your site. This will display on the leaderboard within the game.

  • globalScores (optional)
    Set to true if you wish to display global scores and not just those submitted from your site.

  • pageURL (optional)
    A valid URL to play this game on your site. Defaults to location.href. Normally this default is fine unless you keep sessions in the URL or your games are played in an IFRAME (such as with Facebook apps).

  • callback (optional)
    A JavaScript function which will be called when the player submits a score. This can be used instead of the gateway if you prefer to handle the score information via the client-side. Or you may want to alter the game page based on the submission. The function receives a JavaScript object as a single parameter using the same naming system as the gateway score submission. Callbacks can also now verify javascript callbacks using the same signature system as used in the gateway postbacks.

  • postMedals (optional)
    This parameter will allow the bridge to post back information regarding medals received by the player. This parameter defaults to false.

  • denyScores (optional)
    This parameter will replace the score submission portion of the leaderboard with the value that this parameter is set to. The value will be rendered as HTML in flash, and must conform to AS2 HTML formatting requirements. This allows publishers to ask users to login before they are allowed to submit scores to the leaderboard. This parameter will also remove challenge integration.

  • denyFriends (optional)
    When defined as "true", this parameter removes references to external friend networks. That includes the Friends tab and the Facebook integration.

  • thumbURL (optional)
    New to leaderboard 3.0. You can now specify a thumbnail image for user profiles. These images will be displaced next to user's score that have been submitted to publisher domain boards. globalScores must be set to false for this option to work. This parameter will be ignored on all submissions that provided without a valid userID.

    URLs may be keyed by either userID or username. These values are inserted into the URL using two magic tokens "${uid}" and "${name}". For example, if user "asterick" as logged in with id "09DE", specifying a thumbURL of "http://www.sploder.com/thumbs/${name}.${uid}.gif" will load "http://www.sploder.com/thumbs/asterick.09DE.gif". These values are case sensitive.
    Please note: For compatibility with older games, our services are designed to run in flash player 7 and higher. As a result, we are only able to support JPG images at this time.

  • profileURL (optional)
    New to leaderboard 3.0. You can now specify a templated link for user profiles. These profiles will be accessible by clicking any score submission on your leaderboard that has an associated userID. globalScores must be set to false for this option to work. This parameter will be ignored on all submissions that provided without a valid userID.

    URLs may be keyed by either userID or username. These values are inserted into the URL using two magic tokens "${uid}" and "${name}". For example, if user "asterick" as logged in with id "09DE", specifying a profileURL of "http://www.sploder.com/profile/${name}?uid=${uid}" will load http://www.sploder.com/profile/asterick?uid=09DE" will". These values are case sensitive.

  • publisherHTML (optional)
    New to leaderboard 3.0: Publishers may now specify a full, HTML encoded page to be included with the leaderboards. This block of text will appear as it's own tab and is fully customizable to the publishers wishes. This page can be used to drive registrations, push logins or even display statistics about the current logged in player.

    Currently, only a limited subset of HTML is supported. Please consult Adobe's 'Using HTML-formatted text' for a more in-depth reference. We support 3 internal style classes, 'default', 'title' and 'byline'.

  • publisherTab (optional)
    New to leaderboard 3.0: If you have specified a publisherHTML block, setting this value allows you to change the title text of the tab. This value defaults to "Publisher"

  • bridgeKey (optional)
    This allows you to create a private channel for the bridge and game to communicate, preventing cross talk with other mochi score titles. To use this value:

    1. Create a unique key to pass to the game and bridge
    2. Pass your key to the mochiscore bridge (EG: options.bridgeKey = 'MYKEY'; in your addLeaderboardIntegration call)
    3. Append key to your game SWF url "?mochiad_options=bridgeKey=MYKEY" (EG: "example.swf?mochiad_options=bridgeKey=MYKEY").

    NOTE: This value MUST be unique across to each page, otherwise this may disrupt functionality. This parameter is not required. When in doubt, do not use this value.

1.5 Receiving Player Score Data

To receive scoring information, publishers will need to supply a gateway URL in the embed parameters for the Bridge to send game data. The Bridge will post the data (as HTTP POST parameters) to this URL when the score is submitted. The parameters are:

Score Information:

Player score is typically reported at the end of the game. The player is prompted to submit their score for one or more leaderboards. Leaderboards are defined by the game developer, and can represent a number or length of time (in milliseconds).

  • submission
    "score" will be passed here. This is used to filter score submissions.

  • userID
    Unique ID of the logged-in player. This will be what you supplied in the embed parameters.

  • name
    Username the user input for the score.

  • username
    Username you supplied in the embed parameters.

  • sessionID
    Returned ID provided through the embed parameters to identify the unique user playing the game.

  • score
    Integer indicating the score the player is submitting

Leaderboard Metadata:

Each leaderboard contains metadata to describe how the score should be tracked and displayed. The Bridge will supply the meta data for game leaderboards each time a score is submitted. It is up to the publisher to store this metadata in order to properly display leaderboards on their site.

  • gameID
    Unique ID of the game the leaderboard belongs to.

  • boardID
    Unique ID of the leaderboard.

  • title
    Title of the leaderboard

  • description
    Text description of the leaderboard (optionally supplied)

  • datatype
    Value indicating the type of score. Values are either 'number' or 'time'. Note: time is supplied in milliseconds

  • sortOrder
    Value indicating the sort direction of the scores. Values are either 'asc' or 'desc'.

  • scoreLabel
    Label to indicate what the score represents. (ex: 'Track time', 'Gems', or 'Points')

Authentication Data:

  • signature
    (this is part of the security protocol explained below in 1.7)

1.6 Receiving Player Awards Data

To receive medal information, publishers will need to supply a gateway URL in the embed parameters for the Bridge to send game data. The Bridge will post the data (as HTTP POST parameters) to this URL when the medal is submitted. Please note that you must include and set the postMedals parameter to true in your embed options in the publisher bridge settings. The parameters are:

Award Information:

Player score is typically reported at the end of the game. The player is prompted to submit their score for one or more leaderboards. These events also apply to the internal achievements system. The actual type of the achievement can be determined by the 'kind' value posted in the callback. Leaderboards are defined by the game developer, and can represent a number or length of time (in milliseconds).

  • submission
    "medal" will be passed here. This is used to filter medal submissions.

  • name
    Plain test name of the medal achieved.

  • kind
    this value will be 'leaderboards' in the case of a leaderboard medal, and 'ingame' for an achievement.

  • description
    Plain text description of the award achieved.

  • thumbnail
    Fully qualified URL to a 64x64 pixel image of the award.

  • gameID
    Unique ID of the game that this award is associated with.

  • userID
    Unique ID of the logged-in player. This will be what you supplied in the embed parameters.

  • username
    User name of the player. This will be what you supplied in the embed parameters.

  • sessionID
    Returned ID provided through the embed parameters to identify the unique user playing the game.

Authentication Data:

  • signature
    (this is part of the security protocol explained below in 1.7)

1.7 Partner Server Authentication

In your publisher settings page you'll find a secret key that can be used to authenticate the score data sent from the Bridge to your server. The signature is an MD5 hash of the POST vars + your secret key.

In order to use this for authentication, create a string of all the POST vars and their values, EXCEPT signature. The POST vars and values should be a URL encoded string, sorted alphabetically by param name.

When the Bridge sends variables to the supplied gateway, all parameters are treated as escaped UTF-8 data using the encoding specified by RFC 1738. This will mimic the behavior laid out by the PHP rawurlencode() function in most conditions.

The bridge will additionally send this value to the javascript callback using the 'signature' property name. You url encode the values (excluding the 'signature' property) in order to verify the data.

In accordance to this standard, we will not escape: Letters, numbers, hyphens ('-'), periods ('.'), or underscores ('_').

Equivalent escaped form of commonly used characters

%20space %21! %22" %23# %24$ %25% %26& %27'
%28( %29) %2A* %2B+ %2C, %2F/ %3A: %3B;
%3C< %3D= %3E> %3F? %40@ %5B[ %5C\ %5D]
%5E^ %60` %7B{ %7C| %7D} %7E~

  1. Populate an array of all parameter names as keys and their values.
  2. Remove out the signature parameter.
  3. Sort the array alphabetically by the key name.
  4. Turn the array into a url encoded string that looks like this:

    boardID=1e113c7239048b3f​&datatype=number​&description=This%20is%20the%20MochiScores​&gameID=84993a1de4031cd8​&name=rockstar​&score=11519​&scoreLabel=score​&sessionID=sf908uw098urerjw3948​&sortOrder=desc​&title=My%20Top%20Scores​&userID=29281​&username=rockstar

  5. Append your secret key. For example, if your query string before was ...

    &username=rockstar

    then it would look like

    &username=rockstarsdcb66e8d7676deb7e6db787cbd98d

  6. Compute the MD5 hash with the string, and compare your MD5 hash with the signature parameter sent by the Bridge. They should be identical.

This security authentication protocol is optional, since the data sent is not encrypted. Due to the fact that all of the game-play interaction and communication occurs within the client browser, this security protocol is not foolproof. However, this system will make it more difficult for the casual user to send fake scores to your site. You can also use your own user session ID information that you pass through the SWF to further authenticate the requests.

Note: While using PHP, use caution when working with 'magic quotes'. Developer and user defined variables such as names and leaderboard titles could contain special characters such as backslashes which can result in unwanted behavior. For best results, use single quotes or disable magic quotes all together.

Leaderboards Widget

2.1 Overview

You can display high score information directly on your website using our Leaderboards Widget. The widget accepts a game slug and partner ID and will display all the available leaderboards for the given game. The partner ID will constrain the widget to showing only scores from your site if you choose to do so. The widget is a Flash .SWF that can be embedded on any HTML page on your site. Note that the Leaderboards Widget is separate from the Bridge. If you want site-locked scores or other customizations, you must implement the Bridge.

2.2 Installing the Leaderboards Widget on your site

This widget is a Flash .SWF that can be embeded on any HTML page on your site. You can customize the widget's look and feel through EMBED tag parameters. You can also find pre-populated EMBED examples for every qualifying game in the Mochi Media game catalog.

Basic Embed Example:

We recommend using one of the JavaScript based examples below, but if you want something super simple here it is! The following example uses an embed tag to embed a 400x400 leaderboard widget for the game with the slug "mochiscores-sample-game":

<embed src="http://xs.mochiads.com/static/pub/swf/LeaderboardWidget.swf?game=mochiscores-sample-game"
allowscriptaccess="always" allowmenu="false" quality="high" width="400" height="400"
type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer"></embed>

Simple JavaScript Example:

The following example uses JavaScript to embed a 400x400 leaderboard widget for the game with the slug "mochiscores-sample-game":

<div id="leaderboard_widget"></div>
<script src="http://xs.mochiads.com/static/pub/swf/leaderboard.js" type="text/javascript"></script>
<script type="text/javascript">
Mochi.showLeaderboardWidget({game: "mochiscores-sample-game", id: "leaderboard_widget"});
</script>

Customized JavaScript Example:

The following example uses JavaScript to embed a fully customized 500x500 leaderboard widget for the game with the slug "mochiscores-sample-game", replacing an existing div with the id "leaderboard_widget" and using publisher-specific scores: NOTE: you can select a specific tab by defining the 'defaultTab' option. Valid tabs are: "daily", "weekly", "monthly", and "alltime".

<div id="leaderboard_widget"></div>
<script src="http://xs.mochiads.com/static/pub/swf/leaderboard.js" type="text/javascript"></script>
<script type="text/javascript">
// Customized example: Embeds a 500x500 leaderboard widget, replacing the "leaderboard_widget" div
var options = {game: "mochiscores-sample-game", width: 500, height: 500, id: "leaderboard_widget"};
// Select a specific leaderboard for a game - optional (if not included, a selectable list will be used)
options.leaderboard = "Level 1";
// your publisher ID - optional (if not included, ALL scores from all sites will be shown)
options.partnerID = "0123456789adbcdef";
// username link prefix - optional
options.profileURL = "http://www.example.com/profile/${name}";
// leaderboard background color - optional
options.backgroundColor = "#ffffff";
// Show the widget!
options.defaultTab = "alltime";
// Default to the all time tab!
Mochi.showLeaderboardWidget(options);
</script>

Auto Post

1.0 Overview

The Auto Post feature allows you to add a game to your site with a single click. By implementing our API on your site, you'll be able to browse the Mochi Game Distribution catalog of games and click "add to my site". This will send all the important game data via the API to your url, where you can store and display the game automatically. Here's a high level overview of how the API works:

  1. User clicks "add game to my site"
  2. Mochi servers make an HTTP request to a URL you supply in your publisher settings
  3. The URL is appended with a unique game ID that the user requested
  4. Your site implementation should then call back to get a Mochi URL supplying it with your publisher ID and the game ID
  5. Once we confirm the publisher ID and game ID matches our records, we return the full game data which you can import and process

Mochi Media Game Posts to your Server

curl -d 'game_tag=XXXX' http://www.example.com/mochi.php

You request a feed from Mochi Media:

http://feedmonger.mochimedia.com/feeds/query/?q=%28game%3A{GAME_TAG}%29&pubid={PUB_ID}&format=atom

NOTE: You must use your own publisher ID and the game tag you received in order to receive the game data

NOTE: Autopost will only work with one domain per user account (and creating multiple accounts is against Mochi Media's terms of service). To host games on multiple domains, you will have to do this manually.

Verify Game Hosting

1.0 Overview

To earn money with MochiAds for Publishers you will need to host the game's SWF file on your own server that you've verified in your site settings. Your object/embed tags must be loading the game SWF from this location in order for you to receive credit for the ad impressions and coin sales you generate.

2.0 Verify Game's Domain

To verify that the SWF on your site's game pages are being hosted by your verified domain use the following bookmarklet: SWF Detect

This bookmarklet, when clicked, will show you the URLs of embedded flash content on the current page. If the list of URLs contains games.mochimedia.com odds are you are not hosting the game yourself and will not be earning any money from gameplays on your site.

Arcadem Pro 2.8+



Arcadem Pro is a popular and full featured arcade script. Arcadem Pro 2.8 includes Mochi Media feed support, allowing you to browse the latest Mochi Media games and add directly in their admin panel. The screen shots below show how the integration works:


      

phpArcadeScript



phpArcadeScript recently released version 4 of their popular arcade script. The new version includes direct import of Mochi Game Distribution feeds into the game library.


AV Arcade



Mochi add-on for using AutoPost with AV Arcade script. This only works with PHP5, if the user wishes to use PHP4 they must insert the JSON Decode lines. For support, visit the AV Arcade forums.

Mochi Autopost for AVAv3

Requires AV Arcade version 3.0 or later

onArcade



onArcade has built in support for Mochi Media feed and scores system. See onArcade wiki for more information