room/run/out/case.md

Chronology

When the canvas opened, r/mindcrack was still carrying its ordinary Free Talk, UHC, stream, and video-post routines. The event first became visible in the coded record at d0 03-31 20:51, when a post showed a “Mindcrack logo at (420,33)” (62o1bl). Replies explained the five-minute pixel rule, identified late helpers, started a Guude logo beside it, and wondered how long the work could stay up. By d1 04-01 17:08, one participant said the first logo was “gone now, alas” and proposed a larger rebuild (dfp4v0y); at d1 04-01 17:46 another answered “I have begun!” (dfp6ejt). This first episode runs from 62o1bl to dfp6ejt.

From d1 04-01 20:22, a call to enlarge Guude became a larger building-and-defense episode (62v848). Members added faces and lettering, chose a purple background, negotiated a one-pixel border with neighbouring beer mugs, solicited a stream for help, and narrowed their defense as repeated overwriting outpaced them. The edited post could say “It’s done! Great job everyone!” (62v848), while a later participant said, “we don’t have enough people to defend everything” and proposed pulling back to Guude (dfqhthh). Visible art also drew lapsed viewers back: one said seeing it “bought all the nostalgia back” and prompted old-video viewing (dfpzvsc), while another told former fans they were “always welcome back” (dfpx7ve).

The loss-and-relocation episode crosses batches 01 and 02. By d2 04-02 16:46 an edited post first called the Guude logo’s fall, then corrected that report and said it was moving (630o71). Czech and Dutch visitors, Mindcrack builders, and neighbouring small groups negotiated borders and moves; participants made backup logos, rejected scripts as defeating a “community thing” (dfqmo8s), and shifted from building to maintaining several sites. The record supports a development within this episode: protection of smaller neighbours was not automatic. MenOnKazoo said Mindcrack had expanded into its unfinished logo and asked not to “steamroll over smaller subs” (633yh1); the request received “Sounds reasonable! I’ll do my part” (dfr5pxo) and a reported three-pixel move (dfr77ok). This is a corrective response, not evidence that the community held one consistent position from the start. [crosses 01|02]

At d2 04-03 08:23 a member asked for one r/place megathread (635h8y). A moderator agreed 5.6 minutes later (dfrhk5p) and at d2 04-03 08:31 said recent posts had been removed to combine future discussion (635i5t). The megathread held maintenance, neighbour help, and the first in-room ending account. At d3 04-03 17:02, a participant listed an Etho head, Mindcrack logo, two Guude Gs, Kurt, and Pause as surviving, then separately named the logos and faces “we lost along the way” (dfrzkvb). The list is that participant’s account of the result, not independent verification of the canvas.

After placement ended, a final-result post at d3 04-03 17:36 became a place to identify, mourn, joke about, and claim parts of the work (638be0). Replies said “RIP Doc’s face” (dfs6d15) and added Pakratt and Zisteau to the losses (dfsa6qk), while others thanked helpers and argued over Dutch organization. At d3 04-03 21:33, the established FIU format used the ending—“now as /r/place ended”—to offer its final UHC recap (639sof). At d3 04-04 04:08, the Weekly Recap called the week “Mindcrack Invades r/Place!” and recounted fans and Mindcrackers building the logo (63bxgr). Thus the closing episode runs from dfrzkvb through 63bxgr: immediate accounting gave way to the room’s ordinary recap practices, although some threads continued beyond the window.

Relations — what set off what

The following are supported responses, not inferences from reply adjacency alone. First, loss explicitly prompted rebuilding: “It’s gone now” and “I suggest we rebuild it” (dfp4v0y) received “I have begun!” 37.1 minutes later (dfp6ejt). Second, the beer-mug artist’s request for “one pixel border” (dfplomc) received “there should be room for both of us” 3.4 minutes later (dfpltin). The later words answer the earlier words in each exchange.

The canvas image itself prompted renewed viewing in one participant’s own explanation: “I saw this in /r/place” and “time to watch some old mindcrack vids” (dfpzvsc). A welcome from another participant (dfpx7ve) establishes a contrasting response in the same thread, but not a general causal claim that every returning viewer resumed participation.

Participants themselves connected being overrun to later accommodation. One said they did not want the Pink Bird to see Mindcrack as Mindcrack saw “the dutch group” (dfqprjt); later, the same speaker said the work had to move to avoid “stepping on some toes” because Mindcrack had “a similar experience” with the Dutch (dfr6y1r). This is a participant’s explanation for the move, not proof that Dutch action caused every subsequent alliance. The MenOnKazoo request (633yh1) was followed by explicit acceptance 18.2 minutes later (dfr5pxo) and a concrete move within 48 minutes (dfr77ok). [crosses 01|02]

The megathread relation is equally explicit: the request (635h8y) received “Yes good idea. I’ll make one” (dfrhk5p), followed two minutes later by the moderator’s consolidating post (635i5t). A later call to repair the Pink Bird says this was help “we had promised in your peace pact” (dfrmaj2), directly linking the aid to the earlier agreement rather than merely placing the comments next to one another.

After the close, an organized-Dutch apology said random participants, not the organized group, attacked Mindcrack (dfs5fc1). A direct reply 2.7 hours later, explicitly “speaking as the ‘diplomat,’” called the organization terrible and complained about Discord administrators (dfsdv3z). This establishes disagreement, not a community-wide change of mind. The final Weekly Recap itself recalls and links the prior pixel work (63bxgr); the intervening final-result replies follow the end of placement, but where they merely sit under the result post, this account treats them as an observed sequence unless their words identify or recall the earlier work.

Posts against comments

[batch 01] Posts foregrounded accomplishment and urgent projects. The enlarged-logo post says “It’s done! Great job everyone!” (62v848); its comment layer later says there were too few people to defend everything and recommends saving Guude alone (dfqhthh). The descriptive contrast is temporary completion in the post versus selective retreat in comments, not evidence that the group reversed a settled policy.

[batch 02] “Mission complete” (634qx8) is immediately qualified in comments by “Now to maintain!” and “help out the surrounding groups” (dfrckoy). Elsewhere in the comment layer, one Dutch participant reported a vote not to take Mindcrack’s spot (dfrnmn6), while another reported a later vote to take it (dfrup6k). These are conflicting participant reports; the record does not establish which vote governed action.

[batch 03] “Final result” (638be0) presents a settled image, while comments preserve both survival and loss: Doc’s face was “there briefly” (dfs6d15), and Pakratt “fell into the void” while Zisteau “never fully arrived” (dfsa6qk). The r/placenl apology post (639cud) has no surviving comment bodies, so that thread cannot show whether the room accepted or rejected it.

Counter-reading

My one-sentence reading is: under repeated erasure, Mindcrack participants kept recognizable pictures present through rebuilding and negotiated mutual help, then made a mixed account of survival and loss and folded it back into regular recap formats.

The competing account stated before searching was that neighbour-protection might be mainly a retrospective self-portrait, while operative conduct favored Mindcrack’s own logos, scripts, or knowingly covering smaller allied work. If my reading were wrong, the record should contain explicit support for scripts or steamrolling allied or smaller work, rejection of mutual help, or statements treating border and defense agreements as disposable.

The strongest contrary item is the MenOnKazoo request: it says Mindcrack had “started expanding into” the smaller group’s unfinished logo and asks it not to “steamroll over smaller subs” (633yh1). This changes the finding: accommodation was sometimes a correction after encroachment and objection, not a practice present consistently from the outset. The later acceptance and move (dfr5pxo; dfr77ok) preserve the narrower claim that explicit objections could produce negotiated accommodation.

Searches covered case-native language for writing or using scripts, covering or stepping on small/allied work, breaking truces or borders, and defending only Mindcrack or Guude. They returned a small pro-script complaint—calling people “huge dicks” over being able to run one (dfqzw1d)—but also direct refusal: “we don’t write scripts because we believe it is against the spirit of /r/place” (dfqrp5q). Other returned items disputed whether Dutch work used scripts (dfqq0cv; dfqw4b4; dfqxpw0) rather than showing Mindcrack deploying one. The own-work-only query returned no items. That null result is limited to those terms and this partial record; removed bodies and off-platform discussions mean it cannot establish universal restraint.

Saturation

The event practice is well represented across building, loss, rebuilding, bargaining, maintenance, moderation, and immediate retrospective accounting, but the interactional record is not whole. Deleted and removed bodies are concentrated in central negotiation threads, especially 639cud; final-result and recap discussions continue beyond the window. Discords and Justin’s stream carried plans, assurances, and complaints, but Reddit shows only what participants relayed back, not the decisions inside those venues.

Later slices did bring new practice rather than only repeat settled themes. Nine themes first appear in batch 01: building pictures; keeping them standing; calling people in; bargaining for borders; arguing about fairness; welcoming returning fans; making and mistaking April Fools jokes; explaining r/place; and celebrating completion. Batch 02 first adds gathering discussion into a megathread and taking stock when placement ends. Batch 03 first adds folding r/place into the room’s regular FIU and Weekly Recap formats. The later script-dispute codes found in step 5 extend the batch-01 fairness theme rather than opening another practice.

No single reader held the whole week. Chronology and cross-slice relations were assembled from ordered pooled codes, the forest, facts files, and slice cases; the relation spanning batches 01 and 02 is marked above and rests on participants’ explicit comparisons and responses. One coder read each slice, so there is no agreement measure, and arbitrary slice boundaries weaken any claim that depends on a week-wide reading.

Selection

The case lead read the complete openings table before the gate, using it only to orient the week. Because the gate recorded 1,133 in-window items against a threshold of 500, branch B divided whole threads into three ordered slices. Fleet coders retained threads when their served windows touched the canvas or recruited a community practice into the event; they also retained the subreddit’s own April Fools conduct while marking it as distinct from the canvas. Ordinary UHC, gameplay, stream, birthday, and unrelated discussion threads were excluded, with exact exclusion citations where required. The lead did not read raw threads before consolidation; step-5 reads were limited to returned counter-search items and the evidence passages needed to adjudicate the account.

Other communities named

Neighbour relations are central rather than incidental. r/czech appears as both pressure and negotiating partner; r/placenl and r/thenetherlands appear through expansion, apology, diplomacy, and disputed internal votes. r/thepinkbird, r/MenOnKazoo, and r/PuertoRico receive negotiated room or help. Participants also name r/texas, r/armenia, r/ainbowroad, greenlattice, r/cirkeltrek, r/gravityfalls, r/ftlgame, r/paydaytheheist, r/placestart, r/indonesia, r/armok, r/Slovakia, r/ultrahardcore, and r/FIUHC. These names do not establish the other communities’ internal intentions.

Coordination partly left Reddit. FLOB Discord carried a logo attempt, Justin’s stream was asked for defensive help, and r/place, Netherlands, and Hermitcraft Discords carried boundary messages, diplomacy, or reinforcements. What returned were claims such as “trying to keep some subreddits as friends” (dfqajul) and “getting help from the Hermitcraft discord” (dfqgwsb); the discussions producing those actions remain unseen.

Absence

Removed and deleted bodies interrupt early success posts, the large defense and negotiation discussions, and almost the entire reply layer of 639cud. Surviving calls and answers still show rebuilding, moves, border agreements, neighbour help, moderation, and post-close accounting, but they cannot recover every proposal or the reception of the r/placenl apology. Automated flair and preview comments were treated as platform setting; moderator-run consolidation was treated as community conduct. No removed text was reconstructed, and no claim about a deleted exchange is inferred from its tree position alone.