{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihyeduuoeu3ob7z2s3lyjmzyiagu555uczx5j7o4gtdpfkpjj5rvy",
    "uri": "at://did:plc:pvz7ox4x2ehjiezsahttqyyz/app.bsky.feed.post/3mfjzajvvsxi2"
  },
  "path": "/viewtopic.php?p=449714#p449714",
  "publishedAt": "2026-02-23T15:12:30.000Z",
  "site": "https://forum.luanti.org",
  "tags": [
    "rudzik8"
  ],
  "textContent": "> > ## Clonti\n>>\n>> Mineclonia-specific desktop Luanti builds with user content stored globally (RUN_IN_PLACE=1) and halon's (SS)CSM support enabled\n>\n> [...]\n>\n> isnt \"RUN_IN_PLACE=1\" locally ?\n>\n> shouldnt it be \"RUN_IN_PLACE=0\" for globally ???\n\n_globally_ is in reference to _user content_ and is relative to the \"installation\" that is produced by extracting the tarball/zip. All user content in this case is stored where the binaries are and all users (if more than one) would be sharing the same user content. _locally_ then would mean every user stores their content at their own home folder, not where the binary is.\nIf you have a better term for this, please share it with me. I think I put \"locally\" instead of \"globally\" there originally but then flipped it because that seemed more logical.\n\nStatistics: Posted by rudzik8 — Mon Feb 23, 2026 15:12\n\n* * *",
  "title": "Luanti-related projects • Re: [Windows/Linux] Clonti: Mineclonia-specific Luanti builds with halon's (SS)CSM",
  "updatedAt": "2026-02-23T15:12:30.000Z"
}