Quick Facts

Series

1.	A Disarming Distraction Core Access Codes
2.	Hacking the Wibson

Screenshots

Videos

Comments

Comment by troelala

This can be a hard quest if the text isn't read.
Use the Mech Control Scrambler every time it is off cd. You need to survive for 4 seconds every time before you can use it again, so keep your distance. Without the use of the Scrambler every cd, you will die. I needed to use it 3 times before he went down.

Comment by 695600

Do not go in the back side of the building to kite him away from the three Cursed Expedition Member, if he ventures too far into the building he will reset and you will have to start over.

Comment by 412181

You can take out EACH of the Cursed Expedition Members individually first, then tag the Mekgineer and use the scrambler. Correction to troelala on 09/27/2010: it is a FOURTEEN second (14 sec) cd, maybe it was changed with live Cata. I used the scrambler, hit him a few times, then ran away a little so I could heal and wait for cd; then I used the scrambler again, hit a few times and ran back toward the building to heal and wait for cd. "I" did this about 6 times before I was able to bring him down . . . but that's just ME. Maybe troelala had better gear or weapon or spells (whatever) than I have. Anyway, I got it done so I don't care.

Comment by Skreeran

If anyone cares, 2,700,136.5 hours is 308.2348 years, and 9,720,491,000 seconds.

Do gather data, I killed Cursed Engineers and timed myself with a stopwatch.

Killing ten engineers as a level 84 Undead Shadow Priest with an average itemlevel of 293 (3111 gear score on WoW-Heroes; 5797 Gearscore/Playerscore), it took me (in seconds):

15.851
16.187
15.351
15.825
15.219
15.980
15.175
15.902
16.451
13.951

to kill them. On average, that's 15.5892 seconds per engineer.

I also timed the time between engineers, and got (again, in seconds):

10.346
4.295
3.690
4.653
14.162
11.229
4.774
11.647
4.969
8.687

per engineer, or 7.8452 average seconds. The single digits were usually ones where there was another engineer nearby which I could jump right into combat with, while the double digits are ones where I had to look for one on my dragon.

So, starting with an engineer, taking on average 15.5892 seconds to kill it, and then taking 7.8452 average seconds to find another one gives me the figure of 23.4344 seconds per engineer total.

So, dividing 9,720,491,000 by 23.4344 gives me: 414,795,812.992, or around 400 million gnomes.

The expedition's numbers are extremely large indeed.

Comment by 744328

If you mouse over the quest giver on the map it says "Return tot he A.I.D.A Terminal"

Comment by 755725

I had some issue with this quest. The mobs weren't appearing. I finally gave up and finished other quests. Later I was able to see the mobs and they respawned very quickly.

It appears you can't do this quest when you are in the "war" phase of the Ramkahen quest line. If the mobs don't respawn within a minute, don't waste your time. You are in a different phase.

Comment by pinkconverse

"Dealing with them by conventional means would take you an estimated 2,700,136.5 hours."

So about the time it takes to level from 84 to 85, then. No problem.

Comment by owen67301

I don't know, I came in from the side, well out of aggro range, waited till he was back by the building then zapped him. took several zaps plus a lot of swinging in between, but I never had to deal with any of the other mobs at all, just killed the Mekgineer and looted and it was done. Rogue, but I wasn't stealthed just landed and attacked.

Comment by fordahord

Two points:

1) there is a scenario that keeps getting re-enacted whenever the mech despawns. At that time the level 83 humanoids are green and do not aggro (before the mech corrupts them). That would seem to be an optimum time to hit the mech.

2) The mech does NOT despawn upon entering the building. That was how I was able to kite him away from the corrupted humanoids and kill him.

Comment by cymon

He doesn't reset if you go through the building, his pathing just won't allow him to go out the back door so he goes out the front and around, i've done this on 3 different characters now where i lure him to the back of the building then step out and can heal or range attack while he tries to go around then step back in so he comes back

Comment by Peter4730

THIS IS HOW TO DO THE QUEST. None of the above comments allow fer the idiot-factor (which is ME). USE THE SCRAMBLER TO STUN TWIZ! When he is stunned, RUN IN and inflict damage. Use the scrambler as often as necessary to stun him and then go in for the attack. Ferget the idiots above boasting about "only took me three goes". (Took me a few more). The comments about 4 seconds are right. The effect will wear off Twiz after 10 secs, so you need to run away etc until scrambler is off cooldown 14 secs after activation (4 sec diff). (While running away, use HealPotion or get a pal to heal you).

Comment by 261995

Pull him to the right side of the bldg (started on the corner to his left, zapped to get argo, chains of ice, till CD on zapper, zapped, dps, run a bit chains, zapper, dps, 5 x and he was down hit me once, no aggro from other mobs. 83 DK easy if you have a slow/stun etc.

Comment by 942801

lvl 84 hunter with basic gear .. tanked with pet, dps from range, 1 attempt :)

Comment by 986407

very easy fight for my affection warlock :)

Links

Core Access Codes

Obtain the Core Access Codes from Twizzleflux the Insane.

	Core Access Codes (1)

Provided item:

	Mech Control Scrambler (1)

Description

The expedition's numbers are extremely large, user <name>.

Dealing with them by conventional means would take you an estimated 2,700,136.5 hours.

We can make use of a powerful source of energy held within expedition's crawler vehicle.

We will need the fusion core's access codes to accomplish this.

Mekgineer Twizzleflux has these codes and can be found at the Starwatch Tower to the southeast.

I've uploaded jamming frequencies to a scrambler. Use it to temporarily disable Twizzleflux's defenses.

Progress

Completion

Rewards

You will receive:

Gains

Upon completion of this quest you will gain:

See if you've already completed this by typing:

/run print(C_QuestLog.IsQuestFlaggedCompleted(27777))