Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

More Dev/Bob Cheating Revealed

Ashton692Ashton692 Member Posts: 138

I can't take credit for unearthing this, but in the spirit of showing people that there is more then the T20 incident I am going to post the details of a BOB cheat here.

Anyone in game remembers the whining that ASCN did when they got their buts handed to them during their war with BOB.  If you remember the initial days where ASCN invaded BOB space, you will remember that ASCN had 300 man fleets.  One of the problems ASCN had later in the war was that morale was so low.  They were never again able to get this number of people together.  The reason was they kept losing fleet battles.

ASCN claimed that BOB was crashing nodes.  They were made fun of.  I made fun of them admittedly.  They petitioned all this.  They claimed that when there was a GM in the system the nodes crashed less.  We scoffed.  But it seems ASCN was right.  Apparently CCP has since fixed this - this is no longer an exploit, so don't bother trying it. This is how BOB crashed the nodes.

Originally Posted by Firelord View Post

Yep you sit it at logon with the password filled in on the 2nd eve client.

Jump in system soon as "jumping" comes up click connect on your 2nd client, your first one will be bumped out and you will end up on the otherside, having bypassed the jump que, if the node was crashed by you and all your buddys doing the same thing. Your be the first in the que as the node comes back up.



This is how bob crash nodes, when I was in TPAR-C everyone logging out and back in 100+ fleet to clear the lag crashed the node. Those of us that where slow and were just logging back in as the node was dieing got in first. Of course behide the 20 odd bob that must have had there fingers on the button.

CCP claimed at the time that there was nothing BOB was doing.  I believed them.

So there are 2 things that bug me:

1) How is it that CCP, who has access to the log in times and can see plainly that out of the 400 people who log back in after a node crash, the 100 BOB members all get in first.  Doesn't this raise a red flag?  It was petitioned - CCP was told exactly what to look for in their logs.  Yet they found nothing?  Sure.  Whatever.

2) How did BOB know about this?  This isn't something that you would typically just stumble upon?  Although this is possible is this yet another example of a BOB member, who also happens to be on the bug hunting team, using information and passing it around?

One of the biggest problems that CCP is going to have (if they choose reform) is stopping the information flow.  If I am a DEV there is no log of me saying, "Hey, lets try this, oh look it worked!" on Team Speak.

I can't post this on the EVE-O forums.  If the newly appointed Eve Internal Affairs guy can answer this one - it is on a pile of other crap in this game.

Again, and remember - nothing is definitive.  This in itself hasn't cause me to think "hey, this game is run by the Devs" ... this is one of many my friends.  Because CCP is the judge, jury, and media in all these cases we will never have a definitive "smoking gun" -- so use a little reflective judgement.  If it looks like crap, smells like crap, and tastes like crap then don't frigin play this game.

Cheers.

 

Comments

  • TaramTaram Member CommonPosts: 1,700
    MMM gotta love unproven theories.  And asking CCP is allowed.  Submit a bug report and/or email kieron and ask for an update.



    My feeling:

    1) Ask

    2) See if you get an answer

    3) THEN decide if CCP is being honest or not



    But posting it here and stating you can't put it on the forums to get an answer is silly.  Ask, or you'll only be joining the other people who are making WAGs about the situation.

    image
    "A ship-of-war is the best ambassador." - Oliver Cromwell

  • Ashton692Ashton692 Member Posts: 138

    Whats a WAG? Whiners and G?

    Your post has inspired me to send an email.  I will do so.  There are some parts of this that are proven:

    - It was happening, It was petitioned, CCP came back and said there was no issue.

    My point to you is this - there will never be anything definitive.  It will always be unproven.  Players have no ability to prove anything so people that ask for proof from players are always going to "win." ... CCP controls all proof.  So as players the only recourse we have is to collect and trade enough of these stories, and once enough are in your pocket begin to suspect.  Once even more are in your pocket take action.

  • kovahkovah Member UncommonPosts: 692
    WAG



    "1. In colloquial Internet shorthand, WAG stands for "wild-assed guess". "
  • NicoliNicoli Member Posts: 1,312
    personnally I do not see a lets do this to crash a node but a, Have this ready incase we crash the node as we move to engage. As you said this was a time where 100+ session changes in a unbalanced node could crash the node. I've used the method above back when I was fighting with fountain alliance just in case the server got down we would be set log back in as quickly as possible. though i was not in a position where the node crashes would happen at the time of the ques but during POS seige's like the one last night I had a second client prepped to log in just in case I crashed.



    Now on ASCN part, I hope they would have wished just as well to win the battle through skill not because they got to rip the enemy fleet to shreads as it slowly came through the gate.
  • Ashton692Ashton692 Member Posts: 138

    Read it again mate.  I know what your saying - having a second client on standby - I have often done that.  This isn't what is being described through.  In this case the player is jumping, and then before the crash he is alt-tabbing out and logging in with his backup client.

    Doing this "bypasses the jump queue" which all other players are forced to wait through.

  • bawldybawldy Member Posts: 151
    I knew of this, and ascn and bob were attempting to do the same thing, not TO cause a crash, only if a node did crash.



    I judge this as "NOT AN EXPLOIT OR CHEAT"



    Now if a dev was on a ts type com system, and gave a heads up of a node crashing, then that is back to ccp giving their buddies an advantage...but that is speculation only, and I doubt it happened.

    ccp the "we cheat for our buddies and are proud of it" company...

  • NicoliNicoli Member Posts: 1,312
    Ashton this was something that alot of people where messing with to figure out.  Otherwise you had your gang jumping into the system 3-5 at a time and getting shreaded regarless of the enemy fleet. That whole Que thing war a MAJOR pain in the ass, shit I eve lost a fully T2 fitted Prophecy with a hold full of T2 loot because of a damn jump que. All this did was if you had made it into the system with a jump que but got hung up on the session change it allowed you to get in while you still had a fighting chance.
  • Ashton692Ashton692 Member Posts: 138

    Sure, lots of people may have been... I'm not blasting BOB, I'm blasting how the petitions were ignored.  (Although, frankly, if all this is true then BOB deserves a blast as well -- so much for their "we like fighting" line.)

  • kano71kano71 Member Posts: 207

    pointless thread..

  • CiredricCiredric Member Posts: 723

    Explain to me how avoiding the log in queue is not an exploit or a cheat.

    Have to love clueless people deciding an obvious exploit is ok in their book lol.

    It is pretty obvious to most of the game population that BOB has had inside information for some time.  For me it is this is a huge red flag.

    The problem as most of us see it, CCP continues to refuse to do anything about it.

    You have BOB officers making bannable comments on the forums only to have them deleted by the mods and then denying they ever took place.  Now explain to me how that is not direct favoritism?

    CCP has gone from one of the best dev teams to one of the worst in a short period of time and I see nothing changing.

  • NicoliNicoli Member Posts: 1,312
    What this allows you to avoid is the annoying issue with crashing during a session change or dropping due to a node crash. by having the secong instance of EVE setup you can avoid be stuck in a log in que whil;e your ship is anahilated as it was probably aggroed when it tried to warp off. It gives you a fighting chance. and surprise i found this out via just doing some simple tests while running my character around in empire.
  • Ashton692Ashton692 Member Posts: 138

    So was it a feature?

    Or was it a bug?

    If it was a feature - why didn't the GMs say that when they were near-spammed with petitions from ASCN?

    If it was a bug why did they say they found no Bug exploiting when they reviewed the logs?

    Either way -

  • Anan7Anan7 Member Posts: 13
    *Yawn
  • RollinDutchRollinDutch Member Posts: 550
    I used to do this all the time - when you jumped into a fleet of that size, the chance that the node would crash was about 100%. You then ctrl+Qed the main client and logged on the second client.



    You'd have to wait 3-4 minutes for the main client to show that the node's crashed - you can almost be back into the game before someone who's not doing this is even sure that the node dropped. The 'fix' to this 'exploit' was improving node stability so that most jumpins don't crash the node anymore, making this trick irrelevant (since if you ctrl+q and the node DOESNT crash, you're at a major disadvantage).
  • eowetheoweth Member Posts: 273

    Please rename this ignorant thread. A) you've "revealed" nothing about Dev cheating. B) It wasn't only BoB that did this, many others did it.

    Stop the witchhunt and grow up already, this is getting stupid. If you're in ANY way angry about whatever has happened, or anything your paranoid tin-foil baked brain can come up with, just quit and go away. Don't do this to yourself, having to come up with bizarre possible infractions or ancient history to keep this dumb issue going.

Sign In or Register to comment.