room/run/out/case.md

Chronology

The supplied record is silent from the canvas opening through H+27.67, and the pre-week brief contains no items, so this case cannot establish what the room was doing when r/place opened or how its coordination began. The first visible episode runs from 62uylj at d1 04-01 19:40 to 63297o at d2 04-02 21:07. It starts by declaring “DE OFFICIELE COORDINATIE VOOR PIXELS PLAATSEN IN PLACE” (62uylj), publishes and repeatedly revises plans, and directs people to Discord because “Het plan veranderd ieder uur” (dfqn51t). The reply that the Reddit copy “is echt al 24 uur oud” (dfqotc8) makes Discord's faster tempo explicit. By the episode's end, a moderator post tells people “Houd je aan het plan” (63297o), announces a maintenance script, and later adds an attack on the Void. This stretch is described from batch 01, whose coder read it.

From 632mbf at d2 04-02 22:08 to 635b21 at d2 04-03 07:32, expansion and restraint coexist. A call to make a Goodboye dog orange (632mbf) is refused because the clogs are “een prachtig compromis” (dfqszy6). Elsewhere people defend overnight, attack Singapore, fill territory left by the Void, and make a pact “om samen The Void te bestrijden” (635b21). The moderator's edited plan also promises “gebied terug te geven aan groepen die we weg hebben geplaced” (635b21). These are contrasting practices in the same period, not evidence that the community collectively changed from conquest to restraint.

The next episode, from 635ujh at d2 04-03 10:13 to 636e4q at d2 04-03 12:18, combines allocating space with redesigning Dutch work. The diplomacy post says, “We will review all art and divide the area between those we've wronged in the past” (635ujh), while one participant insists that the room is “uitlenen (niet weggeven!)” (dfrl466). Applicants ask for bounded places; participants propose provincial flags, Delft-blue tiles, Buurman & Buurman, canal houses, and a windmill. The allocation therefore repairs some displacement while retaining a claim over the orange ground. At the episode's end, the flag redesign stalls around scripts: a commenter says they block creativity and go against “het principe van /r/place” (dfrqdvr).

Batch 02 opens 28 seconds after the preceding post, with 636e8e at d2 04-03 12:19, and runs through the last maintenance plan 637wte at d3 04-03 16:35. It begins inside, rather than after, the unresolved script conflict. The dominant episode is participants fighting among themselves over whether the Yeti should survive: one says “Yeti moet weg” and runs scripts against it (dfrnfmf), while another warns that removing a classic meme turns people against them (dfrnkaj). Others propose borders around nearby art, bargain with GreyBlob, and keep proposing national words and pictures, while defense scripts erase attempted houses—“De huisjes worden allemaal weggepoetst” (dfrvgvk). The sequence supports continuing tension between maintenance, expansion, and preservation; it does not show that the earlier canal-house dispute caused the Yeti fight.

The closing episode runs from 6383f6 at d3 04-03 17:05 to 639qno at d3 04-03 21:27. The sticky appears 29.4 minutes after the last maintenance plan and says Reddit ended the experiment, then thanks participants “voor het coördineren en het groots maken van ons Neerlands trots” (6383f6). Replies sing the Wilhelmus, praise colonization, argue over the Yeti and the point of Place, and archive the result as history, backgrounds, and timelapses. A moderator title then says, “Place is voorbij, maar we meemen gewoon door in de Cirkeltrek” and invites people to Discord (638j4l). The record closes with “You guys are real jerks” (639qno), but its deleted body leaves the grievance unknown. This final stretch is described from batch 02, whose coder read it.

Relations — what set off what

The stale Reddit plan explicitly prompts a move to Discord. “Het plan veranderd ieder uur, Join alstublieft de Discord” (dfqn51t) receives, 37.6 minutes later, the answer that the poster already got the copy there and it was 24 hours old (dfqotc8). The later turn names the same plan and venue, so this is an answered correction rather than a relation inferred from adjacency.

The proposed Goodboye offensive—“Maak 'm oranje!” (632mbf)—draws a refusal 5.1 minutes later because people had worked all day on cooperation and the clogs were a compromise (dfqszy6). The reply states its reason; this is a supported response, not merely a neighboring comment.

Across the slice boundary, the canal-house/script dispute in 636e4q is followed 28 seconds later by the Yeti thread 636e8e. Both concern scripts overriding desired artwork, but no passage says the first set off the second. It is an observed continuation of a problem, not a causal relation. [crosses 01|02]

Inside the Yeti thread, “Heb er scriptjes op zitten om hem weg te halen” (dfrnfmf) draws, 3.6 minutes later, the answer that removing classic memes is diplomatically unwise (dfrnkaj). Later, a direct request for a template (dfrqj1o) receives “zo hoort de yeti er uit te zien” after 2.4 minutes (dfrqmup); 1.2 minutes later the requester says, “Ik ga hem herstellen” (dfrqoo5). Here the supplied template directly supports the announced restoration attempt. The later disappearance of the Yeti is an outcome in the sequence, but the record does not establish which actor or script caused it.

The GreyBlob exchange supports a conditional bargain and shows why it failed to finish. The offer permits a new blob only “IF you'll maintain the area orange and defend it” (dfrvghl). Forty-one minutes later a GreyBlob participant accepts—“we will help defend you guys as long as the greyblob can live” (dfrxjjm)—and 16.6 minutes later the proposer promises to contact moderators (dfrycae). After another 3.88 hours, the participant says the bargain is moot because “r/place has ended now” (dfsacgn). The participant explicitly attributes non-completion to the platform ending; the corpus does not show a moderator decision inside Discord.

The last maintenance plan 637wte precedes the closing sticky 6383f6 by 29.4 minutes. The closing post attributes the end to Reddit, not to that plan, so the relation supported here is sequence: a still-active plan was overtaken by platform closure.

Posts against comments

[Batch 01] Posts present a governable project: the current-plan post says following the plan produces “een zo goed mogelijk resultaat” (63297o), and the diplomacy post promises to divide space among groups previously wronged (635ujh). Comments expose the limits of that claim: the room is lending rather than giving away space (dfrl466), proposals are ignored, and organized Discord participants distinguish themselves from other Dutch placers. The posts promise a plan and allocation; the comment layer shows conditional ownership and incomplete command.

[Batch 01] Posts introduce scripts as maintenance and implementation tools. Comments say scripts block Czech cooperation and new Dutch art; the clearest complaint asks who will turn off defense because “De huisjes worden allemaal weggepoetst” (dfrvgvk). This is a practical contradiction, not proof that every script failed: the edited plan also says one bug “is inmiddels hersteld” (63297o).

[Batch 02] The Yeti post calls for preservation, while a comment says “Yeti moet weg” and reports scripts removing it (dfrnfmf). The later closing exchange sharpens the difference: one participant says friends used “10+ accs” to destroy the Yeti (dfs1iso), while another asks why because “De meesten wilde die behouden” (dfsbol7). These are conflicting positions and reported actions, not evidence that the community first agreed and then changed its mind.

[Batch 02] Celebratory posts describe unprecedented coordination, Dutch pride, and successful colonization. The comment layer contains a direct dispute over the event's purpose: one person complains that Discord repaired small projects instead of taking them (dfs0lu0), and the reply says it was not Civilization but a “teken samen iets leuks” activity (dfs1ao1). Territorial pride is prominent in posts; this argument over conquest versus shared drawing is visible in comments.

Counter-reading

My one-sentence reading is: PlaceNL made expansion and national artwork partly governable through changing plans, Discord, scripts, borders, and deals, but its public exchanges repeatedly show incomplete control and conflict over what should survive before participants closed by celebrating and preserving the result.

A plausible competing account is that this coordination was broadly effective and the visible disputes were marginal exceptions. If my reading were wrong, the corpus should contain people saying that scripts and current plans worked reliably, that participants followed instructions, and that bargains or protected artwork held without recurring interference.

The strongest contrary item is the edited current-plan post 63297o: it says a script error “is inmiddels hersteld.” This establishes a concrete repair and prevents a blanket claim that scripts or coordination simply failed. The counter-search also returned dfrfv7q, where a moderator says another fault “Wordt aan gewerkt,” dfqdb8w, which directs people to Discord for the latest plans and agreements, dfqzj9p, which describes script-assisted overnight defense, and 635b21, which states the Void pact and return plan. I read each returned item. A corpus-wide regex search for sentences in which “iedereen” or “allemaal” is followed by following, listening, keeping to, or working with the plan returned no items; that null is limited to those Dutch terms and cannot establish universal noncompliance, especially in a partial record with missing bodies and off-platform talk.

I added the late code “saying the script error has now been fixed” to the existing script theme. The contrary evidence changes the account from coordination as ineffective to coordination as achieving local repairs, defense, and public bargains. The central qualification survives: later passages still show an absent script manager (637wte), erased houses (dfrvgvk), and incompatible Yeti actions (dfrnfmf, dfsbol7).

Saturation

Later-slice practice was partly repetition and partly genuinely new closing work. The first codes for publishing and updating the current plan, moving live coordination into Discord, deciding what the next pixels should do, designing Dutch words, pictures, and borders, holding and finishing what is already there, expanding, attacking, and claiming orange ground, making borders, pacts, and deals with neighbors, sparing and rebuilding nearby artwork, assigning orange space to displaced groups, making, fixing, and arguing over scripts, admitting that plans do not control every Dutch placer, celebrating and retelling Dutch conquest, and crossposting advice for people talking about flags all occur first in batch 01. Batch 02 repeats and extends each of those except moving live coordination into Discord; Discord still appears in later script and continuation practices, but no batch-02 code was added to that earlier theme. The first codes for fighting among ourselves over whether the Yeti stays, thanking one another and singing the event closed, turning the finished work into history and keepsakes, arguing whether Place meant conquest or drawing together, carrying pixel play and the community on elsewhere, finding out too late that Place had ended, joking back at a summoned bot, and calling the Dutch group real jerks occur in batch 02. The new batch-02 practices cluster around the last conflict and the ending rather than opening a different organizing system.

The Reddit record is strong enough to support a full verdict: all 101 threads were disposed and coded, with no event-touching opening classified out of scope. It is not a whole account of coordination. Discord held fast-changing plans, script targets, moderator contact, singing, and continuation, but only invitations and reports return here. Deleted and removed bodies interrupt proposals and the final accusation, and linked images, repositories, and canvases were not fetched. Branch B also means no single reader held the raw week and there is no agreement measure; the account joins two independently read slices, so cross-boundary continuity is weaker than within-slice exchange evidence.

Selection

The case lead read the empty pre-week brief and all 101 openings before the fixed gate. The gate selected branch B on 701 in-window items against a threshold of 500, producing batch 01 (442 items) and batch 02 (259 items), each made of whole threads in corpus order. Fleet coders retained all 101 threads because each touched r/place conduct or its immediate aftermath; none was excluded. A title naming the canvas was therefore never paired with an out-of-scope disposition. The case lead did not read raw threads while the fleet ran. After consolidation and theming, the counter-reading used find and read item; the late code came from 63297o, a thread the fleet coder had read in full.

Other communities named

Goodboye is both negotiated with and targeted by a rejected offensive. r/rmtk requests a ceasefire; Czech and Swedish neighbors are thanked as friends at the close. Puerto Rico, the Dominican flag, Indonesia, LANBox, the Yeti, SS13, the Creeper, and GreyBlob appear in arguments about attacking, bordering, preserving, rebuilding, or exchanging defense. The allocation thread receives claims for r/ftlgame, r/mindcrack, r/menonkazoo, r/formula1, r/dominican, r/farmcarrots/r/fartcarpets, and r/albania. These are PlaceNL's and applicants' statements inside this venue, not reconstructions of the other communities' conduct.

Discord is the main place to which live planning visibly moves: Reddit receives current plans, role and script instructions, requests for moderator contact, complaints, and memories, while the underlying discussion remains unseen. Strawpoll carries a Greece choice; GitHub and image hosts carry tools, targets, templates, and archived results; r/place and r/cirkeltrek are used to circulate designs and the history rap. After closure, a moderator title points through Cirkeltrek to Discord, while one reply points to pxls.space; the latter shows another canvas was available, not that PlaceNL as a group moved there.

Absence

The empty pre-week archive supplies no ordinary-week baseline and cannot show that the community had no earlier life. The first corpus opening is already 27.67 hours after the canvas began, so the origin of “official” coordination is absent. Removed and deleted bodies leave some proposals, warnings, and the closing “real jerks” accusation without grounds; surviving titles and replies establish only the acts they contain, and no missing text was reconstructed. Image-only and link-only posts show what participants called or proposed, not what the targets displayed. Discord is conduct as a chosen venue, but its unseen deliberation limits claims about how plans, permissions, and bargains were decided.