Guidelines ReadMe

GamePix Guidelines for Games Developers Welcome, Developer! Please read these guidelines before integrating your game on GamePix.

YouTube Video Tutorials

Check the official playlist for tutorials on integrating GamePix SDKs: GamePix SDK Tutorials.

Audio and Ads Behavior

• Sound During Ads: The game's music and sound effects must be paused while ads are playing. Ensure that audio resumes after the ad ends. GamePix SDK can manage this behavior—refer to the documentation for details.
• Game Pausing During Ads: The game must pause while ads are displayed to avoid disrupting gameplay. Ads should be shown between levels, not during gameplay. Timer-triggered ads are not allowed.

Interstitial Ads

• Placement: Ads should be shown between levels, not during gameplay. Timer-triggered ads are not allowed.
• Frequency: The game should not trigger multiple ads at the same time. Displaying ads too frequently negatively impacts gameplay and quality.

Rewarded Ads

• Clear Disclosure: Before displaying a rewarded ad, the game must clearly inform users about the required action and the reward they will receive.
• Icon Use: Icons can be used to represent actions or rewards, but they must be easily recognizable and understandable.
• User Control: Users must not be forced to interact with rewarded ads; skipping or dismissing them must always be an option.

Click to enlargeClick to enlarge

Audio Handling

• Automatic Pause: The game's audio must automatically stop when an incoming call occurs on a smartphone, when the browser is paused, or when the user initiates a call.

External Content and Links

• No External Links: Games must not contain external links, including "More Games" buttons, social media SDKs, visual links, privacy policy links, "Rate Us" buttons, logos with readable URLs, or any other form of external linking.
• Resource Loading: The game must load resources from a relative path (e.g., <script src="js/game.js"></script>).
• No External Analytics: Games must not include external analytics (such as Google Analytics, Universal Analytics, or Tag Manager). GamePix provides a dashboard to monitor game performance and earnings.
• No External Ads: Games must not include external ads. GamePix provides APIs for ad integration.
• No Third-Party SDKs: Games must not contain third-party SDKs; they must either use the GamePix SDK or be entirely SDK-free.

Game Display Requirements

• Iframe Compatibility: Ensure the game resizes properly to fit the iframe window. It must be tested with at least a 640x480px iframe.
• Loading Screen: Include a loading screen during the initial game load. The GamePix Unity plugin automatically adds one if used.
• No Quit Button: The main menu must not include a quit (X) button.

Content and Compliance

• Unity Plugin Testing: Games using the GamePix Unity Plugin cannot be tested inside the testkit on my.gamepix but must be tested directly in Unity.
• Unity Plugin Submission: The exported output of a game using our Unity Plugin is a .gpx file. When submitting a game, only this file needs to be uploaded.
• No Malicious Code: Games must not contain any malicious code.
• No Explicit Content: Games must not include explicit or suggestive content.
• WebGL Frame Removal: The default "Unity WebGL frame" should be removed from the game.
• Consistency in Naming: The game’s name must be consistent across the namespace and display.
• Quality Assets: The game’s assets (icon and cover) must be representative of the game. These assets are the first contact with users and should be of good quality. The title on the assets must match the game’s title.
• Accurate Description: The game’s description must match the game and provide clear information (theme, mission, characters, how to play). The title in the description must be consistent with the game’s title.
• No System Popups: System popups are not allowed.
• Copyright Responsibility: By submitting a game to GamePix, you assume full responsibility for ensuring that it does not infringe on any trademarks or copyrights. You may be held legally accountable for any violations. Additionally, all images used in the game and for its promotion (banners and icons) must comply with image rights and must not infringe on anyone’s intellectual property.
• Use of Game Templates: If you use a game template to publish on GamePix, ensure that both the code and assets are licensed for such use. Otherwise, you risk committing a legal violation. Additionally, only complete games should be submitted; drafts or demos will not be approved.
• Duplicate Games: If the submitted game is already present in the GamePix catalog, it may not be approved.
• Allow Distribution Option: By selecting "Allow Distribution" when uploading a game to GamePix, the game will also be distributed on third-party services and websites, generating additional revenue. If not selected, the game will be published exclusively on gamepix.com. Some unauthorized websites may still iframe the game without permission, though we take measures to prevent this.

Localization and Cultural Sensitivity

• Multi-language Support: Games can support multiple languages and should automatically display the user’s system language. If the user's language is not supported, the default language must be English.
• No Religious Content: Religious symbols or content are not permitted to maintain neutrality and respect for all audiences. Ensure that the game and its assets comply with this rule before submitting.

Development Best Practices

• Viewport Scaling: Use <meta content="...user-scalable=NO..." name="viewport" /> in meta tags.
• Touch Optimization: Apply -ms-touch-action:none and touch-action:none in the CSS body to enhance touch functionality.
• Device Adaptation: Use window.innerWidth & window.innerHeight to retrieve accurate device screen dimensions across different browsers.
• Handling Rotation: Some browsers do not recognize native rotation change events in JavaScript or jQuery. Instead, use a resize event to detect width and height changes.
• No "Rotate Device" Prompts: Remove any "Rotate Your Device" prompts and allow gameplay in both orientations. This prevents issues when playing on touch-enabled PCs in an iframe. Ensure the canvas is always centered.
• Fullscreen Compatibility: If the game does not fit correctly in fullscreen mode, add a full-background sprite to the "canvas-working-area."
• Pause/Resume Logic: Pause and resume the game when the document's visibility changes. Refer to best practices for managing this behavior.
• Iframe Click Handling: If the game is played in an iframe, prevent it from stopping when users click outside the iframe. The game should only pause when the Page Visibility API is triggered.

Support

For further assistance, contact us at the address below.