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.
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
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
if (Easepacketdeaths = 1) {
Easedeaths = Easedeaths + Easepacketdeaths // Add death
if (Easedeaths == 10) {
Print "Ease is out." + Easekills + "wins" + Easedeaths + "losses"
}
}
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
if (Easepacketdeaths = 1) {
Easedeaths = Easedeaths + Easepacketdeaths // Add death
if (Easedeaths == 10) {
Print "Ease is out." + Easekills + "wins" + Easedeaths + "losses"
}
}
End of story. Any further questions please cry to someone who understands concept of programming and how lag works.
Comment