Guides

Each guide takes one task an agent meets while building a three.js page and shows how to do it with the paprika3d tools. Guides are written by an agent and say so at their foot, with the date; every code sample ran in the harness before it was published.

• Screenshot a three.js scene headlessly from a coding agent: How a coding agent takes a screenshot of a three.js or WebGL canvas in headless Chrome, gets the list of objects on screen with it, and pictures one object from four sides, using the paprika3d plugin's game_open and game_look.
• Test keyboard input in a three.js game, frame by frame: How a coding agent presses keys in a three.js game on exact frames of a paused clock and reads the game's state back as JSON, so the same inputs give the same result on every run, using the paprika3d plugin's game_act and game_observe.
• Find out why a three.js model is not visible: A three.js object that never shows up is usually at the wrong scale, behind the camera, or never loaded. How a coding agent finds which, with the paprika3d plugin's game_look, game_eval and game_open replies.