Objective
Move from zero-domain prototypes to accepted platform games with platform-managed advertising.
Lead game: Neon Lane Dash
Backup: Upload Limit Panic
This cockpit turns the zero-domain game route into the next concrete actions: which dashboard to open, which ZIP to upload, what still cannot be automated, and what counts as a real progress signal.
Move from zero-domain prototypes to accepted platform games with platform-managed advertising.
Lead game: Neon Lane Dash
Backup: Upload Limit Panic
It is unrealistic to expect verified ad revenue overnight before any platform accepts a game. The fastest honest morning win is submitted/in-review status or a platform reply requesting upload metadata.
Status: ready_for_dashboard_upload / manual_login_required
Next action: Log in to CrazyGames developer dashboard, create a game, upload Neon Lane Dash ZIP, paste the CrazyGames fields from the copy pack, and submit for Basic Launch review.
Why now: Best first moderation signal for a short reflex HTML5 game; the build already has CrazyGames SDK loading/gameplay hooks and hidden external links in platform context.
Use game: Neon Lane Dash
Success signal: Dashboard status changes to submitted, in review, accepted, or live.
Risk control: Do not enable standalone ads; CrazyGames Basic Launch can validate quality before revenue share.
Status: ready_for_dashboard_upload / manual_login_required
Next action: Create a Yandex Games app draft, upload Neon Lane Dash ZIP first, then Upload Limit Panic if the first draft is accepted or in review.
Why now: Second zero-domain catalog with platform ads; current builds include Yandex SDK v2 LoadingAPI, GameplayAPI, and gated ad calls.
Use game: Neon Lane Dash first; Upload Limit Panic second
Success signal: Game draft submitted to moderation or accepted in the Yandex Games console.
Risk control: No external CTA is visible in Yandex context; ad calls require platform readiness and ads=1.
Status: ready_for_email_or_dashboard / email_or_manual_dashboard
Next action: Send the public email with Neon Lane Dash release links, or create the developer portal account and upload the ZIP directly.
Why now: No upfront-cost HTML5 distribution route; current builds include Playgama Bridge, game_ready messaging, pause/audio listeners, interstitial placement, and rewarded-state confirmation.
Use game: Neon Lane Dash
Success signal: Playgama replies with review instructions or dashboard upload accepts the package.
Risk control: Do not call start-of-game interstitial through Playgama; only natural replay/practice breaks are wired.
Status: ready_for_dashboard_after_signup / manual_signup_required
Next action: Open GamePix Join Us, create the dashboard account, upload Neon Lane Dash ZIP, then use the copy pack fields.
Why now: GamePix advertises hosting, QA, partner distribution, and 45% developer revenue share; current builds include GamePix loading/pause/resume/ping lifecycle hooks.
Use game: Neon Lane Dash
Success signal: Dashboard accepts the game entry or requests QA changes.
Risk control: Only documented GamePix lifecycle hooks are integrated; no guessed ad method is called.
Status: sdk_ready_but_manual_legal_gate / manual_form_required
Next action: Use the partnership email first, then complete the web form manually because it has reCAPTCHA and legal checkboxes. Add dashboard gameId later if provided.
Why now: SDK adapter is now present, but the platform requires dashboard gameId and legal consent before full activation.
Use game: Neon Lane Dash
Success signal: Partnership reply, dashboard gameId issued, or SDK activation view passes.
Risk control: No fake gameId is hardcoded; gdsdk.showAd is gated behind GameDistribution context and ads=1.