ForNeVeR/overtone

De-staticify the `GameState`

Open

#110 opened on Feb 9, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)F# (1 fork)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (18 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently, the GameState contains a couple of mutable static fields: https://github.com/ForNeVeR/overtone/blob/421c1129f9efb9ebd30945f114a3dcdd1a4ffa42/Overtone.Game/GameState.fs#L15-L23

We should remove them all. GameState should be an instance type, passed to each concerned entity.

This will allow us to not rely on global mutable effects, helps with things like save games, reproducible gameplay, game replays etc.

Contributor guide

Research direction
Remove all mutable static fields from GameState and convert it to an instance type. Then refactor all code that uses these static fields to receive a GameState instance. This will involve updating constructors, method signatures, and test code.
Tech stack
csharp
Domain
game dev
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
F#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70