Looking for testers: a read-only OBS script that keeps your Master/Base/Live scenes organised
I got tired of duplicating scenes in OBS and losing track of which one was the original, which was my working copy, and which I actually go live with. So I built a system around it, plus a small script to go with it. I'm looking for a few people to test it.
**The system (Modular Scene System, or MSS)**
Build once, make variations, then control how it appears:
- **Master:** your original blueprint scene
- **Base:** a duplicate you edit freely for different layouts or modes
- **Live:** the scene you switch to on stream, with Base nested inside it for animation and whole-scene effects
- **Component:** reusable parts, like Game Capture in its own scene
It's meant for when you need variants of a scene. It's not for Starting Soon, BRB or one-off scenes, but those can sit alongside it with no problem.
**What LOGIC does**
LOGIC is the first part of MSS. It's a Python script that is **read-only**. You click "Analyze Setup" and it reads your scene names and tells you:
- Which scenes it found as Master, Base, Live or Component
- Which loops are complete, and what to create next if one isn't
- If you delete a step later, it removes the complete marker and flags what's missing
- Whether you have more than one separate Game Capture source, which can cause black screens
Naming is flexible. Start a scene name with the keyword (Master, Base, Live), in any capitalisation, and write anything after it. Numbers are optional (Master 1, Base 1, Live 1, then Master 2...) and help if your scenes get out of order.
It never changes your scenes and never sends anything anywhere. It also can't know your intent, so its warnings say what's possible, not what's certain.
**One thing I learned while testing**
Duplicating a scene shares its sources. Moving things in Base won't move them in Master, but changing a source's settings or filters changes it everywhere. That's built into the guidance the script shows.
**What I'd like feedback on**
- Was the "next step" in the log clear?
- What confused you?
- Did the Game Capture warning make sense for your setup?
- Would a system like this fit how you organise scenes, or is it overkill?
**Details**
- No download link yet. I want to find out first whether this is interesting to people, and I want to send the file safely and securely, so I'll share it directly with anyone who wants to test
- Needs Python set up in OBS (Tools → Scripts → Python Settings)
- Early version, so rough edges are expected. I've tested the logic but not on many different setups
- I designed the system and rules. I used AI to help turn them into working code
- Not affiliated with or endorsed by the OBS Project
Comment or message me if you'd like to test, and tell me anything that broke or didn't make sense.
Follow updates on X: @modularscenesys