🎮

Prepare, Launch, & Operate

Pley's objective is for game studios to continue doing exactly what they are good at; building, launching, and publishing their game. With Pley, you continue to do just that, but leveraged by web distribution. Now, that includes your own direct-to-player gamesite AND web game destinations such as Crazy Games.

Even when launching on Crazy Games through Pley, the should always just be:

• One game build
• One game server
• No extra SDKs
• No extra work to maintain

This documentation shows the steps and requirements to launch to Crazy Games as Pley game. Once you are live, there is no additional workload. One game on the web -- multiple destinations for users to play.

Timeline Estimation:

1. Implementation prerequisits (1-2 days of development)
2. Enable mobile gameplay (0-3 days of development)
3. Launch Process (0-3 days, plus Crazy Games' QA wait.)

(1) Implementation prerequisites to launch on Crazy Games

Before submitting the Pley game to Crazy Games, some minor game code additions are required. You do not need to add any new SDKs.

1. Update the Pley SDK to version 5.5.0 or newer.
2. If a new user is generated which creates a username, set the name using GetUsername().
3. Make sure the required Pley analytics methods are called. (How-to documentation / C# Reference)
4. Add the mandatory crazy-games events, and make sure they trigger at the appropriate moment.

//Initialize analyticsKit with player properties
Pley.AnalyticsKit.Initialize(config);

//Example of how to fire an event
PleyResult result = Pley.AnalyticsKit.GameLoaded();

//Examples of how to fire the events which is a prerequisite for Crazy Games:

//Gameplay Starts
PleyResult result = Pley.AnalyticsKit.GameplayStart()
//Player pauses the screen or a menu opens.
PleyResult result = Pley.AnalyticsKit.GameplayStop()
//Player clicks resume or closes the menu
PleyResult result = Pley.AnalyticsKit.GameplayStart()

//Loading screen starts, loading assets for next scene.
PleyResult result = Pley.AnalyticsKit.LoadingStart()
//Loading...
PleyResult result = Pley.AnalyticsKit.LoadingStop()
//Assets are loaded, loadings screen completed, and closes.

Final note; Crazy Games' has some guidelines when it comes to ads and game quality. This is a non-concern for most Pley games but could be good to review before the game is submitted for launch.

• Crazy Game's Guidelines for video ads.
• Crazy Game's Guidelines for Game Quality.

📘

Pley Platform Integration

This is a very small list of things you have to do to enable a Crazy Game's launch. Pley runs the Crazy Game SDK for you, making sure that the right behavior happens no matter where the game build runs.

This lets your game call Pley functionality as it always does, which the Web Playable out-of-the-box translates to the right behavior when running on Crazy games!

(2) Implementation to support mobile

Optional but recommended.

Crazy Games supports mobile gameplay. Right now, Pley mobile is in a beta state (Android). It is recommended to have mobile web support when going live on Crazy Games. For that two things need to be done:

• (#1) Support mobile input and controls in the web build (including on-screen controls)
• (#2) Change any UI/UX elements that behave differently on desktop/mobile, such as tutorials ("Tap here" vs. "Click").

The standard solution for running web- and mobile games in the same codebase is through conditional compilation. To make the web version of the game work on mobile and desktop, the game must change some of its WEBGL conditional compilation. For many games (especially ones with mouse-only input on desktop), no changes are required.

//Example:
#if UNITY_ANDROID || UNITY_IOS
//Code for mobile behavior
#elif PLEY || UNITY_WEBGL 
//Code for web behavior

//////////////////////////////////////////
//Should be modified to be:

#if PLEY || UNITY_WEBGL 
//Code which should only and always be run on web, such as calling Pley SDK functionality.

if(Application.platform == RuntimePlatform.WebGLPlayer
&& (Application.platform != RuntimePlatform.Android || Application.platform != RuntimePlatform.IPhonePlayer))
//Code which should run on desktop web, but NOT on mobile web.
//Example: Change and hide input from touch controls to keyboard input.

(3) Process to launch

Once your game is ready, you should release it to production through the Game Manager. Then, reach out to us and we will begin the process to launch your game. The process will work as follows:

1. Legal: Distribution agreement update (We will reach out).
2. Your game will be submitted to the Crazy Game's QA team.
3. There will be a round of feedback (must-fixes and recommendations).
4. After critical issues are resolved, the game will go live on crazygames.com
5. As a new game, it will be displayed to users under the "new" category until enough other games are released. Then, it is up to the Crazy Games algorithm to decide if your game should be featured. Games need as many players and as much playtime as possible to be featured.

👍

Launched!

That is it!

Once your Pley web game is launched on Crazy Games, nothing else changes.

• Game Updates will automatically work on Crazy Games.
• Game, asset, or settings changes done in the Game Manager will work on Crazy Games.
• Payments, products, rewarded ads -- all Pley functionality is supported on Crazy Games.
• Analytics will work on Crazy Games.
• Payouts (Ads & In-game purchases) will continue to work the same.

🚧

Account Systems; You and Crazy Games

As part of the Pley <-> Crazy Games integration, Crazy Game's account system is used. Users will login through Crazy Games.

While this will work out-of-the-box for your game, it means that users who login on Crazy Games will not be able to play on your game site (because the Crazy Games account system does not exist there).

It is on our roadmap for the end of 2024 to provide a system for users to link their Crazy Games progress with normal Pley accounts and/or mobile game progress.