room/run/out/case.md

Chronology

For the first 13.64 hours, the fleet found ordinary r/indonesia talk but no visible r/place practice. The event first enters the coded record at d0 04-01 05:48, when 62qymh calls readers to “remove the blue from that Dutch flag.” That episode runs through dfow2he at d0 04-01 13:23, where a member reports posting the request to r/sweden. It overlaps a second start at d0 04-01 07:07: 62r9d9 says, “Let's make the Indonesian flag on /r/place.” Members then choose space, seek leaders, place letters and borders, open contingency sites, and recruit from an ordinary daily-chat thread.

From 62wyny at d1 04-02 01:26 through dfrc40s at d2 04-03 04:57, making becomes holding and enlarging a flag. The opening calls, “bendera kita diserang di r/place, bantu mengamankannya!” Members refresh before placing, repair red and white areas, stand night watch, share scripts, build bots, seek allies and debate attacks on neighbouring work. Presidential decrees and “war plans” are playful, but they also carry coordinates, priorities and calls for defence. This is not one smooth mobilization: celebratory posts coexist with comments reporting wrong colours, autonomous expansion, retaliation and uncertainty about who represents whom.

Relocation becomes the central practice from 634q8y at d2 04-03 05:00 through dfrsgcw at d2 04-03 14:40. An announced agreement says, “Maka, kesepakatan dibuat dengan catatan:” and promises a southern site, rebuilding help and an end to vandalism. Participants stop old scripts, distribute new ones, answer boundary questions and negotiate with neighbours. The move does not settle control: members continue to ask whether borders were agreed, report repaired pixels changing back and propose another smaller flag. A later Dutch-area order at 63720w follows the latest coded proposal to migrate at dfrhm10 by 5 hours 48 minutes; the corpus does not say that the proposal caused the Dutch agreement.

After placement ends, dfsict4 at d3 04-03 23:07 begins a retrospective episode that recounts rogue action, defeat, migration and Dutch negotiation. At d3 04-03 23:55, 63anhk formally closes the campaign with “Membubarkan Komando Perang /r/place /r/indonesia.” Comments continue blaming unauthorized fighters, demanding trials, planning a more defendable flag next time, mourning the lost image and joking about an award of Rp0 phone credit. The last small episode, from 63ego9 at d3 04-04 14:34 to dftey3v at d3 04-04 14:42, uses “our defeat in /r/place” as the reason to offer Dangdut Reggae. The room has not changed its mind collectively; different speakers preserve pride, grief, blame and amusement at the same time.

Relations — what set off what

The early Dutch-flag call explicitly prompts outreach: dfoudla asks, “Why no you guys get helps from r/sweden??? We just make a cultural exchange with them 2 month ago,” and dfow2he answers, “Posted this in /r/sweden, upvote for visibility guys.” The request and reported action support this link.

Several later links are equally direct. An unreadable-coordinate request—“bisa kasih link nya, bos” in dfrcnt4—receives “Sudah diedit bos” in dfrcwbb. A question in dfre082 asks whether green pixels reflect missing information; dfre117 answers that Flying Spaghetti Monster and Dwarf Fortress members are helping clear them. A row-count question in dfrvaf8 receives “Bahas di Discord saja” in dfrvl82, showing a design decision being moved off Reddit.

The record also carries participants' explanations, which are not independent causal findings. In dfsict4, ZxHLnelhmwjP9etjMa1gMposSK4= says “some of our guy went rogue and attack their art, they have valid casus belli”; this is that participant's explanation for the Dwarf Fortress war. Likewise, the southern agreement follows conflict and is acted on when dfrdlyi says “Karena sudah ada kesepakatan pindah tempat” and tells users to stop one bot and use another. These passages show what speakers treated as the reason for moving; they do not prove every participant accepted that account.

Post-event joking has a supported trigger. The Rp0 award in 63anhk is answered by the pointed thanks “Terima kasih atas pulsa yang telah dikirimkan” in dfsoxrj. The final music post in 63ego9 explicitly makes defeat and politics the reason for the diversion. By contrast, the Dutch-area move merely follows the troubled southern rebuild in this record; no passage says the rebuild's trouble caused that negotiation. Relations crossing the slice 04|05 and 05|06 boundaries are therefore carried only where a passage names the earlier action. [crosses 04|05] [crosses 05|06]

Posts against comments

Posts repeatedly present a united room: make a flag, defend sovereignty, follow a war plan, relocate under an agreement, then dissolve the command. Comments show the labour that makes those claims partially real—coordinates, borders, watches, reciprocal help, scripts and negotiated repairs—but also contradict their certainty.

In batch 02, posts call the flag “ours”; comments variously describe it as altered Polish or Monaco space and dispute Touhou's claim. In batch 03, celebratory and presidential posts announce success and defence, while comments report falling pixels, mistaken friendly activity and competing expansion. In batch 04, command posts urge guarding or retaliation; comments disown unauthorized expansion, recommend truces, replace scripts and dispute representation. In batch 05, the relocation post presents fixed terms, while comments ask whether the coordinates are correct, whether information is missing and whether another border has been agreed. In batch 06, the post-war statement closes the command, while comments demand trials, imagine attacks and remain salty about lost ground. Batch 07's post calls it “our defeat”; its sole comment only supplies the music link.

Thus the post layer supplies a clearer institutional story than the comment layer. That is a descriptive contrast, not evidence that the community as a whole moved from unity to dissent or changed its mind.

Counter-reading

My one-sentence reading is: after a delayed start, r/indonesia built and defended a national flag through calls, repairs, scripts, negotiations and relocations, but independent expansion, changing commands and disputed representation kept coordination unstable; after closure participants recast the loss through blame, future plans, jokes and music.

Before searching, I set the consequential competing account as follows: the mock-president and moderator-led posts produced a stable, centrally followed defence plan that the room broadly accepted. If that account were right and my reading wrong, the record should contain members explicitly agreeing on one current command and border, following it without renewed correction, and reporting that the agreed flag held through closure.

I searched the complete supplied record for the case's own agreement, command, holding and coordination vocabulary, then read every returned item. Most broad “agree/setuju” hits belonged to unrelated politics, travel, religion or technology. The strongest contrary item is dfrfvzo: “Koordinasinya bagus dari pakde.” dfrdlyi also shows concrete compliance with an agreed relocation by stopping one bot and giving another. These items change the account by establishing that coordination sometimes worked locally; they rule out a claim of constant disorder.

They do not establish the competing account across the event. At dfrn6lp, members are still asking whether another border has been agreed; 16 hours 52 minutes after the praise in dfrfvzo, dfsl1rx says, “Perintahnya campur campur ga jelas...” and complains that too many threads obscure the latest command. No searched item reports that one agreed flag held through closure. That null result is bounded to this supplied record: missing parents, removed turns and off-platform Discord decisions prevent it from proving that stable agreement never existed elsewhere.

Saturation

Practice saturation is strong for the main flag campaign but late for two practices. Fifteen themes first appear in batch 02: flag-making, design, defence, expansion, scripting, leadership, war-role-play, blame, negotiation, celebration, mourning, recounting, restraint and correction. “Joking and sharing music after the loss” first appears in batch 03 and is extended in batch 07. “Moving urgent coordination into Discord” first appears in batch 04. “Closing the war and planning to do better next time” is genuinely new in batch 06. Batch 07 adds no new practice; it extends the aftermath-diversion theme. Later slices therefore mostly repeat and develop settled practices, but closure itself could not saturate before the event ended.

Record saturation is weaker. One coder read each arbitrary slice, no reader held the raw whole week, and cross-slice relations are weaker than a single-reader account. Deleted and removed turns interrupt accusations. Discord carries urgent discussion, design and ambassador work; Pastebin and GitHub carry scripts and revisions. Reddit shows people choosing those venues and some results returning, but not the decisions inside them. Linked images and final canvas states were not fetched. These limits qualify claims about who authorized expansion, which command was current and whether any relocation briefly succeeded; they do not erase the repeated visible practices of flag-making, defence, negotiation, correction and post-event reckoning.

Selection

The case lead read the briefing and all openings before the gate. Because 2,946 in-window items exceeded the 500-item threshold, seven fleet coders handled whole-thread slices in corpus order. They kept 36 event-touching threads and disposed every thread; long threads whose windows touched the event were read whole. Ordinary politics, travel, news, advice and company April Fools material were excluded unless r/place visibly recruited the thread, as it did with daily chats. Context openings supplied inherited edges but were not coded. The lead did not read raw threads before consolidation and step 4; raw item reading began only for the counter-reading search.

Other communities named

Participants ask r/sweden for help; describe r/singapore, r/Touhou, r/dwarffortress, r/Brasil and others as attackers, rivals or disputed counterparts; offer or receive help involving r/australia, r/india, r/pakistan and Palestine; negotiate space with r/PlaceNL and r/AvoArmy; and discuss boundaries with r/StarlightStage, Flying Spaghetti Monster, Minecraft and Armok. These are r/indonesia participants' characterizations, not verified accounts of the other communities. The relation changes within the case: Dwarf Fortress is blamed as an opponent, approached for truce, reported as helping rebuild, and later revisited in responsibility disputes.

Off-platform and external pointers show coordination moving partly to Discord and scripts moving through Pastebin or GitHub. Reddit still receives links, revised orders, reported agreements and complaints; the external venues supplement rather than wholly replace the subreddit in the visible record.

Absence

Removed and deleted bodies were not reconstructed. Some surviving titles support narrow claims—an attack warning or proposal—but not the missing details. Surviving replies still show disagreement over expansion, representation, negotiation and relocation. Automated mention and preview text was treated as platform setting; human choices to summon, answer, parody or seek action against bots were coded.

No supplied passage establishes a single authorized chain of command, a final shared judgment of success, or a stable flag held through closure. That absence is scoped to the supplied Reddit record and cannot cover Discord discussions, script histories, external images, unresolved parents or removed turns.