Sunspear's skill set is weird

Platform, device version and operating system:

Windows 11

Screenshot or image:

What you were expecting to happen, and what actually happened:
I am stuffing my heroes up to L100, and processed to Sunspear. And see that thing above.

  • He has Heatwave talent which starts Firestorm at the start of each turn.
  • And he have to choose between Nature’s Aura which uselessly create Leafstorm at the start of any battle, only to be immediately replaced with Firestorm - and Firestarter which allows you to create Firestorm and immediately replace it with Firestorm.

I think, something is wrong here. :slight_smile:

How often does this happen? When did it begin happening?
Always.

Steps to make it happen again
Look on traits/talents.

1 Like

This isn’t a bug. It’s lousy design, and it’s talent trees that are a poor fit and synergy with the class traits. But it’s working as intended, even if the intentions stink.

2 Likes

Maybe I am slightly differently treat the term “intended”, but If something doesn’t work and cannot work, I would not name it “work as intended”.

How long have we been suggesting a class rework? 5 years? It will be a cold day in Hell before that ever happens.:rofl:

They’re probably never going to revamp classes, which is such a shame. People level up classes, never to use them again, and then question why most of the traits and talents are completely useless. I tried advocating that Warden should have its final trait changed to: “Create a leaf storm when my turn begins” because Banishment and Beetrix would be like peanut butter and jelly.

Elementalist overpowers everything and everybody is used to using it for rough match-ups. But Sunspear is my favorite class to use in PvP with Stellarix because the additional :red_circle: gems make it easier for that dragon to loop when Chrysantherax does not one shot opponents.

2 Likes

There is a cautionary tale here from history.

Years ago, people pointed out Sunspear’s storm creating talents were redundant due to its 3rd trait, hoping the devs would listen and change those talents.

This was never going to happen though, as talent trees are shared among classes, so couldn’t be changed only for Sunspear. Instead, to the great dismay of the player base, the devs changed the perpetual firestorm trait to a +2 red mana bonus instead.

At the time, Sunspear was the only way to get a perpetual red storm. Troops with perpetual dual storms including red like Magma Dragon and Gingeraxia didn’t yet exist. In those days before egg Dragons, Phoenicia was the most powerful AoE troop in the game, but only with a firestorm, so this change nerfed teams popular for doing dailies.

A “Make Sunspear great again” campaign was launched and the devs reverted the change after a few days, bringing back Sunspear’s signature trait.

Be careful what you wish for.

10 Likes

“Working as intended” is developer-speak for the issue not being an actual coding bug.

It’s Hanlon’s Razor. It’s not malice, but incompetence. It’s poor design from a pool of people who probably never play the product and therefore can’t acknowledge a rather simple issue.

3 Likes

Oh, I guessed the talent problem and totally considered 3rd trait change. :slight_smile: Only maybe not to feeble +2 red change, of course. :slight_smile:

It’s not always redundant. The talent gets triggered as your team gets processed, but can be overwritten by the opponent (or even one of your own troops if placed after your hero) if they have a talent with a storm.

The trait ensures that it turns back to a fire storm at the start of your turn (thereby overwriting an opponent’s alternative storm).

2 Likes

If one does x at start of battle and another does x at the start of your turn, then the one that is redundant is the “x at start of battle” one. It literally does nothing, because immediately after the start of battle, you take a turn.
Totally agree that the start of turn one is better, but when you have both, the start of battle one does nothing.