Peak’s New Kick Feature: How It Changes Co‑op Runs

The co-op roguelite Peak has been quietly building a loyal following thanks to its mix of tactical combat, team roles, and chaotic randomness. One thing it has not been known for, however, is robust social tools. Until now, players had to rely on mutual patience, private lobbies, and the good graces of strangers to keep runs from being derailed. The latest patch finally confronts that reality by adding a proper kick feature, along with some unusual restrictions that make it more than a simple “remove player” button.

This article explores how the new kick system works, what its quirks mean in practice, and why it represents a bigger shift in Peak’s social design than it may first appear. You’ll also find practical advice for hosts, guests, and full squads trying to keep their runs fun, fair, and drama-free.

Why a Kick System Matters in a Co‑op Roguelite

Multiplayer games live or die on the quality of their social tools. Even the best-designed combat and progression systems can be ruined if a single griefing player can sabotage the experience for everyone else. Research into online play consistently finds that negative social encounters are one of the main reasons players abandon live-service titles or avoid matchmaking entirely.¹ While exact numbers vary by genre and platform, developers generally recognize that a small minority of disruptive players can have outsized effects on community health.

In a co-op roguelite such as Peak, runs are long, and failure can mean losing significant progress. When you add role-based characters and interdependent builds, one player refusing to participate, hoarding resources, or deliberately wiping the team can waste everyone’s time. That is why basic tools like muting, blocking, and kicking are more than convenience features—they are safety valves that let groups protect themselves without waiting on slow external moderation.

Until this patch, Peak was unusually bare in this area. The new kick feature is thus not just a quality-of-life change; it is a structural improvement in how the game manages social friction.

How the New Kick Option Works

The patch introduces a formal way to remove another player from your session, but it is not a free-for-all. Instead, the system is deliberately constrained and parked under optional settings.

Where the Kick Feature Lives

Rather than being active in every session, the kick tool is tied to a specific configurable mode. Hosts have to deliberately enable it when setting up a run. This design choice reflects a broader trend in online game design: allow powerful social tools, but put them behind an explicit opt-in so that players understand the risks and culture of that lobby.

• Opt-in design: Hosts must switch on the option when creating a run.
• Limited scope: Kicking is available only in runs configured with this setting (not in every public match by default).
• Host-centric: Control resides primarily with whoever “owns” the session.

By keeping the kick feature opt-in, the developers give groups flexibility without forcing every player into an environment where they might be removed without warning.

What Actually Happens When You Kick Someone

When a player is kicked, the game removes them from the current session and prevents them from rejoining that specific run. In Peak’s context, that can be a serious blow: the kicked player may have invested time, collected gear, and leveled up during the run. Losing all of that progress mid-session introduces real stakes on both sides.

The process typically looks like this:

1. The host opens the player list or relevant game menu.
2. They select the player to remove.
3. A confirmation step helps avoid misclicks.
4. The removed player is sent back to an appropriate menu or hub screen.

There is no built-in vote in this implementation. While vote-to-kick systems are common in other multiplayer titles, Peak’s design leans on the host acting as the single arbiter. This approach reduces menu complexity but raises important questions about fairness and potential abuse.

The Strange Case of the Non‑Reversible Kick

One of the most unusual quirks of this update is that certain roles in Peak, particularly the Scout, are impossible to “unkick” once removed. In other words, if you kick that player, you cannot re-add them to the ongoing run even if everyone later agrees it was a mistake. This design is highly specific and has immediate gameplay consequences.

Why Some Roles Can’t Be Un‑Kicked

Although the developers have not published a full technical breakdown, there are plausible reasons for handling certain roles differently:

• Role identity: Some classes may be tightly bound to progression or mission state, making it difficult to reinsert them cleanly without breaking the run.
• Technical constraints: Internal systems like spawned objects, visibility paths, or mission triggers may be linked to that specific player instance.
• Balance concerns: Allowing players to hop in and out of high-impact roles might enable exploits or trivialize certain encounters.

Regardless of the underlying reason, the outcome is clear: kicking a Scout (or any similarly restricted role) is effectively permanent for that run. The party has to continue shorthanded or with a different class if someone else joins later.

The Risk of “Permanent” Social Decisions

Non-reversible kicks add weight to social decisions. In some ways that is positive; hosts must think carefully before ejecting someone. But it also raises the stakes in a way that can magnify misunderstandings. Consider situations like:

• A player seems AFK but is briefly disconnected due to network issues.
• A language barrier makes it look like someone is ignoring strategy calls.
• A new player is learning mechanics and makes honest mistakes early in the run.

If the host responds by kicking and that decision cannot be undone, both sides lose. The squad might find itself down a key role for the remainder of the run, and the removed player is locked out of content they were actively helping complete. These scenarios highlight why reversing punitive actions is typically encouraged in online moderation; even in professional contexts, systems that allow quick correction of false positives are considered best practice.²

Balancing Host Control and Player Safety

Giving the host final authority over the kick button simplifies who is responsible for maintaining order, but it also concentrates power. Other games have experimented with various systems to balance host control with group consent, from majority votes to tiered privileges based on reputation or prior behavior.³ Peak’s current design sits on the simpler end of that spectrum, which has pros and cons.

For now, Peak relies heavily on players self-organizing: choosing hosts they trust, communicating expectations, and opting into lobbies whose settings match their preferences.

Custom Runs: Turning Chaos into a Playground

The patch does more than just add a kick button. It also folds that option into a constellation of modifiers under a catch-all category often used for experimental or humorous settings. The message is subtle but important: this is a tool designed for groups who want more control and are willing to accept the chaos that comes with it.

Why Put Kick Under “Stupid” or Experimental Options?

By nesting the feature among obviously playful or exaggerated modifiers (such as turning off certain enemy types or deliberately making runs bizarre), the developers signal that these settings are not intended to represent the default, balanced version of the game. Instead, they create a separate space where players can:

• Run private sessions with friends and house rules.
• Experiment with off-meta combinations and difficulty arrangements.
• Use social tools like kicking knowing everyone opted into that environment.

This strategy mirrors how some titles cordon off modded or custom lobbies from ranked play, preserving a core competitive space while letting creativity flourish elsewhere.

Synergy with Other Customization Options

Peak’s emerging toolbox for custom runs goes beyond social controls. The patch and its surrounding updates focus heavily on stability, reconnect options, and granular toggles. For co-op players, this has several implications:

• Rejoin resilience: Improvements to reconnecting reduce the frustration of being dropped from runs by accident.
• Enemy and modifier toggles: Groups can tailor difficulty and chaos, potentially making the game more accessible to mixed-skill parties.
• Kick as a last resort: With better stability, the need to kick for technical reasons should diminish, keeping the feature focused on behavioral issues.

As more customization is layered on, Peak moves closer to a sandbox co-op experience, where group culture and house rules matter as much as official balance.

Social Etiquette in a Post‑Kick Peak

New tools do not automatically create healthy communities; they simply enable them. With the introduction of kicking—and especially with some roles being non-recoverable—Peak’s players now need a shared etiquette to keep co-op sessions enjoyable.

Best Practices for Hosts

• Announce your rules early: A short message at the start (e.g., “learning runs, no speedrunning” or “experienced group, follow calls”) can prevent misunderstandings.
• Use kick as a last resort: Try warnings through text or pings before removing someone, unless the behavior is clearly malicious.
• Be extra cautious with Scouts and restricted roles: Treat removing them as irreversible and consider how vital they are to your current strategy.
• Respect time investment: Kicking someone deep into a successful run for minor mistakes is likely to drive players away from matchmaking altogether.

Best Practices for Guests and Matchmade Players

• Check lobby settings: If you see custom or experimental options enabled, understand that the host has more control—including the ability to kick.
• Clarify your role: If you queue as a Scout or similarly key class, let the team know your experience level.
• Communicate issues quickly: If you are lagging or need a short break, say so; silence is often confused with trolling.
• Leave toxic lobbies: If a host is clearly abusing kick or being hostile, simply exit and avoid that player in the future.

Technical Stability and the Road to a Healthier Co‑op Experience

The kick feature arrives alongside a series of stability improvements and bug fixes. Nearly every competitive or cooperative online game eventually undergoes similar housekeeping patches as its player base grows and edge cases multiply.⁴ For Peak, these changes help support the new social tools by reducing the chance that technical problems will be mistaken for bad behavior.

Key technical priorities visible in the update—and in broader industry practice—include:

• Improved reconnect logic: Ensuring players can return to sessions if they crash or briefly lose connection.
• Sync and desync fixes: Keeping all players’ views of the battlefield consistent to avoid confusion or perceived trolling.
• Error handling: Better messaging when players are removed due to server updates or version mismatches, so kicks are not blamed incorrectly.

When technical causes of disruption are minimized, social tools like kicking can be reserved for truly uncooperative behavior, which is where they are most effective.

Practical Tips for Surviving the New Kick Era

To make the most of Peak’s new patch without falling victim to unnecessary drama, players can adopt a few simple habits.

For Solo Queue Players

• Favor lobbies where the host has a visible track record or consistent rules.
• Avoid picking high-impact roles like Scout if you are still learning the game and fear being singled out.
• Watch early behavior: if the host uses kick impulsively on someone else, consider leaving before you invest too much time.

For Static Groups and Friends

• Consider enabling the kick feature only as a safety net, not as a default “management” tool.
• Experiment with custom options to create your own mini-modes, agreeing upfront on how and when kicks will be used.
• Rotate hosting duties so that no single person always controls the social tools.

FAQ: Peak’s New Kick Feature Explained

Can any host kick players in every game mode?

No. The kick feature is tied to specific lobby configurations and must be enabled by the host when starting a run. It is not automatically active in all modes.

Why can’t Scouts be un‑kicked once removed?

Some roles, such as the Scout, appear to be tightly integrated into mission logic or balance in ways that make re-adding them mid-run risky or technically complex. As a result, once kicked they currently cannot be restored to that session, which is why players should treat such removals as permanent decisions.

Is there a vote-to-kick option?

As of this patch, kicking is controlled by the host rather than a group vote. The game does not yet provide a built-in majority-vote system for removals.

Can the kick feature be abused?

Any powerful social tool can be misused. A host could theoretically remove players late in a run for unfair reasons. However, because the feature is opt-in and tied to specific settings, players can avoid lobbies where they have had bad experiences and favor more trustworthy hosts.

Does kicking affect my account reputation?

The patch does not introduce a formal public reputation score associated with being kicked. However, players should still assume that repeated negative encounters may lead others to avoid them or block them in external community spaces.

Looking Ahead: What This Patch Signals for Peak

In isolation, a kick button may not sound like a headline feature. But in the context of Peak’s evolving co-op ecosystem, this patch suggests a shift toward giving players more control over how they play and who they play with. The combination of stability improvements, reconnect support, and sandbox-style modifiers indicates that the developers are willing to trust the community with tools that can both enhance and complicate the experience.

If future updates build on this foundation with richer social features—such as improved reporting, clearer lobby categorization, or refined role handling—the game could become a model for how small-scale co-op titles handle player autonomy without fracturing their communities. For now, the message is clear: choose your hosts wisely, don’t treat the kick button lightly, and remember that in Peak, your social decisions can be just as consequential as your build choices.