Skip to main content
A coding window is the panel of buttons beside the video in MatchCoder. This page lists everything a window’s buttons can ask MatchCoder to do. Use it when you build a window yourself, or when you ask Ask Framesports to build or change one and want to know what is possible.

How does a window talk to MatchCoder?

A window’s buttons call matchCoder, an object MatchCoder puts in every window. Each call below is written the way a button uses it, for example matchCoder.addEvent({ category: "Tackle" }). Ask Framesports works from this same list, so anything here is something you can ask it for. On a match you can only watch, the calls that change codes are refused, and the window says why.

Making codes

These calls cover making codes.

Changing codes

These calls cover changing codes.

Rules the editor runs

These calls cover rules the editor runs.

Reading the match

These calls cover reading the match.

The timeline and the editor

These calls cover the timeline and the editor.

The video

These calls cover the video.

Keys

These calls cover keys.

Places and boxes

These calls cover places and boxes.

Kept values

These calls cover kept values.

Frequently Asked Questions

Can one button make two codes? Yes. Use matchCoder.addEvents for two codes from one press, or matchCoder.setLinkedCodes so a code always brings another with it, however it is coded. See Rules the editor runs above. Can a row cover the whole match, like pitch zones or possession? Yes. matchCoder.setWholeMatchRows keeps that row’s codes end to end from the start of the match to the end, and matchCoder.rowGaps shows any part left uncovered. Does Undo take back what a window did? Yes. A press, and every code its rules add or move, comes back with one Undo.