Guides

Clear Bamboo Co-op Guide

Split roles, call the clock, and clear bamboo with friends without wasting the timer.

Last updated:

Clear Bamboo Co-op Guide

Clear Bamboo by Takemura Onsen Co. (mykzverse) is built for solo or friends. The core loop never changes — chop bamboo → fill your bag → bundle at posts → sell before the timer while hunting the lost village hot spring — but co-op changes who owns each step. Servers hold up to 24 players, runs save across sessions, and a coordinated trio can print cleaner clears than three people wandering the same patch. This guide covers role splits, voice and chat calls, panda ownership, timer discipline with friends, when not to all split for the spring, public-server etiquette, and how saved runs make multi-night squads work.

If you are brand new, skim Getting Started and Controls first, redeem ONSEN on codes for 150 Gems + 2x Win Reward (1h 30m), then come back here before a boosted friend night.

Why co-op feels different

Mechanics are identical for every account. Co-op mainly reduces wasted motion: one player can keep chopping while another ferries and a third watches the clock. It also multiplies mistakes if nobody calls posts or everyone greed-scouts the spring at once. Treat friends as extra bags and living waypoints — not as permission to ignore beat the timer.

Role split that actually works

Pick roles before the run starts. Keep them flexible, but name them so chat stays short.

Chopper

Opens bamboo fronts with Machete, Kaze Scythe, or Wind Orb. Job is throughput and corridor clearing — not sightseeing. Choppers call when a lane is “open” so ferries know where payload is densest. Tool ladder context: tools and upgrades.

Ferry

Owns bag-to-post motion. When choppers are deep, ferry players rotate heavy bags to bundle posts and keep the path readable. Ferry is the role that dies most often to ego (“one more stalk”); give it to the most disciplined friend.

Sell captain

Watches the timer aloud and decides when the group sells. One captain prevents the classic fail where everyone assumes someone else is heading to sell. The captain may also ferry on small squads; on larger friend groups, keep the role dedicated during 2x windows.

Duo default: one chopper + one ferry/sell hybrid. Trio default: chopper, ferry, sell captain. Four+: add a second chopper or a scout who only peels for landmarks when the captain green-lights it.

Voice and chat calls that save runs

You do not need fancy macros. You need short, repeatable calls:

  • “Heavy” — bag nearly full; ferry or self-bundle now.
  • “Bundle now” — group cadence; nobody opens a new patch until posts are cleared.
  • “Sell in X” — captain sets a clock threshold (for example, last third).
  • “Hold spring” — exploration paused; economy first.
  • “Post left / post right” — directional anchors so friends do not invent three routes.

On public servers without voice, type the same phrases. Silence is how 24-player lobbies time out with full bags three screens from sell.

Panda ownership in co-op

After Update 2, pandas collect bamboo as personal helpers. In co-op that means:

  • Each player’s pandas belong to their progression (payload/speed). You cannot “share” one friend’s maxed helpers as a communal pet army.
  • Stack roles with helper strength: the chopper with best panda upgrades should open wide lanes; the ferry with weaker helpers should stay nearer posts.
  • Do not all AFK and expect pandas to finish the sell loop. Helpers raise throughput; humans still bundle and sell.

Deep dive: pandas guide and playstyle notes on players. Tornado mobility from the same update helps squads rotate lanes — practice on known posts before flinging the whole party into fog (tornado guide).

Timer discipline with friends

Co-op greed is contagious. Counter it with pre-agreed rules:

  1. One sell captain — no committee debates at red clock.
  2. Turn-back time — past the threshold, new patches are illegal unless already mid-bundle.
  3. Never pass a post heavy — friends included; call them out kindly.
  4. 2x nights = reliable clears — during ONSEN, prioritize repeat sells over hero plays.
  5. One experiment per run — either test a new corridor or a new upgrade plan, not both, so the squad learns what worked.

Saved runs mean you can schedule a discipline night (post-hug sells) and an explore night (spring corridors) separately instead of mixing them into one chaotic boosted hour.

When NOT to all split for the hot spring

The find the hot spring fantasy is strong. Splitting every friend in a different compass direction is how boosted windows die.

Do not all split when:

  • ONSEN 2x is active and your squad still whiffs basic sells.
  • Nobody has a shared post map from prior saved runs.
  • Gear is uneven (starter + Wind Orb in the same “scout everything” plan).
  • Public randos are already congesting the only known corridor.

Better spring co-op pattern: one or two scouts push a single corridor while a ferry/captain holds the post-to-sell spine. Scouts carry partial bags and turn back on the captain’s call. Landmark notes go in Discord after the run — join via Discord and group — so the next session starts smarter.

24-player public etiquette

Public servers are crowded workshops, not your private farm:

  • Do not body-block posts or sell flows for content clips.
  • Follow experienced players at a respectful distance to learn corridors; do not steal the exact chop tile they are mid-swing on if space is tight.
  • Keep chat calls useful; spam and script ads help nobody (scripts stay unverified and unsafe anyway).
  • Friend invites beat hopping servers mid-2x — runs save, but your multiplier does not wait while you rematchmake.

Classes and Perks from lobby Gems still matter per account. Co-op does not pool gem boards; each friend should spend cutting/speed first so the squad’s slowest member is not the timer bottleneck.

Saved runs across sessions

Clear Bamboo saves runs, which is the secret weapon for friend groups with homework, work, or different time zones:

  • End on a clean sell so the next night starts emotionally fresh.
  • Write one shared note: tool tiers, panda levels, last corridor tried, next unlock target.
  • Onboard late joiners with Getting Started instead of dragging them into a spring wipe.
  • Watch updates together before a big night so nobody shows up surprised by panda or tornado changes.

Sample co-op session plan

  1. Everyone redeems/confirms ONSEN in lobby.
  2. Assign chopper / ferry / sell captain in chat.
  3. Two post-hug sells to sync pacing.
  4. One two-post lane with pandas sweeping edges.
  5. Optional: single scout peel toward spring landmarks — captain retains veto.
  6. Cash a final safe sell before the 2x window ends.
  7. Post Discord notes for the next saved-run night.

Co-op in Clear Bamboo is not a different game — it is the same chop-bag-bundle-sell puzzle with clearer communication. Name the roles, protect the clock, own your pandas, and let saved runs turn one good night into a week of progress.

FAQ

Frequently Asked Questions

Quick answers about codes, tools, pandas, and the hot spring.

Does Clear Bamboo support co-op with friends?

Yes. Play solo or with friends on servers of up to 24 players. Runs save across sessions, so squads can continue progress on later nights.

What roles should a co-op squad use?

A simple split is chopper (open bamboo), ferry (bag to posts), and sell captain (watch the timer and call the sell). Duos can merge ferry and captain.

Do pandas work for the whole party?

Pandas are personal helpers tied to each player’s upgrades. Coordinate who opens lanes based on whose payload and speed are strongest, but everyone still bundles and sells.

Should the whole squad split up to find the hot spring?

Usually no. Keep a post-to-sell spine staffed and send one or two scouts on a single corridor. All-split hunts during 2x windows often waste the boost.

What code should friends redeem before a co-op night?

ONSEN for 150 Gems plus 2x Win Reward for 1 hour 30 minutes. Each account must redeem individually in the lobby before starting runs.

Any etiquette tips for full 24-player servers?

Do not block posts or sell paths, keep calls short and useful, learn corridors respectfully, and avoid unverified scripts. Friend stacks beat chaotic public free-for-alls during boosted windows.