In the most literal terms possible, how does the steam client decide if a game is running?

[iHateTheMetricSystem]

Obviously steam is a client that runs on its files that you download and install. Which group of files or string of code in a file determines the framework that sums to the steam library showing the green text for a game saying it is running? Many might know that steam will not allow its client to record two instances of a game running even if the first instance is a phantom record. If an answer could be provided (or at least a direction given for me to follow) I plan on correcting the glitch where steam believes I am running a game even with no processes in the background or foreground that says I am. This direction I am taking is a very strict and literal alternative to the solution where one restarts steam or his or her desktop or laptop. I understand I am asking for developer-level insight but I am firm in my belief that it does no harm to ask and receive no answer. Please be aware that I fully understand how picky I am being and how unlikely I am to receive an answer that satisfies my conditions but I am willing to have this post in the books incase someone has an answer.

[Darren]

When whatever processes the developer connects to the Steam API are running.

This can be launcher, main process, launcher and main process, or even a tertiary process solely for DRM verification.

[iHateTheMetricSystem]

Originally posted by Darren:

When whatever processes the developer connects to the Steam API are running.

This can be launcher, launcher and main process, or even a tertiary process solely for DRM verification.

Is it recorded anywhere readable which processes these are for a game?

[Darren]

None that I am aware of because as I said it varies for every game.

Stellaris is just the main game.

Elder Scrolls Online includes the launcher.

If the overlay is support it has to at least be on the main game.