Welcome to the Forum Archive!

Years of conversation fill a ton of digital pages, and we've kept all of it accessible to browse or copy over. Whether you're looking for reveal articles for older champions, or the first time that Rammus rolled into an "OK" thread, or anything in between, you can find it here. When you're finished, check out the boards to join in the latest League of Legends discussions.

GO TO BOARDS


Banning for a Feature in your own Program

123
Comment below rating threshold, click here to show it.

dissonancy

Senior Member

09-12-2010

It's intended to be used as a bypass for when your launcher or patcher messes up, NOT for trying to log in while the servers are intended to be down and mess up their maintenance.


Comment below rating threshold, click here to show it.

Beartato

Recruiter

09-12-2010

Quote:
YodaGoneMad:
We REALLY need a red response on this, was it just a fluke for a few people? An accident? I can't imagine them banning accounts, especially paying accounts, because they used a well-known code that was originally posted on these very forums by Riot themselves.

If they don't want people doing it then a warning would be good, but a ban?


Because paying makes you safe from bans.

Riot, specifically Phreak said that people should not use the code when the servers were down/busy, you're just giving them more problems. It was used back in beta for some reason, but now, people are just abusing it and giving Riot a harder time.


Comment below rating threshold, click here to show it.

Ausum

Senior Member

09-12-2010

Does a player that's brand new to the game know about the code? It's not a "feature" of the game, as you put it. Do you honestly think they would bother to set the servers to "Busy" if they didn't care whether or not people were connecting at will? Get a clue, ****.


Comment below rating threshold, click here to show it.

Renrut

Senior Member

09-12-2010

I agree with xbombr, rather than having to get past the patcher they could go the way of almost all mmos and just set a server cap and put in a wait to get in queue during busy server status times if they want to keep it fair.


Comment below rating threshold, click here to show it.

Zenue

Member

09-12-2010

It's not bannable to use it as far as I know, but to share it is.
Riot have stated that they will soon remove it anyway.


Comment below rating threshold, click here to show it.

WantedOne

Senior Member

09-12-2010

Quote:
dissonancy:
It's intended to be used as a bypass for when your launcher or patcher messes up, NOT for trying to log in while the servers are intended to be down and mess up their maintenance.


well, that pretty much explains my post and my reasons for using the code


Comment below rating threshold, click here to show it.

Night4ngel

Senior Member

09-12-2010

Quote:
WantedOne:
When i play, i see sometimes see "busy" or "offline", mainly the "offline" message, even though they said that the servers are online. And it stayed that way for about 2 hours in the "offline" state until i was informed of the code, in which case, i use it, and my problem of a delayed launcher is fixed. If they are honestly banning people for using it, i find that kind of...dumb.


You need to refresh the page after the patcher. hit options then save settings


Comment below rating threshold, click here to show it.

Patronum

Senior Member

09-12-2010

Quote:
johnnyt305:
This isn't an MMO


Massively Multi-player Online.
You are messing MMO games with MMORPG games.


Comment below rating threshold, click here to show it.

WantedOne

Senior Member

09-12-2010

Quote:
Night4ngel:
You need to refresh the page after the patcher. hit options then save settings



ill keep that in mind, thanks


Comment below rating threshold, click here to show it.

Da Orkz

Senior Member

09-12-2010

They are banning people not because of the way they are using the "feature", but when. Attempting to log in during a maintinence can mess up the system, increasing server downtime and basically making everyone more upset.
So don't do it during downtime.


123