Guide · Cockhero craft

How to Pace a Cockhero Session

Cockhero pacing is the sequence of jobs you give the player. Rate matters, but so do pattern complexity, sustained duration, recovery, and the number of things competing for attention.

That is why “make every round faster” stops working. The session gets numerically harder while its shape gets flatter. After a few rounds, the next move is already obvious.

Build the session as a progression of readable demands. Give each round a baseline the player can learn, change one main variable at a time, and use contrast so the finish has somewhere to go.

If you need the tools, layers, and render sequence around this job, start with the complete Cockhero workflow.

Map the session before the timeline

Do not begin with seven songs and hope they become seven rounds. Begin with seven player jobs.

For every round, write five fields:

1. Purpose: what this round contributes to the complete session.
2. Baseline: the pattern or instruction the player learns first.
3. Change: the one main pressure you add after the baseline is clear.
4. Recovery: how the player gets relief, resets, or prepares for the next demand.
5. Handoff: what the player needs to understand as the next round begins.

Replace fast song / hard clips / faster beat with a playable sequence: establish an even pattern / add two short double-time phrases / return to baseline / stop cleanly. The second row describes an experience you can build and test.

The map forces a useful decision before editing begins: where does the difficulty actually come from? If every row rises on every dial, the session has no room to breathe. If no row changes, the rounds are different files rather than a progression.

Use five pacing dials

Track difficulty across five separate controls.

Rate

Rate is how often the cue asks for an action. It is the most obvious dial and the easiest one to overuse. A higher rate can make a passage more demanding, but it cannot give the round an identity on its own.

Start from a verified timing map. The beat-grid guide explains how to count the music, anchor the grid, and diagnose offset or drift. This page assumes the event positions are already right.

Pattern complexity

Complexity is how much the interval pattern asks the player to predict, remember, or recover from. An even pulse is simple. A repeated grouping introduces a grammar. An irregular pattern asks for more attention even when its average rate stays the same.

Teach the grammar before you test it. Repeat a pattern long enough that the player can recognize its return, then vary it briefly. A difficult pattern should feel intentional, not like a timing error the player is expected to decode.

Duration

Duration is how long the current demand must be sustained. A simple pattern can become the hardest section in a round when it holds long enough. That gives you an escalation move without adding denser cues or a new rule.

Keep the meter clear through sustained passages so the duration remains the challenge. A player who loses an ambiguous pattern is testing the interface instead.

Recovery

Recovery carries the player from one demand to the next. It can be a clean stop, a lower-demand bridge, a return to the known baseline, or a short instruction window before the next round.

Decide what the recovery is for. A reset should clearly end the previous job. A bridge should preserve momentum without smuggling in another challenge. A fake break can be part of a game when the deception is the intended rule rather than an accidental ambiguity.

Attention load

Attention load is everything the player must process besides the pattern: instructions, captions, state changes, score rules, visual density, or a new cue language.

Do not spend all of it at once. A pattern change and a paragraph of instruction should not arrive on the same beat. Let one land, then the other. Confusion is not a higher difficulty tier.

Our working rule is simple: change one main dial, or two when their relationship is the point. Max all five and you lose the ability to tell which decision worked.

Give each round one readable identity

Name the round in one useful sentence. “This is the endurance round” guides the edit. “This is round four” does not.

Build that identity in four moves:

1. Establish. Let the baseline become recognizable.
2. Vary. Change one main dial while the baseline is still in memory.
3. Return. Reestablish the known job or signal that it is over.
4. Hand off. Prepare the next state before the next round asks for it.

The return is optional, but it is a strong diagnostic. If a variation never resolves and the next round begins with another variation, the player has no stable reference for what changed.

Community preferences vary sharply here. In one long Milovana creator discussion, participants reported liking music-related patterns, visible advance cues, steady endurance, narrative goals, or a broadly rising challenge. Others criticized patterns that felt random or needlessly fast. One participant explicitly marked their own preference as subjective.^[1] There is no single preferred round. There are recurring failures in clarity and intent.

Build a readable beatbar so the player can see changes before they arrive.

Show a change before it becomes due. The exact visual treatment belongs to the beatbar, but the pacing decision belongs here: the player should not discover a new job only after missing its first events.

Choose an arc shape

Choose the shape by asking what should create difficulty next.

Rising staircase

Each round raises one or two dials and establishes a new baseline. This gives the finish a clear destination, but a repeated same pattern, faster step becomes predictable long before the runtime ends.

Wave

Demand rises, pulls back, then returns in a changed form. Preserve one challenge, such as complexity or attention load, while reducing another. The pullback should change the player's job rather than merely insert a weaker song.

Endurance plateau

The session reaches a stable demand and holds it. Difficulty comes from duration and consistency. This shape needs especially clean cues because small interface errors repeat for a long time.

Game-like branch

Rules, choices, modifiers, or success states change what a later round means. Progression comes from consequence rather than speed, so each branch and state must be legible.

These shapes describe player demand. The footage can follow a different visual intensity arc. A recovery round may use visually charged material while asking for a simpler pattern, or the visual edit may pull back while the player sustains an endurance job. Keep the two plans coordinated, not collapsed.

Place edges and the finish

An edge round should use language the session has already taught. Reuse the known target, stop state, and transition warning. Raise the stakes through timing, duration, or instruction instead of debuting an entirely new interface when the player's attention is already committed.

There is no evidence here for one correct number of edges. Decide what each one changes. The first might prove that the stop state is understood. A later one might shorten recovery or add a bounded push. If two edges have the same setup, job, and release, one of them is probably occupying time rather than directing it.

The finish needs a clear contract. Tell the player whether the session ends in climax, denial, a countdown, or another defined outcome. Then make the final state unmistakable. A finish should collect the session's grammar, not ask the player to read a new rule at the last second.

Community reports support the value of bounded demands and advance notice, but not a universal formula. In feedback on Cock Hero: Innocence, one viewer praised very fast passages because they were short, then asked for beat changes to be announced before they began.^[2] Treat that as one concrete playability report. The transferable test is whether a demanding section is bounded and whether the player can see the boundary coming.

A worked 24-minute session

This map is an example, not a prescription. Its purpose is to show different sources of difficulty inside one coherent plan.

The rate does not rise in every row. Round three increases complexity. Round four increases duration. Round five pulls the rate back and adds short variations. The edge and finish reuse cue grammar that the opening already explained.

You can use the same method with a shorter or longer runtime. Keep the five fields and change the map to fit the project.

Three pattern moves cover more ground than a pile of random sequences:

• Increase rate, preserve grammar. The known even pattern arrives more often.
• Preserve rate, increase complexity. A repeated grouping changes prediction without changing the average pace.
• Preserve rate and grammar, increase duration. The player sustains the known job longer.

Name which move you are making. If you cannot, the variation may not have a design job yet.

Test the map as a player

Scrubbing shows that the events exist. Playback shows whether the demands make sense.

Follow the whole session at normal speed. Do not watch as an editor checking pretty transitions. Try to obey the meter, read the instructions, recognize each state, and cross every round boundary without touching the timeline.

Mark five failures:

1. Surprise: a new pattern or state becomes clear only after it begins.
2. Confusion: the player cannot identify the baseline or current rule.
3. Competition: an instruction, caption, or visual change steals attention from the cue.
4. False recovery: a supposed break still asks for work, or ends without a clear return.
5. Dead recovery: the pressure drops, but nothing prepares or contrasts with what follows.

Also mark moments that work. A clean handoff is reusable grammar. A variation that reads on the first attempt has earned the right to return later.

Test the rendered file, not only the editor preview. Cock Heroine's documentation is a useful reminder that round-sized event groups and tempo changes need deliberate handling, but the tool does not decide whether your complete sequence feels coherent.^[3] The map remains the director's job.

Repair the dial that failed

When a test fails, repair the smallest responsible decision.

If the player misses a change, add notice or simplify the first repetition. If a round feels flat, change its purpose before adding more cues. If an endurance passage becomes confusing, preserve the duration and simplify the pattern. If a break kills momentum, give it a handoff instead of deleting recovery from the session.

Speed can intensify a good job. It cannot give a vague round a purpose.

The current workflow spreads these decisions across notes, markers, event tracks, meter assets, and playback tests. We wish that coordination felt more playful and less fragmented. That is one reason we are building Kira around complete sessions and the decisions that shape them.

Kira is under development. It cannot pace or create your session today. Use the five dials now: map the player's job, change one main variable at a time, and prove the sequence in playback.