Kalista and Jarvan IV disabled?

Junkο·Dec 10, 2014·2 votes·3,766 views

Why were they? Can we at least get an explanation? Also why both and not just one of them? And how did Riot break something that wasn't broken AGAIN?

26 Comments

FunceDec 11, 20144 votes

Sewn Chaos Orianna: When she's idle her ball is invisible.

Kalista: Bug w/ her ultimate, it allowed champions with a free rank in R (jayce, etc) to gain additional points.

Jarvan IV: Bug where his ultimate is dealing too much damage

AtijafDec 10, 20143 votes

In programming, breaking things that weren't broken before is easy. Everything has to work together perfectly and when having to deal with many champions, an error is bound to happen.

JunkοDec 10, 20141 votes

The problem is, they didn't even change anything about Kalista this patch. I would understand if they fucked up something with the Jarvan change, but why Kalista?

Also in programming you will only break things that are connected to what you are changing. Idk how Jarvan ult and Kalista are connected at all. Granted some Rioters said that the coding of the game is shit but still...

The Storm DragonDec 10, 20144 votes

The problem is, they didn't even change anything about Kalista this patch. I would understand if they fucked up something with the Jarvan change, but why Kalista?

Also in programming you will only break things that are connected to what you are changing. Idk how Jarvan ult and Kalista are connected at all. Granted some Rioters said that the coding of the game is shit but still...

Doesn't matter if they changed Kalista or not. In coding, everything is interconnected. You could change some UI element and end up making Rammus ult permanently go on cooldown if it hits a turret. That's just the nature of programming.

JunkοDec 10, 20142 votes

Lol no it's not. Unless you rewrite the entire code from scratch that will not happen. Any decent programmer will have organized code, they are even encouraged to do so.

Bears Dont CareDec 10, 20144 votes

Lol no it's not. Unless you rewrite the entire code from scratch that will not happen. Any decent programmer will have organized code, they are even encouraged to do so.

Keep in mind,you are assuming that thecode is properly organized with League. It was never intended to be as big as it is and so I bet the coding is very poor and when one change occurs, everything breaks.

Maybe one day they'll fix it but that would mean a new game essentially.

JunkοDec 10, 20141 votes

If it isn't organized, it really should be because every single patch recently has had game breaking bugs happen.

vscAlohaDec 11, 20141 votes

Essentially a new game would be required for this.

Sailor MintDec 10, 20141 votes

If it's not broken, don't fix it.

If the code works, there's no reason to touch it until you have to. The old code will naturally get replaced as kits get reworked.

Bears Dont CareDec 10, 20143 votes

If it's not broken, don't fix it.

If the code works, there's no reason to touch it until you have to. The old code will naturally get replaced as kits get reworked.

No...that really isn't how it works because the issues lie at the most base level of the game. Its an issue that cannot get fixed over time, its one that remains because it is a part of the engine. You would need an all new engine and completely new base coding. Essentially a new game.

Sailor MintDec 10, 20141 votes

If you can do everything you want to do with the current engine and there's still room for adding new features, does it even matter?

Why would a new engine, that would come with its own set of problems, be the panacea to all of that is wrong in League of Legends?

Rewrites become a necessity if the current engine gets in the way of design. With the recent releases, I'm not convinced we've reached that point yet.

LordSquirrelDec 10, 20142 votes

Devi Freak Mint, you are wront and Annoth84 is right. Do you understand how programming works especially if the program is written very very poorly? Because I sure do and it seems Annoth84 knows as well. I am a computer science major and I program every day. Lets make an example. Lets say we have many, many if statements, and everything is working fine, but then a new patch comes out and those current if statements don't quit work for the new patch. Maybe you need to add another if statement to catch an error or maybe they need to add a new try and catch block to catch exceptions to prevent further errors. There are many reasons it could go wrong.

Sailor MintDec 10, 20142 votes

Since you obviously don't code.

It's completely possible to have bugs go undetected for years because they require extremely specific scenarios to trigger, scenarios that may not even exist in the current version of the game. That is, until someone makes changes somewhere and the bug becomes a common occurrence.

Like you know, Azir's soldiers killing Jayce's Acceleration Gate.

JunkοDec 10, 20142 votes

I am learning to code. And here we are taught to organize and stress test everything major. Granted LoL is 4-5 years old so the code could be messy from way back then.

Also there is a difference between a bug being undetected and Riot ignoring it. Azir was bugged to hell on PBE and got shipped live with all the bugs despite the PBE community reporting them. Same happened to Smite being able to kill Trynd/Kayle/Zilean/GA

KriptonisAzullisDec 11, 20141 votes

You are basically arguing that changing how addition works would have no effect on anything else in math. Even if you are a complete layman in terms of code, how can you not see that every champion interacts with everything else in the game? How can, for example, Kalista's ult interact with a Jarvan that just used his ult, if there is not specific code that deals with that exact interaction? What, the program just guesses what will happen?

Blood HoneyDec 11, 20142 votes

[{quoted}](name=Rainbowe Dash,realm=EUNE,application-id=3ErqAdtq,discussion-id=eOVNMev9,comment-id=0002000000000000,timestamp=2014-12-10T19:57:11.357+0000) Lol no it's not. Unless you rewrite the entire code from scratch that will not happen. Any decent programmer will have organized code, they are even encouraged to do so.

Then I'm afraid you're not really sure how League is coded, or even how coding works. Gnarly is correct in saying that the coding for the game is all interconnected and any change can effect how a code interacts with the other. Kalista is especially one of those kinds of champions especially since her passive.. I don't know.. needs to have an effect on any champion she uses it on.

vscAlohaDec 11, 20141 votes

Please stop pretending to know how to code. You've done this before and everyone has replied to you in the same manner, and you continue? Cease and Desist.

ANXUEXIAOLUOLIDec 11, 20141 votes

I'm learning game making right now, and I know one line of bad code can break the entire game.

Katunga JonesDec 10, 20142 votes

JarvanIV & Kalista are expecting to have a baby. summoner 31

That's right Poro King is their love child. summoner 30

SmokingPuffinDec 11, 20142 votes

ITT - People who have no idea what working on a mature codebase is like discuss how easy it is.

Oliver The FiendDec 10, 20141 votes

I was wondering why they were disabled myself.

ModWulf HelhammerDec 10, 20141 votes

They did change something on Jarvan (and indirectly Kalista) with the new patch, and Kalista is brand new, so something obviously went wrong with the code on the new patch

Meep ManDec 10, 20141 votes

Well, lets look at potential causes... they did fix a Jarvan bug. Maybe it broke the game somehow. Maybe his ultimate was dealing double damage or something.

As far as Kalista... Im not sure.

JunkοDec 10, 20141 votes

It's possible there was a huge bug, but from my time spamming her with a friend i haven't really seen anything game breaking. I wish we at least got a word from Riot.

CenturosDec 10, 20141 votes

If the code for League is anything like the code for PoxNora... They fixed a bug somewhere, and everything else broke.

Kuroi86Dec 10, 20141 votes

Possibly code error having to do with some connection between the two? It sucks how easy it is for something to go wrong when coding. Friggen make the code perfect only to have it not work and you've got to go in and redo the whole thing.