[breville]

[written by Claude]

Summary

A new block, set X as player 2, makes a sprite a second platform player, moved with W, A, S and D while the first player keeps the arrow keys, so two people can play on one keyboard. It falls, lands and jumps like the first player, under the same gravity. A player 2 block refers to it the way the player does, so events can tell the two apart. Both blocks are in the toolboxes and in the free-play level's Discover blocks catalog.

Captures

Recording

Screen.Recording.2026-11-05.at.11.03.26.PM.mov

Code

Catalog

Key changes

• setAsPlatformPlayer2 and thePlayer2 block definitions. One builder in makePlatformPlayer writes the key handlers for both players, so the two sets cannot drift; the new block's runtime half calls it with W, A, S and D and the second group.
• The player groups live in playerGroups.ts, shared by the engine and every block that names one.
• The engine's player commands take a group: setPlatformPlayer and platformJump default to the first player's. Gravity, footing and landing apply to both groups; the sounds, objectives, jump event and camera still follow the arrow-key player, and the progress report does not count the other player as something touched.
• The two blocks join the complete toolbox, the Platform toolbox additions, the free-play level's toolbox, and the block catalog's help.

Testing

Unit tests for the new block's generated code and its key wiring, for the first player's keys staying its own, and the existing suites for toolboxes, catalog help, image references and the engine's helper code. Checked in the browser as a test student on the free-play level with a two-player program, reading sprite positions from the running game: holding A moved player 2 left and off its ledge while player 1 stood still, holding the right arrow moved player 1 while player 2 stood still, W jumped player 2 alone, and the up arrow jumped player 1 alone.