Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)JE
Posts
2
Comments
128
Joined
2 yr. ago

  • Not to mention the absolute clown show of Star Wars: Battlefront (2004), Star Wars: Battlefront II (2005), Star Wars: Battlefront (2015) and Star Wars: Battlefront II (2017). Come on, 4 isn't even that high of a number.

    I'm wondering if the aversion to numbered titles has to do with execs wanting to divert attention from the sheer number of sequels and reboots being churned out by AAA studios, often way beyond their franchises' reasonable ending points. I remember when Final Fantasy was often the subject of mild ridicule for its absurdly-high sequel numbering, and at this point, a lot of AAA franchises would be starting to get into the double digits. Dropping the sequel numbering may be an effort to get people to forget just how long those franchises have been milked.

    That's not the case everywhere, and I think sometimes on reboots they just want to signify that the franchise is "starting fresh" to a degree (Doom and SW:B for instance), but it's still aggravating that completely-identical title repeats are for some reason acceptable now.

  • "Mortal Kombat 1?" Really? I'm getting pretty tired of this whole trend of really confusing reboot/sequel names that make it increasingly difficult to convey which actual game is being referred to. I kinda wish more games would take the Final Fantasy route and just own their ridiculously long sequel count.

  • It does some funky things with type coercion and comparison which I don't particularly like, but I generally understand why it does things that way.

    A lot of the weird quirks of JS come from the desire to avoid completely blowing up and crashing as much as possible, which makes sense in a web dev context. Forcing weird operations to at least return something can prevent an unhandled error state in a single component from causing an entire page to crash, even if that component ends up malfunctioning as a result.

  • IMO, smartphones had the chance to revolutionize the gaming industry, but ended up wasting almost all of that potential on skinner boxes riddled with ads and microtransactions. Most of the best mobile games are ports from other systems, like the mobile edition of Minecraft and whatnot.

    I think Pokémon Go was possibly the closest any major publisher has come to actually realizing the full potential of mobile games as a format, but it still fell painfully short with massively dumbed down mechanics and an absolute grindfest of a progression system.

    There are still a few good indie projects out there (I like Soul Knight) but generally the mobile gaming market is so full of absolute dreck that I usually just don't bother.