factory_OS & Brand Building

I’ve spent days—literal days—building, tearing down, and rebuilding a core system of streamer.bot actions. Over and over again. Tweaking, tuning, ripping out broken pieces and reinforcing what works. It’s a cycle. But it’s getting cleaner each pass. Right now, I'm on version 3, and I’ll be honest—I’m proud as hell of it.

This build? It doesn’t rely on any of the built-in command system inside streamer.bot. None. It parses every chat message raw, checks for !command inputs, and only then formats it into something usable. No clutter, no hand-holding. Just raw input and clean parsing.

Everything is run on variables. It makes the whole thing extremely fluid. Yeah, that opens doors for future bugs—but right now? It runs like butter. Any command I’ve created works straight out of the box. And every one of them lives in simple text files.

!lurk gets sent.
Bot reads a random line from command\!lurk.txt.
Sends the reply.
That’s it. Smooth. Modular. No UI digging required.

I can edit replies by changing a text file. I can add entire new commands just by dropping in a new file—no streamer.bot rework needed. Unless I’m building something complex with sub-actions, it’s all plug-and-play.

Next Objectives:

Now that the base system’s functional, next up is the Moderation Suite. I want this bot to handle AutoMod duties and log its own behavior outside of Twitch’s mod tools. I want full transparency—every action it takes, I want tracked. Logged. Archived. My tools, my logs, my control.

Beyond the Bot – Brand Construction

Outside the backend, I’ve started dipping my feet into building the wider brand. First came the website. Then Instagram. If all goes to plan, the rest of the platforms should follow before this week’s out.

The idea is simple: a full-stack brand ecosystem. Multi-platform presence. Everything feeding the same fire.
Right now, there’s not much in the system—but that’s fine. You’ve gotta start somewhere.

And I’ve already started.