|
by trancez, Level 33
Last updated at February 27, 2008, 9:43 pm
|
I'm not here to defend SK-Gaming's Arena Team, but merely state the facts that happend.
During this period of time the lag spike happend, Cox Cable(An internet service in Orange County) had spiked throughout the whole region. I also was in my own arena practicing 5s and azure/agnos were complaining about lag spikes, and coincidentally Azurewrath/Agnos(They're roommates) live in the same arena as Mykke (Orange County, CA). Right after this was said, SK msged me about the lag spike rule. I should have dealt with this in a more timely fashion but I was busy practicing 5s in arena, talking to NWMF to setup the match, explain the WoW registry lag fix to azure/agnos, and talk to SK at the same time. Later on, Affix also confirmed a lag spike and he also uses Cox Cable Internet.
According to the ruleset (http://www.battlegroup9.com/bg9tourneyruleset.doc), #14.
In case of an instance server crash, severe lag conditions,
or game-altering disconnect, teams may replay their match. If conditions are
too severe during the scheduled match time for 1 hour or more, the match maybe
rescheduled for a more suitable time.
While my judgement at the time was based off forcing my own team to replay because of a game-altering disconnect, asking them to replay the match shouldn't have been as much of an ordeal as Veex's made it. (I made the rule based off the WSVG rule that any lag spike/disconnect forced an automatic replay regardless, the difference though is there was an admin watching you play the whole time.)
I don't believe it's fair to change the ruleset mid-tournament while another team in previous rounds were effected by it. The difference between this incident and the fnatic/CLC one was that 10 people were listening to CLC play on BG9 vent saying they heard it happen, which isn't also a valid reason but just enough I guess.
The fraps from the match, starting about half-way through, is here from Neilyo's PoV: http://www.battlegroup9.com/skvsTSG.wmv
From the fraps about the incident, and here's the facts on it:
- Edit, there's some confusion because Veex's pet and TSG's paladin have the same name in the video.
- 53 seconds into it is when Mykke(SK's Priest) get's spell locked, he still has the pet targetted during this.
- For about 5-6 seconds, he remains with the paladin/warlock pet targetted. At about 22%, he targets himself and trinkets but dies shortly thereafter.
- Pronne(SK's Druid) does not attempt to heal Mykke until he's at about 22% as well, so it seems unlikely he would have lived though it could have been possible if Mykke had given himself a few more seconds to live and give pronne a chance to heal. Also note that Pronne has a full innervate and is the most mana'd at this time as well.Whether the lagspike effected Mykke's death is still questionable, the arguement is very valid still.
Edit: I don't want to spoil people's amusement since the above content is invalid, the match stands 2-0 and the round won't be replayed.
Though I write for the website, I do this out of volunteer work mainly. The only reason I started writing for SK was to get this tournament sponsored by a high profile sponsor. If there's someone else out there that could run this full-time and help me out, I would gladly accept the help because I really had no one volunteer to help. My team(fnatic) was extremely frustrated that I chose the tournament's issues over the team's, which doesn't make well for good chemistry which is another reason I think we played poorly in the matches vs CLC.
If there is a next tournament, of course there will be a ruleset based
off no admin judgement needed at all with maybe small exceptions and an
invite system based off Ladder Ratings similar to what the BG3/Cyclone
admin team uses. I will either play without administrating or only administrate as well, being that it does conflict with opposing team's agendas.

edit: for
- Veex's claimed Mykke(SK's Priest) was spell-locked while trying
to Smite his fel-hunter pet, this is untrue because in the video he has
TSG's paladin targetted at this time.
- 53 seconds into it is when Mykke(SK's Priest) get's spell locked, he still has the paladin targetted during this.
for this point, does Neilyo have a casting bar on the priest to prove he wasn't smiting something, and was he ever targeting the pet prior to the pally?
Smite his fel-hunter pet, this is untrue because in the video he has
TSG's paladin targetted at this time.
I'd love to be able to watch that video, because I'm not sure what nonsense you're talking. Also, you do realize people play off focus frames and proximo, right? Ever see a shaman load up a chain lightning with no target? Doesn't mean he's about to cast it into empty space, because TOT means little to nothing. I'll be able to answer more when I can watch the video.
Maybe the pally having the same name as the pet has something to do with this?
Maybe I'm just sounding stupid.
Does that mean replayed or 2-0??
or game-altering disconnect, teams may replay their match. If conditions are
too severe during the scheduled match time for 1 hour or more, the match maybe
rescheduled for a more suitable time.
Is a four second spike really severe lag conditions? I understand your position Trance but if it had happened at a 'less crucial moment' would the match still be ruled a 'replay'. I helped write the WSVG rules and I can tell you from my limited experience with rule creation that you absolutely cannot apply the same rule differently depending on the situation. Wording like "game-altering" disconnect is also bad because really that is open to all sorts of interpretation and will only cause more drama like what you're seeing from this.
My advice is that you state things clearly and deliberately. For instance: Any player who disconnects prior to the gates opening will result in an immediate 'replay'. If a player disconnects mid-fight they may petition their opponent for a replay but will otherwise have to accept the round's outcome.
Thats just **** I came up with off the top of my head. The biggest reason you have to make somewhat 'bummer' rules like that is because some players are not exactly the best sports and what happens if a competitor is OOM and running around watching his team lose and realizes pulling the plug will give him another shot at winning? I know that sounds really bad but you and I both know that some people will do anything to win.
you are amazingly dense if you are letting some other lag reports, sometime the same evening, somewhere in CA, actually influence your thinking about this case. there is no way to connect that to the specific claim of the priest's lag spike.
everyone in that match was playing fine... the priest was casting spells and stuff... then in a 7 sec timeframe he gets spell-locked, focus-fired and executed to death, while receiving zero heals. Turns out that just in those 4 sec he was lagging, not before, not after, not anyone else.
NOW. is that "instance server crash, severe lag conditions,
or game-altering disconnect"... or NOT?
because anyone at any time, 30 min after the match ends, can claim a lag spike during a decisive moment. You claiming that this invisible 4 sec, JUST as he dies, is "severe lag conditions" cause you got whispers about some other lag supposedly someplace else on west coast, is laughable.
But... Trance thinks that the priest has TSG's paladin targetted from the movie, when he actually has the pet targetted.
Edit: Ah, I see what you mean.. you commented on that above in a reply. 5 minutes late, yup. :P
Touche' sucka!
I'm talking about this comment from you: "By late, I mean I posted this like 6 posts up =]"
But, I had already made this edit 2 minutes earlier: "Edit: Ah, I see what you mean.. you commented on that above in a reply. 5 minutes late, yup. :P"
It's not us, it's this sucky ass psuedo-forum code they use here.
Ok that is just ******* hilarious that right there is.
One guy experiencing a 4 second lag spike is not severe. Can it effect the outcome of the game? Yeah, but isn't there a reason you do best out of 5 games to begin with?
This is just common sense.
and the guy in charge going on about who was targeting whom like some sherlock holmes (when the priest himself describes in great detail in irc that he was trying to smite the pet when he got gibbed)...
poor veex and co. are doomed.


Your Comment is being posted. Please wait...