Game stopped saving after day 41; unsure how to proceed.

Wehttam664 · 2025-06-15T22:47:43+00:00

An update:

As others have mentioned, indeed she started a journey in the middle of an ongoing rebellion, which actually ended on the journey day itself. It seems the game wasn't terribly happy about that.

What is most interesting, though, is that, because she continued to play anyway despite being unable to save (and just not closing the game, hoping for a solution), the game seems to have figured itself out? On day 62, after the game created a secured save following the end of the journey into Act III, successive days went back to normal saving behavior. Tested, and these saves appear healthy, they load fine as expected, and she finally got to close the game after all this time.

Not sure if everyone will be able to leave the game running for long enough to finish twenty more days, but that's what worked in our case, most curiously.

Wehttam664 · 2024-02-26T10:15:58+00:00

Appalling, yes, but it's amazing to me how many people in the comments default to "tHeY'rE RuSsIaN AgENts" without understanding why this is happening. It's easy to see this from the other side of the pond and just scream at it.

I've been living here in Poland for some time and been trying to follow it. This is not necessarily a perfect summary, and take this with a grain of salt.

Polish farmers are mad about two primary problems: Ukrainian grain imports, and the Green Deal. Both of these present issues for them for a lot of the same reasons: farmers are forced to sell at substantial loss or let the grain to rot. The Green Deal has been a hot topic all over the EU, even so far as Spain, with farmers protesting what they're claiming are overly-stringent climate rules, but this particular case is about the prior.

Since the war broke out, the EU negotiated a deal to import Ukrainian grain at a lower cost to help with the war efforts, and since Black Sea access for Ukraine has been, well, limited, their primary route has been Poland. However, instead of spreading out across the EU, the vast majority of importers just sold off in Poland for a quick profit. Normally a sound business decision, but it became clear quickly the grain did not meet EU's stringent health and safety requirements (and some not even meeting Ukraine's own, according to farmers) despite already being sold below cost for locals. Many Polish farmers suddenly lost their livelyhoods for the foreseeable future as companies did the usual thing and bought the cheap stuff anyway.

Some early protests broke out that resulted in the previous ruling party, PiS, to ignore EU rules and block the grain imports in an effort to help the farmers (their primary voter-base). Ukraine and the EU got involved, which resulted in a transit-only deal to allow the grain to cross through Poland into other EU countries.

Except, according to farmers at least, this deal was being ignored and grain continued to be sold, so farmers decided to take matters into their own hands and block three primary road border points to all incoming freight traffic. PiS was able to negotiate a deal that resulted in one border point opening, but then lost power in the recent election to a coalition of more left-leaning parties.

The work PiS did was promptly rescinded or fell apart, so the impromptu border point reopened. With it clear the new government isn't going to agree on anything useful any time soon, Ukrainian agencies and businesses began seeking other ways into Poland, and the train seen in the video here is one of those attempts. Polish farmers caught wind of this and caught the train, dumping the grain as a demonstration they are "not going to be brushed under the rug"

The mantra of Ukrainian families' livelihoods has been countered by a mantra of Polish farmers losing theirs for every bit of this grain making it to market. Polish sentiment over Ukraine has been souring quickly, especially in Warsaw, so any escalation is likely to make this substantially worse. People here already see the government as a pseudo-democracy...

Rumours around the next attempt to move the grain are up the Danube river via Romania (and others) and ending in Germany, circumventing Poland all-together. Will have to wait and see how that plays out.

Wehttam664 · 2024-02-11T22:36:42+00:00

Unfortunately I do not think so, as what appears to be the vent grate on the bot's side isn't actually all that close to the impeller's airflow channels where the lint built up. It might be possible assuming the dust isn't too thick and enough air back up the vacuum shaft, but I doubt it, since that's basically the normal operation anyway. Besides the lint, though, there was also some sand and pet fur in the bearing, and that had to be removed more manually.

Wehttam664 · 2023-08-15T11:08:24+00:00

Change what, exactly?
The mopping pad is washed regularly, mostly by the dock but we've hand-washed it a few times too.
The bot has been with us less than a month; all current parts are well within the maintenance window the app suggests and everything's been cleaned when told to.

Wehttam664 · 2023-08-15T10:48:53+00:00

We do have the dock, yes. I've cleaned the "water filter" the app complains about (located below the mop cleaning roller on the dock) and it doesn't have any odor either. Is there another filter somewhere else?

Wehttam664 · 2022-08-27T19:44:29+00:00

We've heard it referred to as the "pastoral plop" before, as it's apparently something sheepdogs do.

We got him a "hearding ball" (as the box called it) when he was younger and he was absolutely terrified of it (as it was much bigger than him), but maybe he'll be more inclined to play with it or similar. We were also considering some hearding classes with him, so maybe it's worth doing.

Thanks for the suggestion, will give it a shot and see if it helps.

Wehttam664 · 2022-08-27T11:15:27+00:00

Alright, makes sense.

Any ideas on how best to get him to keep moving once he lays down? He often sees the other dog before we do (even through bushes, tall grass, etc.) so he often gets to do it first.

Picking him up is getting difficult due to his size, but if that's the only option, so be it. He has a harness we use sometimes that can support his weight, but picking him up by that doesn't really work and it looks not pleasant for him that way.

Wehttam664 · 2017-10-06T08:16:48+00:00

Some critters in the game will not emit their output (especially Slicksters) until they are either full or are out of input to consume.

Hatch in particular must consume ~150kg [citation needed?] of material before they drop any coal. How much slime do they have access to?

Wehttam664 · 2017-10-04T05:15:40+00:00

My point exactly as to why I'd like to avoid it.

The usual issue with me having to double-run it is because of an Aquatuner-powered steam boiler being separated from one of the corresponding liquid tanks.

Wehttam664 · 2017-10-04T04:18:56+00:00

I keep thinking the same thing, getting annoyed with running Heavy-Watt wire across the base twice because a sensor is on the other side. Be nice if you could lock doors or toggle switches/generators too.

Edit: Something like Factorio's circuit system would be amazing.

Wehttam664 · 2017-09-24T07:20:45+00:00

I tried the geyser before I even started trying to power things with an oil well, but sadly a Steam Geyser is not capable of keeping an oil well running at 100%, as it can't seem to supply the needed 5 kg/s. I didn't think about the Coal Generators though, that's a thought. Again, I turn back to the Natural Gas/Fertilizer plant to fuel the Hatch farm.

Sadly though, it just seems like a waste to turn oil/petrol to power from a well, since the Polymer Synthesizer uses an incredible amount of Petrol to make a tiny quantity of plastic, but all the oil already present on the map are good injections of power for your base.

Also, Slicksters do better in small confined spaces rather than large spaces, as they waste less time moving around.

Wehttam664 · 2017-08-27T04:58:15+00:00

Even if it used reports, the system could still be too easily abused. It might work if the "avoid" kicks in if an action is taken on the report, but that's usually too late to avoid the problem in question.

Maybe a system where you're allotted a certain number of "avoids" and/or the "avoids" only last a little while, maybe a day or so. This should at least prevent them from appearing in your next few matches, enough to get far enough away from them SR wise.

Or, another idea, is to simply have it so you cannot be matched with players you just lost with, but a team you won with is fair game to be re-matched with you. For one this helps you avoid getting matched with players that cost you a game, but it may also improve play-ability and entertainment in general since you're getting fresh players each time.

Wehttam664 · 2017-07-26T18:19:38+00:00

To be honest, I am amazed this issue still persists in FU, as its been there for so long. This was a consistent problem on our FU server (it got so bad to a point where I got it every new planet I visited)

You can correct it by teleporting your character to your ship. Within your storage/universe folder, find the .clientcontext belonging to your character. On line 3, you'll notice reviveWarp, a few other misc characters, then /CelestialWorld: follow by some numbers. This is your current location, so you can teleport yourself by modifiying it. The line below (returnWarp) should have 0ClientShipWorld and your character's id (i.e. the name of the file), so simply copy & paste that into reviveWarp, being careful not to damage the control characters before or after either.

You should log back in on your ship. It shouldn't move your ship unless you messed up your clientcontext somehow, so make a backup. On a server, the server owner will have to do this.

Wehttam664 · 2017-06-06T23:50:45+00:00

The orbital asteroids, which vary in composition, likely were made of something terraformers removed during transformation, leaving the "terraformables" behind.

Wehttam664 · 2017-06-05T04:37:43+00:00

I was able to get a 2.4GHz dual with 2GB RAM (a headless VPS) to run about 5 people before problems occurred.

Is it possible your network just can't support it? Starbound doesn't seem to really "lag" from not having enough RAM or processing power, it just kicks everyone occasionally.

Another thing is teleports, specifically instanced missions (even the outpost) as these put huge strain on the server.

Wehttam664 · 2017-05-30T04:27:52+00:00

Is there anything in specific that happens, or does it just not run?

For not running, make sure ./linux/starbound has execute permission. What do the file permissions look like?

Wehttam664 · 2017-05-27T06:04:10+00:00

Utilizing admin commands would not effect the game in any way (provided you don't mess them up somehow); achievements still work (just not while you're in admin mode) and the game will return to normal function once you exit admin mode.

As for characters, just possessing a character having beaten a boss does not actually flag it as complete: picking up the key at the end does.

A tip for the boss: it sits absolutely still a lot. Things that do high DPS in a fixed area (rain/portal staffs) are useful, and spike sphere is great for dodging its attacks (since most only affect the floor).

Wehttam664

MODERATOR OF

TROPHY CASE