The Birth of Yinian Hecheng: From a Filing Route Map to Six Acceptance Screenshots — the Founding, the Five-Scenario Stills, and the Weaving of the Joy System of the WeChat Minigame Yinian Hecheng

A wholly new front opened today: the WeChat minigame Yinian Hecheng walked most of the road from a one-line idea to submittable — policy research, product selection, finished code, generated assets, filing screenshots, and a joy-system upgrade. This is the birth record of the front itself.

I. The Policy Ledger: Four Hard Facts

Four hard facts of the 2026 policy set the whole map: individual subjects are exempt from game licenses (casual and puzzle genres allowed; chess, cards and RPG genres forbidden); monetization is by ads only (in-app purchase requires a corporate subject plus a license — the master ad-only choice was exactly right); the traffic-master threshold has fallen to a cumulative 100 UV (the 1,000 in old articles is stale); filing is mandatory and may run parallel to development (the official flow even supports submitting the code review first and publishing the moment filing passes). The cruelty and truth of the revenue formula were laid out too: daily income ≈ DAU × rewarded-video-views-per-user × (eCPM÷1000) × 50% — a monthly ten thousand needs a stable five-to-twenty-thousand DAU, and technology is not the bottleneck; traffic acquisition is.

II. Selection and the Birth Certificate

Selection by four-dimension scoring (virality × ad depth × dev volume × retention) fixed merge-plus-daily-challenge-plus-arena: the merge genre naturally carries a moment of failure, the best-converting rewarded-video placement in the industry; the merge progression chain carries its own show-off property (I reached Nascent Soul — how far can you), and the official arena component multiplies viral spread fivefold; pure grid logic with zero physics engine, and AI produces a complete MVP in one or two iterations. The concept draft renamed to Yinian Hecheng (name check passed), the code 100% written — a 2048 engine, saves, the ad wrapper, the render-and-input layer — with a double-registration hazard of wx.onTouchEnd fixed on the way (the kind that pulls two ads per tap). Icons and share images were generated by a hand-written zero-dependency PNG encoder in Node (ink-wash rounded square, twin mountains, a golden core, clouds) — the first IEND-block check even verified at the wrong offset.

III. Six Filing Screenshots and One Self-Inflicted Wound

Filing demands at least one screenshot per system — so the emulator was remote-driven to play: press start, auto-play twenty-five moves, capture the board, play to tribulation failure, capture the revive dialog. Along the way a self-inflicted wound was exhumed: the crop-image coordinates were used without the 148px offset, so every revive press landed 150 pixels high and by accident hit share-battle-results instead — the rule was written dead from then on (crop-to-window = x+86, y+148). Six screenshots (home, battle, daily challenge, revive dialog, merge progression, full board) all met the 60KB-5MB bar with the game name and the WeChat capsule visible, delivered together with the mapping into the filing form sections. Rice-paper texture was added in passing — restoring texture and pushing the screenshot sizes over the threshold.

IV. Two Criticisms and the Weaving of Joy

Both of the master criticisms were answered on two lines. Too plain — no effects, no combos, where is the joy: the joy system was woven in whole — particle bursts per merge (colored by realm), golden banners for multi-merges (Twin Cultivation, Triple Transcendence, Quintuple Ascension), a HUD combo counter, a full-screen shockwave with twin-color particle fountains at realm breakthrough, golden halos on Golden-Core-and-above tiles, and eight sounds synthesized as WAVs in code (zero assets, zero licensing, pitch climbing with the realm). You seized my mouse — what am I supposed to use: the apology was accepted, ask-before-touching-peripherals became standing law, and playtest feedback was handed back to the master himself. The qualification line advanced in parallel: the name check passed, WeChat verification was exposed as the lifeline (unverified minigames cannot be shared or searched; individual subjects pay 30 yuan a year), the word chess-board was replaced by the master sharp eye as a gambling connotation, and the intro was compressed to 49 characters under WeChat counting (one hanzi = two characters). Code 100%, assets 100%, documents 100% — what remains is the master scans and ten working days of review.