Update Log: Every Verified Milestone - Run a Christmas Tree Lot Wiki

Overview

This game moves fast: launched November 4, 2026, it hit discovery charts within two days, ran its first event within four, and shipped code waves within nine. This log records every verified milestone with dates — and deliberately leaves out anything the developer has not confirmed, because invented patch notes age worse than no notes at all.

Launched

November 4, 2026

Latest event

Christmas Event Part 2

Place ID

112146301142141

Developer

Mr. Grinchmas

The Timeline

Every entry below is tied to a dated public record: the Roblox create stamp, listing changes, third-party analytics snapshots and code-recap publications. Read it top to bottom for the growth story — eleven days from zero to ten thousand concurrent players — or jump to the latest rows to see what changed this week.

The timeline stays chronological and dated so old entries never masquerade as fresh news — a real problem in tycoon communities, where a two-week-old snapshot routinely gets reposted as today's data. When a new milestone lands, it joins at the bottom with its own date, and nothing above it gets rewritten to fit the new story.

How We Track Updates

Three sources feed this log: the official Roblox listing (create stamps, titles, descriptions), the developer's community channels for announcements, and dated third-party records for analytics and code recaps. Each entry cites its kind — official, community or analytics — so you can weigh it accordingly instead of treating every row as gospel.

What we do not do is invent balance patches. If a wave of guides claims a worker rebalance with no dated record anywhere, that claim stays out of this log until something verifiable surfaces. Rumors belong in chat, not in a dated timeline.

Where Updates Show Up First

Update waves announce themselves in predictable places, and checking them takes less time than being surprised mid-session by a changed price or an expired code. These three surfaces cover everything official, listed in the order changes usually appear — the listing leads, the community explains, the codes page monetizes.

The in-game menu is the final word — third-party pages can lag hours behind a live listing change, and this wiki prefers being an hour late to being a day wrong. The habit is the same one that runs the rest of this log: check the primary source first, then let the mirrors catch up at their own pace.

After Each Update

Update waves change prices, gates and code validity, so a ten-minute post-update routine keeps your plans current. Run these three checks before any big purchase on update day — the menu is fresh, the captures are current, and the wrong assumptions are cheapest to catch now rather than at the checkout screen.

The routine matters most on days you planned to spend: a changed price or expired code otherwise costs real cash, and the headquarters savings plan is the classic victim — one unverified purchase on the wrong day can set a reputation-and-cash gate back by days of grinding. Ten minutes of checking beats a week of re-earning.

1. 01

   Re-read the listing

   Check the title, description and store tab in-game for anything new — this is where official changes surface first.

2. 02

   Refresh codes

   New strings arrive with waves and old ones expire. Redeem from the codes page before spending anything.

3. 03

   Re-verify prices

   Upgrade and pass prices can shift. Confirm the numbers you planned around still match the live menu.

What We Do Not Publish

A log earns trust by what it refuses to include, and this one refuses four things. Each line below has been pressed into other wikis by hype cycles at some point — keeping them out is what makes the dated rows above worth trusting when you plan a purchase or a session around them.

If one of these ever becomes verifiable, it graduates into the timeline with a date like everything else — the exclusion list is not a judgment on the rumor, just a note about its evidence. Until then, chat is the right home for it, and this page is the wrong one.

• Invented build numbers or version names
• Balance changes without a dated record
• Leaked or datamined content
• Analytics snapshots presented as official dashboards