Hcfyk

Use ability every N minutes of real time

Since it is a turn-based game, the player can just wait for the ability to be available again.

Use ability once or N times per day (sleep to restore, or wait out day-night cycle)

This works well in the The Elder Scrolls serie because you cannot rest if ennemies are nearby. Meaning, if you are in a dungeon for example, you can probably only use it once for the entire dungeon (not saying it cannot be abused, of course).

If you plan to implement this in a turn-based game, just make sure that the player cannot rest whenever, which would make negate the interest of the reloading time.

Use ability every N turns of combat

In most game, there are often mechanics tied to resource management. For example, your more classical mana-using mage have to manage its mana pool, so he has to make choices about what spell to use. This is interesting for the player.

Your "Use ability every N turns of combat" mage however, doens't have to make those choices, since each spell use its own resource, so to speak. Therefore, the only question the player has to ask himself is "should I keep this spell for later in the fight or use it right now?" (since I assume every cooldown is reset when the fight is over).

I believe this is a less interesting choice, because for example, if you decide to heal an ally for 50 HP when he has 50/100 HP left or 10/100 HP left does not make a difference on the result of the fight.

You mentioned items to restore the cooldown of the spells. They are analogous to mana potions in this case. Therefore, I don't think it solves the issue of your cooldown-based mage being less interesting than a mana-based mage.

Side note

Have you played pen and paper RPG already? Most of the times, those games include spellcaster classes with different resources mechanics. Take a look at Pathfinder classes for example, maybe this could be interesting?

If you make your game a dynamic game world, where things happen as time progresses, and adversary positions, actions, and their own "recharging" effects are also tracked, then you can get a game with natural trade-off consequences from resting without doing anything, because it costs:

• opportunities to take action before the situation changes will be lost if/while the player(s) do nothing but rest




• adversaries can be taking actions the players don't want to happen, while they rest, and other events can happen in the game world




• adversaries can be resting wounds and recharging their own abilities while the players recharge theirs

As Wazpoodle noticed, the problem is mainly that defending for a long time do not have any other drawback than time.

All the propositions revolve around giving the player other things to do during the waiting time, but in combination to those, you may also privilege fights that end quickly.

For example, a fight that is finished in the first 3 turn may give a additional bonus (XP, money...), that degrade slowly over the duration of the combat.

If the player want to turtle, he will receive a reduced / no bonus.

This would incentivize this class (the burst attack may be enough to end the combat on the first turn), while also pushing the player to act now and make do if the burst is not enough.

A very useful way to think of balancing combat is that you have exactly one goal:

Reduce the damage done to the party

"Heal" is the most obvious way of achieving that goal: it simply erases the damage done.

"Defend" is another direct means of doing so, via diminishing the effectiveness of enemy attacks.

"Attack" is also a means of reducing the damage done to the party: if a player does enough damage to an enemy so that it dies one turn sooner, then that player has achieved the effect of sparing the party from an entire turn's worth of damage.

If you don't want it to be optimal for players to usually choose "defend" rather than "attack", then the trick is to adjust the numbers so that attacking saves more damage than defending does. I think the best way to do this is to look at the figures

• Determine what percentage of a turn's worth of damage the player mitigates by choosing "defend". Take care to account properly: for example, if "defend" only reduces the damage that specific player takes, then choosing that action only has any effect on those turns when that player gets attacked.


• Estimate the entire party's average rate of damage per turn, and compare that to the amount of damage the player can do by choosing "attack". This should let you measure, in turns, how much faster combat will end by making that choice.

Note that to get the effect you want to achieve, you probably need the average damage per turn your "burster" class does to be rather low.

This means that you will have to design encounters so that the timing of damage is a valuable thing. For example, if an encounter has three identical enemies, damage done near the beginning of a fight is three times more valuable than damage done near the end of a fight — the former reduces the amount of time you spend with all three enemies damaging you, whereas the latter only reduces the amount of time you spend with a single enemy damaging you.

Fundamentally, the options are to make the undesired player behavior less attractive, to make desired alternatives more attractive, or some combination of the two.

In terms of implementation, it might be worth considering non-linear solutions. You've already identified some disincentives, but I noticed that they all happen to be linear. For instance, limiting an ability to once every X time units. An example of a non-linear approach would be to use a limit of X+N where N is the number of times used thus far. Conceptually, you would apply this to something where you find yourself thinking "a little is good, some is fine, but increasingly less so". In terms of theme, this maps on to the idea of diminishing returns.

You can also include more complex formulas. For instance, instead of a strictly increasing value for N, you could include a formula allowing it to gradually ease back over time. Or you could make it more aggressive, 1.5*N, 3*N, N^2, etc.

While this can give you extra flexibility to your design, there are some trade-offs to consider:

• it creates more parameters to balance


• it can create more obvious 'sweet spots' leading to more average play strategies
  
  
  
  
  • not necessarily bad, but you need to consider if it detracts from the experience
  
  
  
  

Non-linearity can also be applied to incentives. For instance, one of the Ascension deck builder expansions has a enemy with a reward of X+N where N is the number of times this enemy has been defeated so far. Conceptually, you would apply this to something where you find yourself thinking "a little is okay, more is better & increasingly so". In terms of theme, this maps onto the idea of compounded returns, reaping rewards for early investment.

Again, you can use more complex formulas. A common variant is to include a cap, for instance a reward of X+min(N,C) where N is the number of times, C is the cap and the min function gives you the smaller of the two.

As before, there are some trade-offs:

• it creates more parameters to balance


• it can create run away leader (aka snowball) effects leading to more extreme, all-in play strategies
  
  
  
  
  • not necessarily bad, but you need to consider how it impacts the design
  
  
  
  

A potential solution could have the burst damage be enabled by other skills, such as debuffs, self buffs, and the like. In MMOs this is called a rotation - it's been awhile, but IIRC WoW has a good example with the fire warlock, who has a spell that does a ton of damage, but with limited CDs and a bunch of pre-requisites for getting the most out of the spell.

How about making the abilities recharge from enemy kills? If there's a boss every, say, 10 enemies, and each kill recharges 10% of the power needed, the optimal strategy is, indeed, to use your other abilities to take out the normal enemies, then fire the big guns at the boss.

Path of Exile uses this structure for both flasks (which instantly recharge in town) and Vaal skills (which only recharge in battle).

If you're dead-set on having this be time/turn based, then you need a mechanism in place that punishes taking a long time. For example, enemy monsters can have the same mechanics; if you take too long killing them, they start unleashing dangerous moves. Or reward taking a short time; you get bonus xp or resources if you can quickly kill the enemies.