@Red Named Morons - You Going to Ignore Karma in 2017 (Fire Ricklessabandon)

Vanjie·12/20/2016, 7:20:42 AM·2 votes·1,024 views

Since he doesn't want to address the botched identity he ruined and only wants to give Karma a numbers buff for 4 years now, maybe it is about time you either fire the imbecile Ricklessabandon or make someone else in charge of her. It is close to a year year and Karma still has an incomplete visual update and thematic problems, a kit that is bland and not unique, a half worked on skin for Christmas, another numbers buff she received for an ability that functions like something else in the game, a nerf to the numbers buff he insisted on buffing when everyone told him not to, a complete lack of communication in regards to anything involving Karma. Remember, Riot Games think Karma mains are there most dedicated and passionate fans in this game . . . . yet they cannot be bothered to do a single thing on her. No Department at Riot Games can be bothered to, at least, fix and finish her incomplete visual update. Moronic Red Names that support a champion with no identity, a failed and half worked on visual update and thematic, and think they are communicating great with Karma mains . . . . because we are the most passionate players in the game.

Please fire Ricklessabandon for continuing to ignore the problems he created with Karma. Please fire this incompetent Developer that has yet to communicate with the community about her problems and what they need help with. Please fire this imbecile Developer that didn't care about Karma when he stripped her of everything the community loved on Karma, and replaced it with his own ideas so he can have an excuse to support it 4 years later. Fire the moron Ricklessabandon.

12 Comments

IxtaliKing12/20/2016, 9:33:21 AM7 votes

Wow... I know Rickless~~ messed up~~~~ with~~ ruined Karma, and has failed to really communicate with Karma's community, that's his bad (nobody's perfect). However, let's not call for anyone to be fired, that's just well over the top and mean. I 100% understand how mad you feel about the way Karma has been handled, many of us feel the same, but that doesn't mean we should go after people personally because of it.

He is human just like the rest of us and he at least believed when he was changing Karma that he was doing something good. In theory it looked good for the most part minus the removal of her shieldbomb, but it turned out to be a failure (as predicted by many). To be honest I'm more mad at the people who didn't even like/play Karma before who jumped on the idea of that update, only to then dump her again after the update landed and failed. I'm sad that we didn't have someone like SilverSquid to articulate the cons of that 5.10 update at the time, because if we did those changes probably wouldn't have made it to live. I'm also disappointed in myself for not having the confidence to voice my concerns at the time.

For now we're gonna have to take this "L", they can't leave Karma as she is forever - especially after her current pbe changes go live, they'll have to address her properly. Until then, try not to let the salt take over bro.

Deep Terror Nami12/20/2016, 7:23:58 AM4 votes

I disagree.

Breaku12/20/2016, 9:43:43 AM4 votes

Karma is in a great spot right now =D

vampirekid1312/20/2016, 9:49:44 AM1 votes

did karma get another update, or are we talking about the same update from years ago? because technically that update was successful.

karma now has a lot higher play and ban rate than she did before the update that "ruined" her.

a lot more people like her. looking at her 50% winrate and 10% playrate she is in a very good place right now. shouldnt touch anything on her.. also she needs the 5 people that played her before her update to stfu.

Vanjie12/21/2016, 4:34:28 AM1 votes

So guys I do not care. I am blaming this imbecile. He needs to be held accountable for his choices and the fact it's been 4 years and he has still not rectified his mistakes. Stop shoving your idiotic kit down our throats and make it more interesting or remove it.