Freight Fate v1.8.8

Changed

• Connecting a computer to orinks.net no longer involves copying and pasting anything. Setting up online features used to mean copying a Driver ID and a token from the website and pasting each one into the game. Now the game shows an activation code, reads it out loud, and can spell it letter by letter or copy it to the clipboard if you would rather type it into the browser yourself. Once you confirm the code on orinks.net, the game finishes connecting on its own.
• Automatic Mastodon posts moved to their own hashtag. Deliveries shared to your Mastodon account now carry the FreightFateRuns hashtag instead of the FreightFate one. Players use the FreightFate tag to share their own thoughts about the game, so anyone who had muted it to keep the automatic posts out of their timeline was quietly losing those conversations too. The two are separate now: FreightFate is for people talking, FreightFateRuns is for the game posting. There is nothing to change in the game. If you muted the FreightFate tag because of the delivery posts, you can unmute it and mute FreightFateRuns instead, and if you liked following other drivers' runs, follow FreightFateRuns to keep seeing them. The change is on the orinks.net side, so it already applies to every version of the game.
• The automatic transmission works each gear harder before shifting up. Pulling a load, the engine now runs into a higher, more realistic RPM range in every gear instead of grabbing the next one early, so climbs sound and feel like the truck is actually working. Running empty, the two-gear jumps the box likes on flat ground now land far enough above the downshift point that it no longer shifts up and immediately drops back down. Contributed by corykad (@corykad) in PR #144.

Fixed

• Picking a lower gear with the clutch held no longer damages the engine. Downshifting several gears at highway speed used to bring the redline warning and engine damage the moment the gear was selected, even with the clutch to the floor and the engine disconnected from the wheels. The warning and the damage now begin only if you release the clutch while the gear is too low for your road speed. Contributed by corykad (@corykad) in PR #144.
• Copying to the clipboard works on Linux. On Linux, copying a delivery summary, a reviewed message or a link always said the copy did not take. Linux desktops offer clipboard text under a different name than Windows does, and the game was only ever asking for the Windows one. It now asks for the names Linux really uses, so copying out of the game works, including copying your activation code during online setup. Windows and Mac are unchanged. Thanks to a player report.
• Continuing a saved run announces the right date and season again. When you picked a run back up, the calendar went back to the day you set out on rather than the day you had driven into, so a haul that had rolled past midnight came back on yesterday's date, and a long run that had carried you into a new season heard the old one, with the weather to match. Continuing a drive now puts the calendar at the same moment your trip clock is at, so the date, the season and the weather all agree. Contributed by Day Garwood (@day-garwood) in PR #146.
• Continuing a saved run no longer pushes your deadline further out. Every time a delivery was picked back up, the game worked the deadline out again from where you were and how long you had been going, which quietly gave you more hours than dispatch had agreed to. A run you were running late on could be rescued just by saving at a stop and continuing. Deadlines now stay where dispatch set them. A run already under way gets one last recalculation the first time you continue it after this update, so nobody loses hours they had been counting on, and it is fixed from then on. Contributed by Day Garwood (@day-garwood) in PR #146.
• Quitting mid-drive writes a save that agrees with itself. Quitting to the title mid-drive puts you back at the stop you last saved at, but the save was still being written with the hours of service and the fatigue you had built up since leaving that stop. Continuing always put them back, so the drive you returned to was correct either way, and this only mattered to the cloud backup, which was storing a shift that never happened. The save now records the stop you will actually resume from. Contributed by Day Garwood (@day-garwood) in PR #146.