STREAMING GUIDE / CREATOR PROJECTS

Subathon Timer not updating in OBS: fix the display first

Separate an OBS display problem from Twitch event delivery. A controlled local time change is the fastest useful first test.

START HERE

Pause the timer, set a short exact time locally, and watch the intended OBS text source. If local commands do not change it, check the source name, selected scene, and WebSocket connection before changing Twitch settings. The source must be a direct item in the scene the timer searches.

Make a local test without spending Bits or subscriptions

These checks cover Maskarauder's Windows Subathon Timer and the source revision linked below. Note the current remaining time before experimenting; use a rehearsal scene outside a live broadcast. The setup page covers first installation.

  1. Start OBS and the timer, then finish Twitch authorization if requested.
  2. At the timer's terminal prompt, enter p to pause countdown.
  3. Enter s, then enter 00:02:00 at its follow-up prompt.
  4. Confirm the intended OBS source displays two minutes. Enter 30 and check that it becomes two minutes thirty seconds.
  5. Enter r and verify countdown resumes.

If this works, the local command-to-display path works. If a Twitch event still does nothing, move to the event delivery guide instead of rebuilding the OBS source.

Check what OBS is actually displaying

Use a Text (GDI+) source on Windows. Open its properties and confirm its text contains only a time value such as 00:02:00. Keep a heading like “Time remaining” in a separate source; decorative words in the clock itself can prevent parsing.

Disable Read from file for this source. OBS's file-reading mode displays file contents instead of the text property that this timer updates. If the property changes but the image does not, also check source visibility, transform/cropping, text color, and whether another source covers it. A connection fix will not make off-canvas text visible.

Match both the source and the scene

In the timer's config.py, OBS_SCENEITEM_NAME must match the OBS source name, not its displayed text. Source names are compared exactly. OBS_SCENE_NAME = None tells this revision to search the current program scene when it connects; the preview scene in Studio Mode can be different.

The reviewed implementation searches the selected scene's direct items. For a clean test, place the clock directly in that scene rather than hiding it inside a group or nested scene. If using a named scene, enter that exact scene name in OBS_SCENE_NAME, restart the helper, and repeat the paused time-change test.

After renaming a source or changing scene collections, check the configuration again. Do not create several almost identically named clocks as a workaround: it becomes difficult to tell which one is being updated.

Distinguish pause, completion, and connection failure

What happensWhat to try
The exact-time command works, but countdown is stationaryEnter r to resume. Use the terminal p/r controls for deliberate pause and resume rather than relying on source visibility.
The clock reached zeroSet a positive test time and resume. Do not treat a completed countdown as a disconnected server.
The console repeatedly reports connection failureUse the WebSocket checklist and verify source/scene lookup as well as credentials.
Changes appear in a different clockCheck the OBS instance, scene collection, exact source name, and launched application folder.

Rehearse the scene changes you will use live

Once the small test passes, restore the intended time and visit the starting, main, break, and ending scenes. Use p and r explicitly when a scene change should pause or resume countdown. In the reviewed version, hiding or showing the source may stop controlling pause after terminal commands have been used; test the displayed time rather than assuming the visibility icon controls it. When reusing it across scenes, use the existing source rather than assuming a newly created text source is the same clock.

Close duplicate timer processes. Keep the chosen application folder writable and edit its own configuration. Before reporting a bug, collect the timer version, the source's exact name and type, the configured scene, and whether the paused s test worked. Share a sanitized error excerpt rather than the whole configuration or user_token.json. This checklist follows source behavior; it is not a claim that every scene arrangement has been hardware-tested.

Sources & version notes

Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.