Diff

Only if you can't see the relationship between clearly parallel events. What you are failing to see throughout all of this is the internal mechanisms of the in-game universe. Again, alternative explanations are possible, but: This sure ain't it. This isn't an explanation. There's no in-universe mechanism for this. It does not engage with the themes of the game. The returning point is the point where the seraph returned to the world. That all ties together nicely. Internal universal consistency is not circular. Nothing here is sacred or unchangeable. And it's not like the game doesn't have holes in its universal mechanics. Just keep from ripping open any new holes in the universe. Separate objects could work fine. Anchors found in ruins sound workable in terms of in-universe mechanics, although the mechanics around discovery like you describe sounds dreadful from a gameplay perspective. And on lore, what are anchors capable of holding a seraph doing in ruins from a time before seraphs? That has a fix, but what is it? All Jonas tech is far too end-game to be useful and IMO don't address the fundamental differences of seraphs. Temporal gears have the same weirdness seraphs do. That's aesthetically nice. Respawning in-game and respawning in-universe rhyme. Having the same explanation is aesthetically nice. It makes a world feel more cohesive and real. I can't speak for others but when I point out lore it's rarely because I'm clutching my eldritch game bible and preaching. I'm pointing out elements that depend on or support whatever it is we're talking about. If that element updates, its dependencies should update as well. And it shouldn't be done by reducing the number of links. Or, again, toss it in as a non-default worldconfig and forget about it. Only the defaults need to worry about lore at all.

Has very little to do with the specific words "energy" or "flow" so that's not so surprising, but you did find the end of Chapter 2. That's (mostly) what I'm referring to. There are a few scraps of lore before the main story though. And beyond temporal gears allowing you to temporarily move your returning point, there is one other game mechanic that interacts with them. The base return teleporter teleports you to your returning point. That makes little sense without there actually being something physically distinctive about that location. When they die, seraphs always return to the point they first re-entered the world. You can re/write lore to make that make sense some other way. I'm still eager to hear any alternative lore ideas you have for sleep being tied to respawning. And of course it can always be a convenience/configurable option. But the current mechanic makes internal sense and ties nicely to the lore.

Nah, this lore is established in other ways in the discoverable bits of lore you dig up. Seraphs are immortal because they are anchored to a point in time and space. The temporal gear lets you exercise some influence over that returning point. But the returning point and the seraphs' immortality are the reason seraphs exist at all. The logic isn't circular, it's closed. No loose ends. Can it be changed? Sure. But offer another closed alternative. What logic is there to taking a nap altering a point in time?

Rainbow's saying that you will starve faster if you are hurt.

Edit the existing release and it'll let you re-select the versions your mod is compatible with

I think it would work, it worked for me with Terrain Slabs, but with more severe changes to worldgen I think there would be a visible seam between any new chunks and old chunks.

if nobody's on, shouldn't hurt a single thing to let your laptop take a break.

I think it's lore-related. Seraphs are immortal and are anchored to a specific point as part of their nature. You can alter that returning point with a temporal gear, but you are temporally anchored to your returning point and will always respawn there until you take action to alter it.

We do it all the time with products. Provenance is important. A lot of people loved Fairlife milk not for the milk, but for its provenance until it came out that they are actually beating those cows. Nothing physically changed about the milk before or after that news broke, or before or after they started beating their cows. Blood diamonds, "Made in the XYZ," "locally owned," Fairtrade-, Utz- and Rainforest Alliance-certified chocolates, responsibly sourced conflict minerals. It's a very, very common and routine thing to choose and identify products by provenance of their component parts. And AI does have its own ethical issues. You may ignore it, others choose not to, but it's not difficult to imagine at all. "WHO" is also an easy discriminator. If someone consistently releases poor quality mods, you may choose not to engage with any of them, rather than waste more time investigating. AI is that someone for many. As mentioned elsewhere in previous topics, practically, AI mods have a higher failure rate for performance, for bugs, and people may choose to avoid the whole class. It's not that human-made mods are immune to having problems. But the rates are far different with 100% human-authored code vs AI autocomplete vs vibe coded nonsense. With no disclosure, it's impossible to tell how AI was used in a mod, and it's often less of a headache to just skip the mod.

Why avoid something largely beneficial that will decrease overall bad vibes and conflict just because it won't solve every instance? This kind of behavior is likely already covered by the rules, as evidenced by how these topics always get locked.

You see echoes of that on the forums. The discussions often get heated so they're quick to act on the forums.

Isn't that at odds with the part of the flavor text that says "even when resisted?" Them being very durable is also at odds with them being relatively easy to shatter to create a returning point, unless the shattering isn't like physically based.

You can probably do it but it's likely to be more effort than it's worth. If it's a recent version, it's probably more reliable and easier to go the downgraded-flatpak route like hstone's thinking.

I don't think that's right... it's typically only pushing that's privileged. If nobody can pull, I don't think you'd be able to install the app at all. I found some hints on the internet that you just need to initialize Arch's keyring. This also doesn't entirely make sense to me, but there's multiple people saying it works so the incantation for it is: sudo pacman-key --init && sudo pacman-key --populate The other advice I see is removing and re-adding the remotes: latpak remote-delete flathub flatpak remote-delete flathub-beta flatpak remote-add flathub https://dl.flathub.org/repo/flathub.flatpakrepo flatpak remote-add flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo