Play With Friends: The Co-op Guide - Run a Christmas Tree Lot Wiki

Overview

The business loop gets genuinely better with company: servers hold six players including you, and a well-split group can run stocking, checkout and car loading as parallel assembly lines instead of one stressed player sprinting between all three. This guide covers the server limit, the role split that actually works, and the honest truth about when solo play with staff is just as good.

Server size

6 players including you

Co-op roles

Inventory · Checkout · Loading

Passes

Bind per account

Solo viable

Yes — with staff

What Friends Change

A full server divides the loop's four beats across four pairs of hands. One player watches stock and places truck orders, another holds the register, a third carries trees to waiting cars — and nobody stands idle while queues build. The loop is identical to solo play; the throughput is not, and busy hours are where the difference shows.

Two things do not change in co-op. Game passes bind to the buying account, so your 2x Cash does not carry to friends. And reputation still flows from service quality — a full server serves faster, but the happy-customer pattern matters exactly the same, per the reputation guide.

The Three Co-op Roles

Split the loop into three responsibilities before the lot gets busy, and the session runs itself for hours. The split works for any group size from two to six — scale by doubling up on whichever role jams first, and re-check the assignment after every big purchase.

Roles are a starting grid, not a cage. The best groups swap deliberately and out loud — one sentence in chat before the swap, so nobody discovers an empty register by walking into it. The grid also tells new players where to start, which keeps the first hour of a fresh group from dissolving into five people improvising.

Planning a Session With Friends

A good co-op session is mostly planning, and the plan fits in five beats from invite to wind-down. Skip the first one and the whole evening fragments into wrong servers and doubled purchases; run all five and the group hums like a staffed lot with better jokes.

The plan costs two minutes in chat and saves the kind of confusion that ends sessions early: wrong servers, doubled purchases, empty registers and the slow argument about whose cash bought what. Groups that skip the beats spend the session recovering from them instead — run the plan, then play.

1. 01

   Verify the game page

   Everyone joins the listing by Mr. Grinchmas — the naming gets confused with other holiday tycoons.

2. 02

   Count the group

   Six players max including you. A seventh friend needs their own server, so decide the roster before launching.

3. 03

   Assign the roles

   Inventory, checkout, loading — assign per strengths. The newest player usually takes loading; it teaches the whole loop.

4. 04

   Agree the money plan

   Decide who funds restocks and how spending gets called. Overlapping purchases waste the common pot.

Solo Still Works

No friends online tonight? The loop runs fine alone: staff hire for 1,200 to 1,800 cash and automate the same tasks a friend would cover — the hiring guide prices both roles. Workers take breaks, so solo coverage needs more attention than a friend's, but nothing blocks progression.

The honest comparison: friends give flexibility, staff give consistency. A tree-handling worker never stops to chat, never wanders off to decorate, and never argues about the money plan — but also never volunteers to restock early when the shelves thin. Solo nights run on routine instead of banter, and the routine carries the loop fine.

Co-op Mistakes

Group sessions fail in predictable ways, and three patterns account for most of the chaos in busy-server screenshots. Each fix below is one sentence of communication — which is why co-op skill is mostly chat discipline wearing a game costume.

None of these mistakes cost cash directly — they cost the window of time while everyone figures out what happened, which during a busy stretch is worth more than any purchase. The pattern across all three is the same: one unspoken assumption, discovered by six people at the worst possible moment.

The Session Agenda

A one-minute agenda keeps a group session productive from the first truck order to the last. Run it in voice or chat before anyone spends cash — the four beats below cover the decisions that otherwise get made twice or not at all.

Item two matters most on update days, when a fresh code wave changes everyone's opening budget and the group's first purchase target with it. Run the agenda once at session start and once after any patch — the second run takes thirty seconds and catches everything the first one settled before the change.

• Confirm the correct place and everyone's roles
• Redeem codes together so nobody misses the cash wave — see the codes page
• Agree the first purchase target and who funds it
• Set the end-game goal: expansion, reputation push or a busy event window