Goldberg Who?
Every studio has a production backbone. At The Maple Barrel, ours is a grumpy Discord bot named Goldberg.
I built Goldberg to patch the holes in how our team works. Over time he became the thing that ties our tools together. This post covers why we needed him, what he does, and what he's done for a remote, part-time team making games.
Our unique challenges as a studio
The Maple Barrel is fully remote, and everyone on the team works part time on their own schedule. That freedom is a big part of why people can make games with us at all. It also creates three problems we fight every week: organization, motivation, and siloing.
None of these are solved by working harder. They're solved by making the team's work visible and making the team feel present.
Discord as our third space
We don't have an office, so we needed somewhere online that feels like one. For us, that's our Discord server. It's where we hang out, ask questions, hop into calls, and share work in progress.
Discord also has an open API. That means we can add bots and features for pretty much anything we need. So instead of asking the team to check five different tools, we bring everything into Discord. If someone on the team needs a piece of information, it should be one message or one slash command away.
What is Goldberg?
Goldberg is a Discord bot I created that runs on our production server. I started him to fill specific gaps in our production process. He has since become the backbone of how The Maple Barrel works.
He connects our version control, our sprint board, our team schedule, and our build pipeline, and reports all of it in Discord. Here's what he does, and which of our three problems each feature tackles.
Commit notifications
Tackles: organization, motivation, siloing
This is where Goldberg started. My biggest frustration with most version control is that you don't know when something changed, or what changed, unless you go looking. On a big team, very few people go looking. You can't control that.
I was already hosting our SVN repository on my homelab. So I figured I could host a Discord bot next to it that watched the repo and posted every new commit to a channel.
The effect on the team was bigger than I expected. Everyone can see the game moving forward in real time, even when they're not online together. It's hard to feel like a project has stalled when the commit channel keeps lighting up. And yes, if you commit without a message, Goldberg will call you out:
🔹 New Commit!
🔸 Project: Minimum Mage
🔸 Revision: 1042
🔸 Author: michael.kirkpatrick
🔸 Date: 2026-10-14 23:52:07 -0400 (Wed, 14 Oct 2026)
🔸 Message: Left the message field blank, just like your soul.
Office hour reminders
Tackles: motivation, siloing
Every member of The Maple Barrel hosts a one-hour office hour each week. For that hour, they sit in a Discord voice call and are available to anyone.
This does two things. First, it makes sure the whole team has regular, predictable access to each other, so questions get asked instead of sitting in someone's head. Second, it keeps the server feeling alive. Logging on and seeing a teammate in a call is a lot more motivating than an empty server.
Goldberg reads the team schedule, reminds hosts when their office hour is coming up, and announces to the team when one starts. He also answers /officehours and /schedule for anyone who wants to know who's on. Naturally, he does it with attitude:
Put down whatever you're doing that definitely isn't work.
🕐 Office Hours are starting NOW.
@Michael (Michael Kirkpatrick) has graciously agreed to field your questions.
📅 Every Tuesday at 7:00 PM EDT
Don't waste their time. Or do. I'm a bot, not a cop.
Scrum integration
Tackles: organization
We run sprints like a traditional agile team. The sprint board is our source of truth for what's been done and what's left to hit the sprint goals. The hard part is getting people to keep it updated while they work.
Goldberg connects to our sprint board in Taiga. Three days a week, at set times, he DMs each person the tasks they still have open, along with a banner showing what day of the sprint it is and when it ends. Early in the sprint the tone is a gentle nudge. Past the halfway point, it gets more urgent:
Final warning before the sprint closes: ship these or explain yourself at retro. Your call.
🗓️ Day 13 of 14 · deadline Friday, October 16 (1 day left)
Anyone can also run /my_tasks to see their assigned tasks, or /sprint_board to see the whole board.
Auto builds
Tackles: organization, motivation
Rapid playtesting and consistent builds are a cornerstone of scrum. You can't review a sprint if nobody can play it.
Our builds run automatically. When a build fails, the errors get posted straight into Discord, so the right person sees it without anyone digging through logs. When a build succeeds, the team can grab it with /builds, which links to the latest playable build of every project on the Goldberg web app.
Bullying the team
Tackles: motivation (honestly)
A useful bot is good. A bot with a personality is better. I wanted Goldberg to feel like a member of the team, and a sarcastic one felt right. It's fun for a team to have a shared enemy.
So Goldberg roasts people. He replies with insults in certain channels, fires back when someone says his name, and needles anyone who leans on him too much:
At this point, I'm doing more work than you.
It keeps the server lively and gives people a reason to show up. When a conversation needs to be serious, /shutup mutes him for a while, and /wakeup brings him back.
One place for everything: the Goldberg web app
Tackles: organization, siloing
Goldberg isn't only a bot. He also has a web app, and it's become our central source of information.
The biggest piece is our custom wiki. Most wiki tools we tried were bloated and hard to keep up to date, and an out-of-date wiki is worse than none. So we built a lightweight one into the Goldberg web app, shaped around how we actually work. The web app also hosts our game builds and project data that Goldberg pulls into Discord.
/documentationlinks to the wiki/repogets you set up with the SVN repository/buildslinks the latest playable builds/helplists everything Goldberg can do
A new team member can go from joining the server to finding the docs, the repo and a playable build without asking anyone.
What Goldberg taught us
Goldberg started as a multiweek-long project to fix one annoyance: not knowing when someone committed. Since then, every time we've spotted a gap in how our remote, part-time team works, Goldberg has grown to fill it.
If you're running a small remote studio, here's the takeaway. Your tools don't need to be fancy. They need to live where your team already is, and make the work visible without anyone having to go looking. For The Maple Barrel, that place is Discord, and the one making the work visible is a bot who thinks we're all a bit lazy.
He's probably right.