• 2 Posts
  • 184 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle




  • Yeah, they hotfixed that like 5 minutes after launch, and it took a little while for Steam to catch up for everyone.

    FactoryGameSteam.exe is definitely correct, probably because they now maintain FactoryGameEpic.exe and maybe a couple others, for the console releases they"re working on. But they seem tobhave neglected to instruct Steam that the exe name had change, so Steam was still looking for FactoryGame.exe. Renaming the file was an effective workaround for the first hour or so.







  • #4 for me.

    Proper HTTP Status code for semantic identification. Duplicating that in the response body would be silly.

    User-friendly “message” value for the lazy, who just wanna toss that up to the user. Also, ideally, this would be what a dev looks at in logs for troubelshooting.

    Tightly-controlled unqiue identifier “code” for the error, allowing consumers to build their own contextual error handling or reporting on top of this system. Also, allows for more-detailed types of errors to be identified and given specific handling and recovery logic, beyond just the status code. Like, sure, there’s probably not gonna be multiple sub-types of 403 error, but there may be a bunch of different useful sub-types for a 400 on a form submission.