GameArter Basic SDK for Construct

Before a possibility to connect to the SDK, there is need to make a project configuration.

Create new html5 game project in projects section of GameArter system.

This is way you will get your project Id for communication with GameArter SDK.

Create a configuration for selected project version. You can have up to 5 versions of every project. (Only 1 version can be live, the other 4 serves for development purposes or AB testing).

• 1

  Documentation

  A button opening knowledge base you are currently at.
• 2

  2.1 Project ID

  Every project must have own unique ID. Project ID is a signature needed for communication with GameArter services. You got this id during creating your project in projects section of GameArter system. (point 2.1)

  2.2 Project Version

  For possibility of testing, GameArter provides to run up to 5 game versions. Every version has separated configuration and databases.

• 3

  SDK mode

  The mode, under which the SDK will run. Select Lite.
• 4

  InGame Currency

  The game uses own currency which will be exchangeable into global GRT (native IAP support). Select No.
• 5

  Progress mode

  SDK allows three types of counting user's game progress. Value of user's progress must be always saved in the SDK. This information is needed for displaying game info (progress, badges...) in the user's profile.

  Current progress state can be displayed also in the game. If the game does not contain GUI for this value, there is possible to display user's progress with other user's data over GameArter_DashBoard prefab. If you want to use GameArter_DashBoard prefab, but without progress bar, switch its visibility to state "hidden".

  • SDK | progress is being counted on a basis of received badges. (2 badges of 10 = progress 20%). You can display the progress in your own GUI, or via GameArter prefab GameArter_DashBoard prefab. If you want to use GameArter_DashBoard, but without the progress bar at the bottom, you can switch options of SDK Progress bar.
  • Individual | SDK does not count progress, only holds its value. There is always need to send changes of user's progress into the SDK. Progress can be displayed in your own GUI, or via GameArter_DashBoard, see the point above.
  • None | A game does not contain progress feature.
• 6

  Smart Events

  Before implementation, please read and try to understand Events purpose - In-game currency distribution. According to the event specification, make a plan, which game data will be saved as events and which as a different type of data.

  Event explanation
  Event is an important variable connected with a feature (leaderboard) or a reward (achievements, currency reward), or with a shop for direct in-app purchases. Event example: kills in a shooter game , lap time in a racing game, number of gints in a logic game... Value of event can be increasing, decreasing or without defined trend. Events with defined trend can have attached unlimited number of badges on every event. There can be active also leaderboard above these events. Events with undefined trend are designed for direct connection with in-game shop. There is a possibility to work with events in many ways, events are written generally to allow anything a developer may need.

  Examples:

  • "kills" event = total number of kills in a game
    Initial value is 0 (new player). The number of kills can only grow in a time (= event with increasing trend). There will be a leaderboard connected with the event (most kills in the game). There will be badges - 1st kill, 10th kill, 100th kill... Leaderboard and badges are made and distributed by SDK. Developer only needs to keep best "kills" value in events = update the event with every kill. Required "kills" value for events is set on server (point 2.3). Then, once the value of the event will achieve the value of a badge, SDK will reward the badge to a user automatically. If a user sends a request to see a leaderboard, the SDK will create the leaderboard by comparing "kills" values of all users in the game.
  • "bestLapTime" event = the lowset time achieved in a lap
    Initial value is any not-null number. E.g. 120 (secs). Lower time is mostly better (= event with decreasing trend). There is a leaderboard for the time in the lap (made by SDK on basis of the best time of all users who completed the lap). There are 3 badges for the lap - gold / silver / bronze time. At the end of every lap, the developer checks time saved in the event "bestLapTime" and if current time is better (lower), he updates best achieved time in the lap.
  • "maxAchievedMoney" event = a special help event allowing give own badge
    This is a special event allowing to give a badge on basis of a dynamic variable. E.g. there is a need to add badges "Earned 1st dollar" and "Millionaire". The badges are connected with a currency which has dynamic value changeable in both directions. Then, if currency value will achieve a specific milestone, you can update event "maxAchievedMoney" and a user will be rewarded by a badge.
  • "hints" event = number of available hints for a player.
    Let's say a logic game will not contain any in-game currency, badges or leaderboards. All required functionality is implementation of in-game purchases. A user has certain number of hints to use (either one-time only, or every day) and in a case of need, he can buy more for GRT currency via native GameArter shop system.

  
  Another possible event use-case

  Initial values of events are changeable in web environment as well. Thanks to this option, events can be used also for game testing - If you set e.g. items to be unlocked on basis of some event value, you can unlock them directly from server without need of game rebuilding.

  
  

  Define number of event groups | set number of groups in which you want to have events divided (better clarity)

  Event Group name - name of a group of events

  Events in group - number of events in the group

  • Event string id | ID name of the event. Name in lowercase letters, without spaces. this is string ID over which you will get and set values for the events.
  • Event Initial value | initial value of the events. (probably 0 for increasing trend). Any number > 0 you consider as optimal for decreasing trend. Any number >= 0 for undefined trend.
  • Trend | select, whether the event has increasing trend (value number is better (kills), or decreasing (lower number is better (best time of the lap), or undefined (value can be changed via in-game shop - e.g. number of hints)

Remember you projectId and Project Ver for next steps. Once done, save the basic configuration by pressing "Save configuration"

Services configuration is for files management, project versions management and adjusting data filled in the project configuration and for adding additinal SDK features as badges, leaderboards and in-game purchases. Services configuration is manageable via the project panel. Project configuration is still available for option of updates under button "Export conf".

Rows / Buttons explanation:
• Version ID | project version
• Last modified | Last modification in the version configuration
• Version State | project mode - testnet / production
• Interpreter | interpreter under which the project version runs
• Config status | Status of data state - draft / pending (= waiting for authorization by admins) / live (= approved,in production)
• Export conf buttonn | Opens project configuration (panel 2.2)
• Events button | Opens events configuraion (= rewards, badges, leaderboards)
• Packages button | Opens packages configuraion (= ingame purchases)
• More button | Opens configuraion of additional features
• Saved data button | Opens environment for reading / changing data of logged (developer) account in the game
• Files upload button | Opens environment for uploading game files
• Test the game button | Opens game in a new tab
• Remove button | Removes project version

• 1

  Smart Events configuration

  
  • Server-side contains all defined events. If not, contact support.

  
  EventDetail

  • Event ID | non-changeable string ID. All data you will fill for the event are associated with this ID. If you change its name / remove the ID, all associated badges and leaderboards will be lost. Do not change this, if it is not necessary. If so, contact support for possibility to convert users' data below the new event ID.
  • Leaderboard | Checkbox for activation of leaderboards for the event. SDK automatically creates leaderboards for the event. There are leadeabords created with filters 1 day / 1 week / 1 month / all-time. Trend of leaderboards is intended by event trend.
    
  • Trend | Trend of event. From safety reasons, there is no possibility to manipulate with events in both directions. An event can only grow (increasing trend) or fall (decreasing trend). Usage: increasing trend - total number of kills, number of opened maps. Decreasing trend - best time of a lap.
  • Initial Value | Initial value of event. By this, you can overwrite initial value set in the game. This value is returned to all new players. Default value for events with increasing trend = 0. Default value for events with decreasing trend - none, need to be set.
    If availability of some item depends on a state of event value, this is way you can set the item property for new users without need of rebuilding game, directly on one click from server.
  • Reward Cx | Reward for occured event in a currency depending on a native game currency. (Full SDK = GRT, Lite SDK = GRT/local game coins on basis of local game coins existence). Reward is for a change about one unit. Examples:
    • kill event - a coins reward for 1 kill
    • lap of a round - better time lap about 0.2sec → reward per 1 unit (=1sec) = 1coin → 0.2*1 = 0.2 coin reward.
    Values are for viewing only. This will be set / adjusted by GameArter administrator.
  • Reward Exp | available for Full SDK mode only. Works same as Reward cx, only the reward is in game experience. On basis of achieved experience in the game by users, there is possible to automatically manage items - unlock them for using (see more in items configuration). This feature allows to create basic game design.

  
  Add badge

  • Badge name | Name of a badge you want to add (e.g. 100 kills)
  • Event value | Event value on achieving which the badge will be received (= 100)
  • Coin reward | Received coin reward for received badge.
  • Exp reward | Received coin reward for received badge. (full SDK only)
  • Dx reward | Received diamonds for received badge. (rewards disabled currently)
  • img url | image of a badge. Fill name of image file. If you do not have an image for the badge, let it be.

  
  Event Badges List | list of created badges. You can adjust already defined badges here. If your game is already released and badges are rewarded, and you want to change value for a received badge, please contact support. Badges of all players will have to be recounted.
  
  Badge Collections | Group more badges to a defined collection. Max number of collections is three. E.g. Character, car, others. Badge collections do badge listing in GUI clearer.

  
  
  Saving events configuration

  Filled events must be saved. There are 2 options of saving. "Save as concept" saves the changes as a concept only - these saves are not visible from game. If you want to save the data and have access to them from a game, save them via "Save to production" button. If you do bigger changes for a project in production state "live", there is a need of approval by administrator. It is to prevent clashes which would lead to possible game crashes after changing values for badges, eventIDs and so on.

At the very beginning, there is need to set basic project configuration.

Download latest version of GameArter SDK Unity package from GameArter SDK for Construct section.

Insert GameArter SDK into your project:

1. Press right mouse button in Layout scene
2. Select "Insert new object option"
3. In "Platform Specific section", find and select GameArter SDK. Note, you will find this SDK there only if you do not have it selected in your project yet and you have it added in Construct.

GameArter SDK is initialized automatically. Initialization is created on basis of configuration data filled in GameArter object.

• Individual Game Mode

  There's a possibility you require to run the game in individual game mode on certain website or e.g. for testing. By using individual game mode features, you can set individual mode the game will run in for every website the game is published on. SDK will return you after its initialization number of mode which you will assign to a certain website. Then, you can simply set data with which the game should run according the mode number.

• Browser name

  WebGL games have often different performance in various browsers. With knowledge of a browser a game is running in, there is a possibility for optimization of disabling features for certain browsers. E.g. car destructions for Chrome.

  • List of Browsers

Requests to GameArter SDK may be caled only after SDK initialization.

Asking for nick-names is very annoying. Instead, nickname should be took from user's profile in GameArter. Similar with language, country and so on. Users should not be requested for any data they already provide. Here's example of available expressions for getting user's nickname, country and language.

• Tracking redirects

  With our solution you will know about every made redirect. - From what logo, on what website, and how oftenly is being used.

  

Every game contains many data-weight cutscenes, stories and animations which are displayed calmly only one time for the whole game. GSDK helps to reduce game filesizes by providing a story module — an option for downloading these stories from external storage only in a time when it’s required. Dynamic loading of game stories might be done via asset bundles or this SDK feature when the story is displayed in gameplayer above the game (like an ad).

• 1) Calling browser stories

  Be sure that animation of such number is available for your game.

• 2) Callback functions

  There is a callback state - "not found","loaded", progress states and "completed".

  
• 3) Setting / switching of stories

  Is being made in "More" section of configuration of the project

  

GameArter SDK allows to installation of web games as Web Apps to user's device. Installation is possible to PC as well as mobile device. This feature is available for games running directly at GameArter (not within an iframe).

Implementation

• NOTE: this feature is functional after submiting requests for publishing in GameArter.
• Icon of web app (displayed at user's screen of desktop / mobile) must be in .png format and in 2 dimensions - 192x192 & 512x512px. Name them "favicon-192.png" and "favicon-512.png" and attach to folder "_pwa". Upload this folder with other project files in "Files upload" section at GameArter panel.

NOTE: Button "Install game as app" must be hidden in default.