Bots don't "make mistakes"

[Capital Knockers]

waal of test

You obviously haven't been witness to many of my other posts! B)

[fLaReD]

omg i cant believe this is happening its all cuz of obama!!!

[kthx]

This guy is like a less intelligent version of Man Kitten. Someone silence him and his ignorant threads and posts.

[Money]

Didn't want to have to reply to this thread but the same five people are having the same discussion over and over again. Clearly some people need to learn how SUBBING WORKS.

Let's explain:

C 4:spikey> us
Ease has been substituted by Ardour, with 1 deaths left

At this point in time, the bot has recorded a substitute by Ease as the !sub command has been used. Looking at it from a programming perspective, the sub command is being called BEFORE it checks for a death. You idiots need to learn that code cannot be simultaneously read at the SAME TIME. It is technically IMPOSSIBLE for the bot to be checking for 10 deaths and applying a sub. The sub overrides and breaks the loop checking for 10 deaths in milliseconds to sub ease.

T saetep> yeah
Ease is out. 12 wins 10 losses
T ignite> whoa

How did Ease get 10 deaths if he was in spec then? On Ease's screen, due to his lag (probably 60ms) the sub has NOT occured yet. Therefore, his client is still sending packets to the bot. The bot has already completed the sub command and is now 1/100th of a millsecond going back into a loop and receieves a packet from Ease's client saying that he has DIED. Therefore, the bot finishes this loop and adds +1 to Ease's death even though he has already been subbed out. A separate function PRINTS this on the screen so everyone will cry. Contradictory to whatever you nerds are believing, the bot is STILL RECORDING statistics of players who are in spec. The method the bot is coded ensures that in order to prevent recording extra deaths, SPECS the player. Unfortunately due to the lag on Ease's screen, the bot printed out the 10 deaths when they ACTUALLY DID NOT OCCUR but ONLY OCCURED on Ease's screen. In REAL TIME, the bullet NEVER hit Ease.

Let me demonstrate with some simple pseudocoding for you nerds



So guys, where does the issue lie? The bot completes the loop and records Ease's death from the packet that Ease sends (because Ease has not been subbed on his screen DUE TO LAG) when in fact Ease is technically never in game. You people are retarded saying he can't die in spec. Technically he CAN.

End of story. Any further questions please cry to someone who understands concept of programming and how lag works.

holy nerd

[Exalt]

holy nerd

holy turd

[Ara]

I don't know how you can twist and turn this simple matter into what ever you
want it to be. Simply put, ship exploded, it died, what ever happened after that
was because of bad coding and wasn't supposed to happen. Appeal should've
been accepted, illegal sub shouldn't have taken place. What comes to lag, you
are talking of several clients lagging, that don't even fing matter. Ease's client
registered the hit, sent the "client dies" info to the server, he was dead.

[Creature]

I don't know how you can twist and turn this simple matter into what ever you
want it to be. Simply put, ship exploded, it died, what ever happened after that
was because of bad coding and wasn't supposed to happen. Appeal should've
been accepted, illegal sub shouldn't have taken place. What comes to lag, you
are talking of several clients lagging, that don't even fing matter. Ease's client
registered the hit, sent the "client dies" info to the server, he was dead.

The sentance should be:

"Simply put, the ship should never have exploded, it should have been in spec. what ever happened after that was because of bad coding and wasn't supposed to happen. Appeal should not have been accepted, because a legal sub was used. What comes to lag, you are talking of several clients lagging, that don't even fing matter. Ease's client registered the hit that should have NEVER happened because he already been subbed out, sent the "client dies" info to the server ILLEGALLY, so he should have been in spec with 9 deaths."

[Mattey]

If he had already been subbed out how did the client register the death? You're talking out of your ass. Thunder are some scared bitches and they should be.

The truth is NOBODY can determine what real time was because everyone lags on this game. The spectator with the least lag was THE BOT. THATS WEIRD THAT IT COUNTED HIS DEATH WHEN HE WAS ALREADY SPECCED RIGHT?

[Creature]

If he had already been subbed out how did the client register the death? You're talking out of your ass. Thunder are some scared bitches and they should be.

The truth is NOBODY can determine what real time was because everyone lags on this game. The spectator with the least lag was THE BOT. THATS WEIRD THAT IT COUNTED HIS DEATH WHEN HE WAS ALREADY SPECCED RIGHT?

Sigh Mattey, I JUST FUCKING EXPLAINED HOW THIS OCCURS DO YOU NOT READ MY POSTS.

Example code for the bot:

for (Easedeaths < 10) {

if (sub == true) { // The bot is checking if sub used
sub Ease out for Ardour // Sub Ease out
}

return Easepacketdeaths // Get packet from Ease's client count deaths (Ease is lagging, so he hasn't been subbed on his screen yet, and has JUST been hit by the bullet, so client returns an extra death INCORRECTLY)

if (Easepacketdeaths = 1) {
Easedeaths = Easedeaths + Easepacketdeaths // Add death (now Ease is at 10 deaths)
}

if (Easedeaths == 10) {
Print "Ease is out." + Easekills + "wins" + Easedeaths + "losses" // (prints out the statement with his deaths and kills)
}

}

The problem here is that EASE was SUBBED OUT BEFORE the bot checked his deaths. The reason why the sub still went through is because he was technically subbed before death was recorded. The bot runs the code one line at a time.

The simple solution would be move the if then statement checking for subs to the END of the for loop. Of course, I'm sure this has been fixed now that it's been blown into such a huge controversy.

[Mattey]

All's I'm saying is that ease got hit by the bullet on his screen and deserved that death. Am I wrong dude? Am I wrong?

[Capital Knockers]

All's I'm saying is that ease got hit by the bullet on his screen and deserved that death. Am I wrong dude? Am I wrong?

Who can say 'you're wrong' to that face? :P

[Kawrae]

Wow, what an epic failure.

Bots can't make mistakes like this. It doesn't matter what you saw, or Pure_Luck saw, or anyone else saw: it is literally impossible for the bot to make a mistake in thinking someone died when they didn't. The only way the bot counts a kill is when the player's client itself calculates..... BLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABL ABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLAB LABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLA BLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABL ABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLAB LABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLA BLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABL ABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLAB LABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLA BLABLABLABLABLABLABLABLABLABLA ....due to the built-in subbing.... delay,BLABLABLABLABLABLABLABLABLABLABLABLABLABLABL ABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLAB LABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLA BLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABL ABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLAB LABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLA BLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLABL ABLABLABLABLABLABLABLABLABLABLABLABLABLABLABLA ....ridiculous that this appeal was denied. BLA

Just like at school!

[tragiK]

why is this even up for debate? captains and assistants try to pull off this kind of sub all the time, except most of the time it's a desperation move that results in a 51-xx loss. it's much harder to pull off in twd cuz of the delay, but in twl/twdt there is no delay, you do the !sub command and it executes immediately.

clutch sub and it won them the game, gg.

[KiAN]

why the hell is this such a big deal? both squads will be in playoffs anyways.

this has, to my knowledge, never happened before. so when it happens again, you let me know, for all you nerds saying something must be done, some rule needs to be made.

[PaulOakenfold]

this has, to my knowledge, ever.

i feel ya