• 0 Posts
  • 33 Comments
Joined 1 year ago
cake
Cake day: July 11th, 2023

help-circle

  • I think we don’t actually disagree and I was just not precise enough in my original post.

    What I described above applies to abilities that are relevant in combat and any other type of encounter that the respective system mechanically treats as a conflict similar to combat. That absolutely does not mean other abilities should not exist, just that they should not be practically usable during an ongoing combat-like short term conflict.

    Also: Abilities that are useful in short term combat-like conflicts and abilities that are not should not compete for mechanical resources of any kind, that is never fun.






  • Most abilities should be either “per round/turn” or “per encounter”.

    Abilities that are too powerful for that should either not exist or require significant preparation (enough for the opposition to have a chance to discover and interrupt it).

    Abilities that fall in the second category should automatically come with a less powerful variant in the first category.

    Maybe as a middle ground some player abilities could use the “roll for recharge” mechanic from powerful monster abilities.







  • I agree with the general sentiment that there are limits to what should be possible even with the rule of cool.

    In this specific case we don’t even need to go into the territory of undefined stuff that the DM decides on the fly, the rules as written already explicitly say “You create up to 10 gallons of clean water within range in an open container.”






  • Nowhere in that text does it say “managers are the real software architects”. What it does say is “what managers do affects software architecture”. Sure you can extrapolate that to delusions of grandeur, but if you take into account the explicit call for collaboration it is much more likely what was meant is more along the lines of “we can mess things up if we ignore the architecture, so let’s talk to the real software architects before making org decisions”.

    About the comic: That one does have the line “management designs software architecture”, much closer to the negative interpretation; but that too can be interpreted in a more positive way as “… and we are not good at that, so let’s make sure to bring in the people who are good at it at important points”.