Leaderboard

I think brief time limits for specific challenges are the way to go, and there should never be an absolute failure state attached. An easy example is a mini-game inside a mini-game collection like Mario Party - the timer creates tension, yes, but even if you fail, there's plenty more chances to make it up because that challenge was one of many you'll be taking on. When you do eventually lose the game, it feels fair because your failure is a result of repeat losses, not one. In an RPG context, the same approach works fine - give the player a limited time to accomplish an objective, perhaps with negative ramifications for failure, but allow the game to continue. Fallout would have actually worked with this; its open-world nature meant that the player could still win without ever saving Vault 13, so why not simply give the player a different ending if the Water Chip is never recovered? There's a story consequence (your friends all die), and a gameplay consequence (less direction/info on taking out the Master), and none of it would feel especially unfair either. Perhaps saving Vault 13 could have been a more multi-part objective with a mix of different limitations, hard and soft. Multiple outcomes with a sort of granularity in success would have also been just as fair. For example, perhaps you side with the rebels and convince them to open up to the Wasteland, saving the Vault but ruining its safety and lifestyle. The details of course require tweaking to make everything interact and operate smoothly (which endings trump which?) but you get the idea. As you brought up, System Shock 2 had time limits attached to inventory items (upgrades), and I think this is also a much more fair sort of limit to include in a game. While charging stations were fairly plentiful (at least one per deck of the ship) it still provided benefits while also encouraging the player to make ideal use of time. It's a timer, yes, but it's disguised both in gameplay and narrative. In that sense, a game like Fallout also has a timer - ammunition - but you can also use others like food supplies to accomplish the same. Instead of an annoyance, it becomes a game mechanic for the player to consider. The only real issue here is development time and priorities. I can appreciate the want to tell a specific story and limiting the player's choices because of it, just as I can also appreciate that implementing so many different outcomes may not be feasible for most games. Ultimately the question isn't just how to implement time limits in a fair and effective way, but whether it's feasible. Doing it mechanically is probably the best bet when budget is a concern - building unique situations and outcomes for different possibilities is tough, but expressing that same thing as a game system is comparatively much less work.