• 0 Posts
  • 49 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle

  • Totally.

    I didn’t know games could come with professionally printed labels, when I was a kid with no income. I thought everyone just got them on disks labeled in marker from a good friend of the family.

    It’s important to me to support developers, but I can’t say I regret getting to play those games before I could have ever afforded them.

    I’ve since gone on to buy those same games from their developers several times over on various platforms.


  • Why not both?

    Because DRM misfires for a small percentage of paying customers.

    Those paying customers, ironically, usually get help from the pirate community to get their game working.

    Then they go back to paying for everything, because they still trust game studios more than pirates. Wait no, this last bit usually doesn’t happen.

    Overall DRM prevents zero percentage of all privacy, while hassling a small percentage of paying customers.




  • Don’t make me point to the sign with people standing on boxes in front of a fence.

    This should be very easily solved with matchmaking lobby settings.

    Anyway, most accessibility settings are either something every competitive player should be using anyway (reasonable color contrast settings, HUD tweaks for clarity) or things that only people who need them despately would ever use (remapping all buttons to be able to play using only a stick in the players mouth, because they have no hands).

    This seems to me like a total non-issue. And in the very few cases it is, the ranked lobbies can just diable that setting.

    The backlash was probably because for you and I a harmed pvp experience is a “could happen” while for a bunch of gamers the lack of accessibility is a daily undeniable part of their reality. For some people, games are a critical sanity-saving retreat from the rest of their life. Let’s let them have their tweaks outside of ranked play.












  • With only 2 developers, CI/CD can be your best friend. Automate the daylights out of testing your code.

    Remember to tag your regression tests in some way - any test that is preventing a production bug that actually happened needs to be marked as a ‘regression’ and treated as high priority to keep passing.

    Treat all others tests as more art than science. Keep the reliable ones, toss out the brittle ones.

    Look for a network traffic recording/replay library for your toolchain. Reusing integration tests as unit tests is a huge time savings.

    If you have live data access, build yourself a few charts that represent a typical day. Knowing what “normal” looks like in your database can be priceless on a weird day.