GML language tutorial practice on your own GameMaker scripts

What PixelTread can do for your project

• Filesread_file, write_file, edit_file, grep, glob and list_dir work in the chat's working folder, which should be your project, and a counter shows how many files were created, edited and read.
• Shellruns your build or test command and judges success by the real exit code, not by a claim. Dangerous commands are blocked, and the output is on the card.
• Webweb_search and http_get read the official GameMaker manual and its function reference for GML, so the agent can quote the function names it uses in the chat.
• Screenshots and imagesocr reads text from a saved screenshot, such as an error message from the editor, and gen_image saves image files that you can review and keep.
• Orchestrationtask runs parallel sub-agents on separate files, run_on_model sends one hard step to a bigger model, and skills hold reusable playbooks for jobs you repeat.
• Approval modesAuto-run acts at once, Ask first pauses before actions that change something and shows the diff, and Plan only writes a step list and runs nothing.
• Cronruns a saved prompt on a schedule, for example a weekly look at your build log for the first error, so a routine check needs no typing.
• Modelsconnect a cloud AI provider, a model running on your PC, or the built-in model, and press the Test button to check an endpoint before you start a chat.

Four tasks, step by step

Attach one object to another

You want to make objects stick to other objects, such as a hat that follows a character. Tell the agent which two objects you mean and where the hat should sit. It uses grep to find where both are created and read_file to open their scripts. Then edit_file stores the target instance in a variable and sets x and y from the target plus an offset in the step code. A card shows each change. Small edit. In Ask first mode you read the diff, accept it and play the room to see whether the hat stays on the head while the character moves. If it lags by a frame, ask for a second pass. Keep the old version in your folder until you are sure.

Accept any number of arguments

A script with unlimited arguments needs argument_count and the argument array, which GML provides. A typical gml tutorial shows the idea once, but your own message script has its own callers. Ask the agent to read the script and every call with grep, then to rewrite the function so it loops over the arguments it receives. The edit_file card shows the diff, and Shell runs your build command so you see the real exit code. Every caller stays visible. Review the diff, check that each old call still passes its values in the same order, and run the game once before you accept the change.

Plan a short cutscene

Beginners often ask how to make cutscenes, and one answer is a small state machine in a controller object: a state variable, a timer and a script for each step. Start in Plan only mode, where the agent writes a step list and runs nothing. Read it, change the order if you like, then switch to Ask first so the agent creates the script with write_file and edits the controller with edit_file. You decide at each card. Finally, build, play the scene from the first frame and compare what you see with the plan you approved.

Fix jitter from fractional positions

A common cause of jittery movement is noninteger values that are drawn at fractional positions. Ask the agent to find the drawing code with grep for draw_sprite and to read the movement script with read_file. Then edit_file rounds the position before it is drawn and shows the diff. Shell runs your build command and reports its real exit code. Easy to read. In Ask first mode you accept the change line by line, run the game, walk back and forth for a few seconds and watch whether the sprite still shimmers. If it does, the next card can look at the camera code. Either way, the card keeps a record of what changed.