Imagine If

Please don’t perverse the word “science” to try to hide the abrasive way you approach discussions. The main problem is that you think your perspective is right and everyone is wrong, and you become abrasive, people starts blocking you, and the discussion stops. And by that time, you haven’t even made your point clear.

If you think my suggestions will make the DK too simple, suggest other ways to make it more engaging. If you think the damage of Obliterate cleave would be too high, suggest ways to tone that down while removing the clunky and jarring need for DnD. Don’t say, “Oh, you just want to play a Paladin.”, or “If it is that easy, a bot can play for you.”

Here is a story:

The way you approach discussions reminds me a lot of a stubborn and obnoxious engineer that I worked with. Support team, marketing, and sales all urged the engineer to change the UI because the UI was pretty much a large grid representation of the database. It is clunky and users cannot use it. Multiple releases later, the engineer still did not change the design because he felt the large grid is perfect since it is how the database is designed, and all the users are wrong and they just need to adjust to the UI. He was laid off.

As a Tech COO, I can tell you that the best and most successful people I’ve worked with are the ones who considers and takes in other perspectives, and improves their knowledge and their work.

Next post, approach the discussion with that in mind. Simply tell me, what you think is the problem with making Cleaving Strikes that trigger off of, say, Festering Scythe. Is it too much damage? Too fast of a ramp? No one knows what your main contention is because you put too much abrasive non-sense in your posts.

3 Likes