![]() |
09-06-2015
|
273 |
Enguard & Alumni
Join Date: Sep 2011
Posts: 5,773
|
The server is what verifies hit detection and if the server said that someone won then they won, arguing against that is kind of like arguing against a calculator on a math problem... This is just not true, I've been in tons of spars where a player hits the other a frame before and they get the win because spars do not immediately end when the last hit is landed There's a frame delay before the spar ends, which is obvious when you consider that you can see several frames of the death gani, that allows for both players to be hit in a certain time frame, but one of them will clearly land the hit first There are situations where both players hit each other on the same frame but this isn't one of them |
09-06-2015
|
274 | ||
Registered User
Join Date: May 2013
Posts: 3,027
|
And you would need to see who delays more. If kouji delays less than domi, and swung first, then domi clearly got the hit due to delay. But, if kouji delays more, and swung last, then he won only, because of delay. The server could have taken it's sweet time to register domi's hit on kouji, thus kouji dying last, and responds with Rebellious winning. You'll have to see who delays more, and who hit first. Like I said tho, if both players die, it should be a tie.
There are a lot of matches that have been lost in singles by what should have been a tie hit, due to the winning player having more delay. Now, what I want to know is. How come the match viewers are laggy? Is it some sort of stream, making it all warpy, or is it because there are a lot of players around in the same level? |
||
09-06-2015
|
276 | |
Registered User
Join Date: May 2013
Posts: 3,027
|
People saying, "oh, but not when we did gst in xxxx, xxxx team didn't get dq!" True, but I think the hosts are still learning and are trying to change that. I'm sure next gst, there will be less issues. Maybe stricter rules. |
|
09-06-2015
|
277 | |
God
Join Date: Aug 2014
Location: my house
Posts: 132
|
I am not trying to take any side, but I support the admin trying to make the finals fair by giving Rebellious and VIS a final match to make things clear. If he/she declared Rebellious as winner, then this thread would probably be other way around, VIS arguing that it should have been a tie. He/she just tried to avoid argument like this(would of worked if Rebellious won the 7th match, but plan failed). |
|
09-06-2015
|
278 |
Registered User
Join Date: Sep 2011
Location: Puerto Rico
Posts: 108
|
Except it wasn't a tie?? Because I hit first If I delayed it would have shown domi hit before me in the video, this is not the case, because the video shows I hit first, and it doesn't even show him using his sword because he used it later than I did. There shouldn't have been a redo because there was already a winner. After my amazing performance and watching the pop-up say "You have won the spar!" I thought it was over. |
09-06-2015
|
279 |
Temp. Retired Player
Join Date: Sep 2012
Location: Philippines
Posts: 194
|
this shouldnt be a surprise for some people but Im sure you guys have faced delayers and always have those moments where you are both at .5 and you swing you sword first then following delayer strikes back after you hit them and its considered tie instead of a win for you but the situation we are discussing about is when player 1 hit first and killed player 2 and then approximately nearly a second after player 1 died because of a martyrdom trick of player 2. This is from what I saw, I thought it was a tie too until rebellious said that the system declared them winner. It was really a close match but If the system says they won then they did, but if it was really a tie then the system would have said otherwise but this time it didnt
Last edited by KuyaGabeGraal; 09-06-2015 at 11:23 PM.
|
09-06-2015
|
280 |
Çòñtëgó Me§§iaH
Join Date: Apr 2015
Posts: 175
|
Let's not take away from VIS's win. It's over and everyone did a good job, banned players or not, gg. Was fun. The better team should always win delay or not. Don't try to trade hit for hit with a someone who delays and you're both .5. It's simple really and it's always been the case with delay. Nothing new. GG all teams and congratulations to VIS and Deity on a clean win. |
09-06-2015
|
281 |
helo utub
Join Date: Feb 2012
Posts: 1,225
|
Message said we won, not sure why people are trying to argue that. Comyt mentioned this happening to him in the past and his team stayed the winner. That's not consistent and it's admins making up rules as we go. Again with the banned players, you can't allow some teams to use them and disqualify others for doing the same, that's not fair. Anyways, no idea why some of you are trying to make an argument out of this when Rebellious won that round, as the message said. You'd all be annoyed if this happened to your guild. For those who say ViS would be annoyed if they counted our win as a win, let's think about that. It said we won, therefore ViS has no argument. ViS never won, so we aren't taking away anything from them @Contego. Rebellious is the one who had their win taken. Not sure how you and others find it impossible for an admin to be wrong. Grats to reb for winning back to back Gsts!
Last edited by GotenGraal; 09-07-2015 at 12:00 AM.
|
09-06-2015
|
282 |
Emperor
Join Date: Sep 2011
Location: New York
Posts: 1,000
|
alright so comyt (4 gst wins, at least 4 second place finishes, ~60k spar wins) and thallen (however many gst wins, 40k spar wins) vs aguzo (who even knows how many spar wins this clown has, all of his gst wins from being carried by alumni, graalbuster). who are we going to listen to here lol rebellious won system's decision should be final decision |
09-06-2015
|
283 | |
Victor
Join Date: Apr 2015
Location: Guam
Posts: 728
|
|
|
09-06-2015
|
284 |
Registered User
Join Date: Sep 2013
Posts: 61
|
Here you have Domi, a player well known for delay vs Kouji a US legend who has never been known for being a delayer in his time of graal lol. Kouji hit first and took down Domi. Rebellious Winner GG
Last edited by juan23; 09-06-2015 at 11:52 PM.
Reason: don't ddos me br0
|