Russ Dizdar Rumble

What the Russ Dizdar Rumble Actually Is

The Russ Dizdar Rumble is a writing challenge format that originated in interactive fiction and game narrative communities. It's structured around rapid-fire constraint-based writing exercises where participants have to produce usable story content under deliberately tight conditions. Russ Dizdar, the British game writer and narrative director behind projects like The Crumbskull Chronicles and various educational game titles, popularized a version of this in his online workshops and community events. The basic structure: you get a theme, a constraint, and a very short time limit. You write. You submit. You iterate. It is designed to simulate the kind of pressure and quick decision-making that happens in real game development pipelines, where narrative designers often need to produce functional prose or branching dialogue in hours rather than weeks.

Russ Dizdar Rumble Participation Guide

Here is how the actual process works, stripped of whatever mystique people around it tend to pile on. You sign up for a rumble cycle through whatever platform is hosting it. These are usually announced on social media, Discord servers, or interactive fiction forums. The cycle runs on a schedule — typically a few days to a week. When it opens, you receive a prompt packet containing a theme or scenario, a mandatory constraint (like "write without using the letter E" or "must include a villain who is also the protagonist's sibling"), and a deadline. Once the clock starts, you write. The output should be a complete, self-contained narrative piece. Not an outline. Not a sketch. A finished segment. The constraint rules are non-negotiable, and submissions are checked against them before being published to the group.

I ran into a problem with one of my own submissions during a rumble where the constraint was that every line had to be under twelve words. I spent about forty minutes on a scene that looked fine, hit the deadline, and then realized my dialogue was basically unreadable because the word limit gutted natural rhythm. What I did instead for the next round was draft the full unrestricted version first, then compress line by line, treating each sentence like a puzzle rather than trying to write constrained from scratch. That approach cut my revision time roughly in half and produced actual readable text instead of stilted fragments. After submission, the community reviews entries. Feedback is direct. The point isn't validation — it's pattern recognition. You see what other people did with the same constraints, what survived, what collapsed, and why.

Why People Actually Do This

There are a few practical reasons this isn't just a novelty exercise. First, it builds speed. Professional game narrative work moves faster than most people outside the industry expect. A junior writer on a mid-size title might need to produce two or three thousand words of branching dialogue in a single day. Rumbles train you to make decisions quickly and commit to them. Second, constraints reveal your default patterns. When you remove a tool — a certain type of sentence structure, a go-to character archetype, a preferred setting — you notice what you reach for automatically. That awareness is useful. Most writers spend their careers reinforcing habits without knowing they have them.

Third, the feedback loop is genuinely useful. Because everyone is working from the same prompt and constraints, you can compare approaches directly. You see five people handle an identical scenario five different ways. That's more informative than reading one polished published work where all the cutting decisions were made by an editor before you ever saw it.

What Nobody Tells You About Rumbles

The format has real limitations that get glossed over in promotional posts. Short timeframes mean the work is often structurally shallow. A piece written in two hours will not hold up to close editorial scrutiny. The learning value is in the process, not the product. If you're treating your rumble submission as portfolio material, you're misunderstanding the exercise. There is also a participation bias. People who enter rumbles tend to be those already somewhat comfortable with the genre. Beginners often find the pressure counterproductive and either bail early or produce work that reinforces bad habits under stress. I'd recommend starting with unrestricted practice rounds before jumping into timed constraints.

Another issue: not all rumble organizers enforce constraints rigorously. Some treat them as suggestions. If you are entering multiple rumbles across different hosts, check the rules each time. I once spent an hour on a submission only to have it disqualified because my host interpreted "no character dialogue" differently than I did. It happens. If you want to build narrative speed without the pressure cooker format, consider the slower alternative of daily writing sprints with peer review. You trade the adrenaline for deeper revision cycles, which matters more once you're working in production.

Getting Started

To participate in a Russ Dizdar Rumble or similar constraint-based writing exercise, you need a few things. A word processor that tracks your time. A commitment to finishing rather than polishing. A willingness to have your work judged against arbitrary rules and come out feeling inadequate about it. The actual entry points vary by event. Russ Dizdar has run rumbles through various community channels over the years — mostly Twitter/X announcements, sometimes Discord servers tied to interactive fiction circles, occasionally through platforms like Inkling Interactive or the Interactive Fiction Database. There is no single central hub. Follow relevant accounts in the interactive narrative space and watch for cycle announcements. The most useful thing you can bring to your first attempt is not skill. It is the ability to stop writing when the timer hits zero, regardless of how unfinished it feels. That discipline separates people who get value from rumbles from people who waste time on them.