We've all heard about points of no return, but I've been having difficulty with points of "next intersection in 5km."
More specifically, I've encountered a couple times recently in big RPGs where installing a temporary restriction ends up breaking the intense mood that seems to be the reason for the restriction in the first place because of the gameplay balancing concerns. I've kind of nicknamed this 'rift prevention' to myself, after an old experience where temporary loss of backtracking led to a long and painful brute force solution.
Effectively, the core problem is that the game can't tell the exact capabilities of the player's setup or how well they can adapt to whatever's hitting them next. It's entirely possible they barely scraped by the last encounter or boss. In that case, they would need to spend some time regrouping/grinding for a subsequent encounter that's more challenging or demands a different composition. This part is just a description of a difficulty curve. The issue arises when the ability to regroup/grind is cut off just after the player scrapes by. The player getting stuck is a very bad outcome, because being stuck is not a good gameplay experience. But then, in order to ensure the player isn't stuck, you either need a designated grinding area or to ensure that the encounters don't scale much until full access is returned. If the vibe you're going for at this point in the story is that the characters are desperate, that doesn't align with the gameplay constraint. The lack of continuity in the difficulty curve's slope is also pretty jarring on its own.
The two specific examples that really brought this to mind are below:
Xenoblade 3, Chapeter 5/6 spoilers
The game is usually clever with its exp setup to try to keep the players on-level despite the wildly varying amount of sidequest content a given player is likely to do. Exp can be earned by doing things not directly related to combat like completing quests or exploring the map but these sources only actually apply to the character levels when the player requests it. Grinding fights for exp is then redundant: if you're underlevelled, you can just do some sidequests from a previous area. This also allows for sidequests to be more story-focused instead of just a container for fights. There are other minor issues with the system as implemented (still needing to grind for item drops, for example), but only one's of major relevance here.
Late in Chapter 5, the party is infiltrating a prison and are cut off from the rest of the map by what might as well be a ledge in an older pokemon game. Which means that the system described above immediately starts breaking down. How can the player replace combat grinding with sidequests if they can't access the sidequests? Well, everything's still fine as long as there isn't anything too important at the end of the segment. Oh wait, it's the most important story bosses this side of the endgame.
The game tries to resolve this by including some quests within the prison itself. But these aren't the lovingly created vignettes of the rest of the game. These are straight up the time-wasting "get me 20 of X item" quests that are heavily abstracted elsewhere because people don't like playing them. Which are required to do for everyone, not just the poor fool who can't beat the next boss. Did I mention said boss is the second most gimmicky in the game, you don't have access to the extra party slot during it for reasons (would have been a great and easy to explain in-story moment for the Nopon to kick some ass too), and detailed changes to the rest of the party require a resource that you *don't* get from quests?
Oh, but we're not done yet. There's still two (or three, I don't quite remember) fights after this, and no room for even blatant-padding quests. So they're just way easier than the first one. Let me tell you, "just get this crap over with so I can get back to an actual party menu" is pretty much the exact opposite of the state I was supposed to be feeling at this point.
FE Engage, chapter 10 spoilers
This segment has a retreat map after a failed offensive, with the team stripped of the super mechanic and carrying over the units from the previous map.
I get it, a retreat map can be to get correct in Fire Emblem. When so much of the game is fighting outnumbered 2:1 or more, it can be hard to accurately portray an overwhelming force. Going in to the map, I had pretty high hopes. After all, I was well aware of how much auto-hitting damage the enemy had access to. But they didn't use the vast majority of them, only the one that can put its user out of position. Between that and a lack of mages, there wasn't anything that threatened my covert units in the ample forests. I expected constant enemy reinforcements that never came, only a group that showed up at the very end when I was "rescued" (reached the final part of the map after clearing the vast majority). It felt disappointingly easy.
It definitely feels like this is due to the placement of the map. It's possible that I would have been required to play this with less than a full squad if characters had died in the proceeding map, and the rewind mechanic was disabled by the plot (for 75% of this map only).