• 0 Posts
  • 18 Comments
Joined 4 months ago
cake
Cake day: June 12th, 2025

help-circle
  • I’m definitely overstating for effect, but yeah, to me, the game very much feels like they wanted to cater to the inhuman speedrunning and challenge running crowd from Hollow Knight, and made things unreasonable for causal/average gamers.

    Maybe my bias is in having played and loved Hollow Knight first, but I NEVER felt like I was being given an unreasonable challenge in Hollow Knight. And Hollow Knight, by the late and post game, is HARD. They just managed to balance the difficulty curve so masterfully, that every escalation felt natural, even exciting.

    Silksong, overall, did NOT do this for me. The early game felt obnoxiously punishing, the mid-game completely fell off a cliff into easy, once you get a handful of key upgrades, and the late game just varied all across the spectrum.




  • There’s about 3 different “no double-damage” mods that I’ve tried, for a boss I just couldn’t be assed to try legit, anymore. They all seemed to work, fine.

    There was a “respawn outside the boss room, instead of at a bench” mod that I installed for a particular boss (you can probably guess), but I can’t really speak about whether it works, cause I happened to beat it on the next try after installing.

    There was an “infinite shards” mod I tried, but it didn’t work at all, and I didn’t see any others, so be wary of that one.

    Referring to mods available on Nexus Mods, BTW.









  • These all sound like good improvements to WASM as a binary target, but… how do we STILL not have access to any kind of I/O? How is that not the #1 priority? No access to the DOM, no access to local storage, no access to networking… WASM will continue to be borderline useless until it can actually do the things an application needs to do, without having to implement some hackjob JS interop layer.







  • That’s a perfectly valid approach, yes. We do exactly this, at work. It’s pretty common, if not ubiquitous, to have your database schema consist of not only structure, but data as well. We call it static data, and it’s all defined in deployable scripts, just like our tables and views are. If ISO makes changes to the dataset, then it’s just a table update to match it. And ISO is nice about keeping backwards compatibility inb their standards.

    Since this is not strictly your own data, you could also go with just storing the code value on your tables, and letting the UI layer do the lookup, either with built-in features of your language/framework, or with a static csv file, like you mention. You may not want to do this for static data that is entirely your own, like, say, a status or type enum, since it makes your database schema less-self-descriptive, and more prone to becoming invalid.

    You could also set the country code up as a not-strictly-enforced foreign key, where your app will lookup additional info (E.G. the proper name) for a country code, if it’s a standard one, but just skip that if it’s not a standard one.

    It’s up to you what you think is most appropriate.