Kalista, Bane of Supports (Complaint)

Righteous Savant·11/21/2014, 6:39:05 PM·1 votes·477 views

As a dedicated support player, the newest addition to the roster is proving troublesome. There are three key points that I believe need to be fixed with Kalista. I say "fixed" because these are indeed problems that need to be solved. If anyone disagrees, then that's your choice. For me, after the first evening playing with Kalista players, I am ready to dodge games when seeing her selected. I never dodge games or did I even think I would want to. Let's get to the list.

Problem #1: Relic Shield currently cannot work well with Kalista. Since Kalista has an ability that can allow their partners to kill minions and give her the credit, the Spoils of War Passive does not click here. Yes, you could tell your Kalista not to hit the Cannon Minions, but honestly, "get along better" is never a solution. It's an ideal, and I've gone on record never to run a business with them as policies.

Solution?: This one is easy. Since the Spoils of War Passive has been adjusted in the past, such as for Zyra's sprouts, it needs to be adjusted here as well for when being that if a support with Relic Shield gets the kill Oathsworn to Kalista, the Spoils of War exhausts a charge.

Problem #2: Anyone can be Oathsworn against their will. I'm sorry, but forcing a player to have an ability that they don't want? Where is that fun?

Solution?: I believe it is an easy one, but the developers and the community don't seem to be in sync on this. I know this has been discussed before, but even the official description says the following about the Black Spear's Active Ability:

*Kalista offers a pact to an allied champion, should they agree, the item is consumed and the pair are Soul-Bound for the remainder of the game. When accepted, the binding enables Soul-Marked, a passive on Sentinel, and allows Kalista to use Fate’s Call when she unlocks it. *

So, where exactly did anyone agree? It's forced, not voluntary. This mechanic needs a revist, for players who do not wish to have Oathsworn forced upon them. Also, to any players who don't think this is a problem, then you haven't found it out for yourself yet. Also, read on.

Problem #3: Oathsworn can be used against players, not just your opponents. I will give a horrible yet poignant example. Last evening, I was in a game as a support Blitzcrank. My Kalista partner recalled due to low health, but I was fine and kept pushing. I came into a one-on-one with an opposing Alistar. After a few moments, I had the advantage. Right when I was getting ready to finish Alistar off with his remaining 100HP, Kalista had reappeared and used the Fate's Call, pulling me away from Alistar. Afterward, she dashed over and killed Alistar. Yes, this was a clear kill steal, and Kalista found I refused to lane with her further.

Solution?: This goes again upon Oathsworn's imposition against players. You are essentially having strings attached to you. I can accept when an opponent has forced crowd control upon me, but a teammate? No.

The solution here is simple again: Oathsworn needs to be reworked. Habits like this will happen, and as a dedicated support, I have my own personal rules to play. One of them is when a teammate decides they are more important than the team or their partner, I can no longer support them.

Personally, it has reached the point that when I see Kalista is selected, I have to accept the following:

  1. I cannot use any of my tank supports, as Relic Shield is out.
  2. I have no voice in being Oathsworn or not.
  3. Kalista can become my ventriloquist, and I really don't appreciate where her hand is.
  4. Queue dodging is becoming a rising urge that I must fight committing.

If this is not remedied and soon, then my desire to be a support is hindered. It is often not fun to play with Kalista as a support for me. I know that I am not alone in this. Just so we are clear, Riot, when a game's fun factor lowers or disappears, guess where the players' time and dollars go? Hint: Not to you.

Get these fixed. You don't need more of a message than this.

0 Comments