Scripting

Pink Demo's main logic is in assets/scripts/ClickGame.ts. It binds existing scene UI nodes, with a recovery path for missing nodes. The normal gameplay path registers clicks, updates the score, moves the target through fixed positions, and resets the game.

Initialization, click handling, and reset are separate methods to inspect

Development workflow

1. Locate ClickGame.ts with Quick Open.
2. Read the relationships between start(), onTargetClicked(), and resetGame().
3. Watch type checks and the Problems panel while editing.
4. Save and wait for language services and COCOS compilation to update.
5. Run main.scene and verify the score cycle 0 → 1 → 0.

Checks after editing

Search all references before changing TARGET_POSITIONS or an asset path.

Find definitions and uses before changing routes or asset paths

Check for duplicate event registration, node-validity checks in asynchronous asset callbacks, and restoration of score, position, and scale on reset.

TARGET_POSITIONS is deterministic. Keep its order stable when adding positions and check modulo indexing. For onTargetClicked(), test the immediate state update, movement after the animation, and repeated rapid clicks. For resetGame(), confirm that an old tween cannot move the reset target again.

APIs and versions

Use APIs for the project's declared COCOS version. Pink Demo's prerequisite is listed in First AI change.

• COCOS Creator manual
• COCOS Creator API

PinK extension APIs and game runtime APIs are separate. Do not import internal editor APIs into game scripts.