I played Hollow Knight. I don’t recall if I defeated a single boss. I must have done a couple but several of the first you were meant to defeat remained unchallenged.

There are non boss fights that get more elaborate as you go, and let you pick up some new skills and abilities.

Another one like this that shouldn’t have been was Orie and the blind forest. If you play it on story mode, which I did because it was great eye candy and I just wanted to see it all, there a spot in the middle of act 2 where you have to land several double wall jumps in rapid succession with nearby spikes. Someone at that studio needs to be beaten about the shoulder with a clue bat about wtf “story mode” means. I never got to see the story and was too mad to watch someone else play it on youtube.

I’m fairly sure that my problem with both was the same. Only partly fat fingers and part was that certain movements don’t work identically on all controllers. Some things are counterintuitively easier on a D pad than a thumb joystick. It’s just not as crisp to go from one input to another 90 or 180° opposite. If your game mechanics are built on that, then some ports will be much harder to play.

You should either not port them, or adjust the timing grace period up on that hardware.

Regarding controls, I have to play precise 2D games with a d-pad or I get immediately frustrated— that said, it was odd playing most of Celeste that way and then having to switch back to the thumbstick for the section at the end with the bubble comets.

I was just wondering about control setup and latency as a major factor in a game with very strict timing requirements. Last time I played was on a TV (over HDMI in game mode though), with a wireless Xbox controller. I wonder how much easier I'd have found it on a 240Hz monitor with a wired controller?