• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle




  • There are definitely technical reasons why saving mid-run is a lot more complicated. With Pacific Drive, right now when you save, it’ll save:

    • the state of your car - this will likely be done by looking each individual “equipment slot” the car has, assigning them a number, assigning each possible upgrade for that “slot” a number/letter, and storing its damage state (which is probably just a scale of 1-5 or whatever). So the game will store everything about your car in the format off “slot x, upgrade type y, damage z”, which can just be three values.
    • your quest state. The game won’t remember what quests you’ve done or how you’ve done them in the way that you remember it - it’ll just store that you’ve completed quest step 14a and that 14b is your active objective.

    It makes for a fairly simple, small save file. Being able to save mid-run would add a lot of complexity because it’d need to save a complete map state, including:

    • the map layout
    • your position in the map
    • the enemies and hazards in the map - their positions, states, etc.
    • what’s happened already in the map
    • the loot in the map, and whether you’ve collected it or not

    And so on. Not only does it massively increase the complexity, it would also increase the size of save files a lot and make saving and loading a lot more cumbersome. And that’s just a simplified breakdown; there are definitely other factors that can make it much, much more complicated.


    There are definitely some games where “easy mode” save systems could be implemented without much changing on a technical level, but I don’t think Pacific Drive is one of them.


  • I’m not cheering for the layoffs, of course, nor am I necessarily in favour of monopolies and the consolidation of the gaming industry (although, in this instance, I think it’s probably a positive thing for fans of Blizzard IPs). But layoffs during this kind of merger/buyout are expected. Microsoft has its own legal departments, payroll departments, marketing departments, etc, and while they might need expanding slightly as the company grows/absorbs new companies, they don’t need an entire second company’s worth of those departments.

    These layoffs were about cutting redundancy rather than just chasing short-term profits. It sucks for the people who were laid off either way, but I think it’s good to be realistic about why they happened.



  • So a few things:

    • sorry that’s been happening to you, it must suck
    • the Reddit admin’s response doesn’t seem great
    • this isn’t a relevant place to be posting this
    • your tone in the DMs with the admin and in the comments comes off as overly panicked and alarmist. It’s going to be hard to win anyone over like that. Take some time, write it up with a more calm and informative tone, add proper context, etc.
    • you’re not going to get your story out there by spamming it in random, inappropriate fediverse communities. If you’ve got solid evidence, email a journalist at a place like The Verge or Ars Technica about it. Just don’t expect them to care if you don’t have evidence - right now, it just mostly reads as “user upset that Reddit admin didn’t ban other user”. Yes, it sucks, but it largely just reads as a social media drama piece at the moment, and not anything with any real substance to it.
    • or just report it directly to law enforcement





  • It’d make for a good anti-spam measure if there was a limit to the number of DMs users could send to other people who don’t follow them back. It’d mean people can still use Twitter DMs like a normal messaging service (which isn’t something I care for, but I know some people use it like that).

    As it is, it just feels similar to the whole “rate limiting the number of tweets people can view per day” thing, where they’re taking the most obvious route to reducing bandwidth usage by restricting users.