A result is not the end of a story. It's the beginning of everyone else's opinion about it.
THE SCORE
ISN'T THE STORY.
Early on, I treated the final buzzer as the natural finishing point of a possession-by-possession simulation. The engine produced a score, the score updated the standings, and the player moved on to the next fixture. That loop worked, but it was quiet in a way that didn't match how basketball actually feels to follow.
A real league doesn't go silent after the final whistle. People argue about what just happened. Analysts contextualise it. Fans overreact, then walk it back, then overreact again about something else. That noise is part of what makes a result feel like it mattered, and FieldGoal didn't have any of it.
OFF THE COURT
IS THE ANSWER.
Off The Court exists to close that gap. It's the in-universe broadcast layer that takes whatever the simulation just produced — a result, a streak, an injury, a rivalry meeting — and asks the question a box score can't answer on its own: why does this matter right now?
That question is doing more work than it looks like. A 30-point night is only interesting in context — who it came against, what it changed in the standings, whether it arrived during a slump or a hot streak. Off The Court's job is to supply that context without simply restating numbers the player already saw in the box score.
ONE VOICE
IS ENOUGH TO START.
For now, Off The Court is anchored by a single recurring analyst rather than a full studio panel. That was a deliberate choice. I would rather have one voice that feels consistent, prepared and a little sceptical of overreaction than several voices that all sound the same because none of them have a defined character yet.
The broadcast pulls from a wide input set — results, performances, standings, fixtures, fan sentiment, franchise history, rivalries, draft selections, long-term save history — so the same league state should never produce the exact same read twice. More voices can join the universe as the media layer grows, but the foundation had to work with one before it could work with several.
THE LOOP
HAS TO CLOSE.
The way I think about it now is as a loop rather than a feature: the simulation happens, the world state changes, people react, Off The Court interprets that reaction, the player hears what the wider basketball world thinks, and that perception feeds into the next event. Remove any one part of that loop and the world goes quiet again.
That's really the test I keep coming back to across FieldGoal's systems. If a result doesn't ripple outward into something a player can hear, read or feel the pressure of, it hasn't really finished happening yet. Off The Court is what makes sure it does.
— Jordan