Main AFK cloaky thread

  1. stop being dohuja umniy
  2. scan it
  3. warp to the same grid with similar fitted interceptor
  4. align
  5. use overheat from time to time

I still donā€™t seem to have a answer to any of the questions I asked. Are you sure you know what you are talking about ?

I mean its ok if you donā€™t , just doesnā€™t quite make sense why you would shout it loud and clear on the forums . All you seem to keep saying is that I wont understand without actually attempting to explain the point you were trying to make. Thatā€™s cool , I guess

Since someone has already addressed the ceptor burning comment you made I will leave that for now .

If you could try answer my final question on my last post, what do you think my objective is when making suggestions towards cloaks? Really try this time .

Yea sorry completely forgot about wh spaceā€¦ ehh

/me puts on cloak.

YOU CANā€™T SEE ME!!

dodododoooooo
dodododoooooo

ā€¦

WAIT! THATā€™S IT!

Every time someone cloaks, it should play:

Systemwide.
On every client.
And you canā€™t mute.

All problems solved.

The End.

Best idea ever :rofl::rofl::rofl:

1 Like

Are you saying that you can repair modules with nanopaste while theyā€™re still running? Nope, you canā€™t. Your mwd will burn out loooooooong before you get to catch up.

Just accept that thereā€™s no way for you to get him and move on.


Your question has been answered, itā€™s just your lack of knowledge about game mechanics and inability of reading comprehension that is the problem. Iā€™m not going to waste my time trying to educate you on a subject you consider yourself knowledgeable about when you donā€™t have a clue. I tried it before with others, but you people are all the same. Either you donā€™t want to learn or you simply are unable to learn, for whatever reason, and believe you are right, denying any and all facts about the opposite.

You want the answer to your initial suggestion? Then use the god damn ā– ā– ā– ā– ā– ā– ā–  search function or just look through this very thread. You are not entitled to have it answered for the 23572359087236th time just because you donā€™t want to spend 10 seconds on looking for the answer.

And just that you get it this time:

means: I donā€™t give a ā– ā– ā– ā–  about this thread and Iā€™m not reading it anymore. Itā€™s on my muted list like all the other afk cloaker whine threads and the only reason Iā€™m occasionally looking in here is my tendency to torture myself whenever the thread title shows up under ā€˜latestā€™, something I asked CCP to fix.

Jesus ,

I donā€™t think the eve forums are best place for you bro , a tad on the unstable side I think , stay well

1 Like

I took it ti mean you would effectively pulse OH, allow cooling, and repair damage when required. You would then catch up a bit ā†’ hold station ā†’ catch up a bit more ā†’ hold station etc etc

As you cannot repair module when they are active, you would have to turn it off and fall quite far behind.

If you are in the same fit you would hold station at the same range, catching up bit by bit with each pulse. There is always a way to catch someone.

You arenā€™t reading.

You have to turn it off to repair it. If you turn it off there is zero chance of any form of station keeping.

If theyā€™re moving 15km/s and you turn it off for even just 5 seconds to repair (which lets face it is far shorter than it would actually be) youā€™d end up falling behind at least 60km (accounting for non-prop speed). It would put you farther behind to overheat than to just stay unheated, because of turning it off.

Literally the ONLY way you could do this with heat is if you somehow fit two MWDs.

Doh! Of courseā€¦thatā€™s what happens when you try keeping up with threads in work and boredom is melting your brain :smiley:

1 Like

This is literally me right now:
image

So yea, I totally get it.

Iā€™m a DBA, so Iā€™m ā€˜Waiting for the developers to compile their code and test itā€¦ā€™

See, Iā€™m a specialist so I can slack^2ā€¦

What a dumpster fire

Technically Iā€™m a network admin. But I donā€™t like the tools available to monitor my everything, so I am building my own between putting out fires.

I used to think that was an excellent expressionā€¦ butā€¦ I think I found a new way to describe what most people do in this thread:

1 Like

Are you plaing this game only on forum?

10 Turn overheat for 1 (one) mwd cycle on
20 Turn overheat off
30 Wait till rack cool off
40 goto 10

I may actualy try that sometime, thanks for the suggestion.

Even if it were not possible, as opposed to just very difficult, to catch an interceptor burning like that, it would still be an improvement.

You could check with probes on his position while you were active to ascertain his position. two consecutive hits would tell you he is going in a straight line. You could check as often as you like to be sure he is on that heading, probably AFK and almost certainly not doing anything you care about.

If he sets up a script in some fashion to make turns, he may be even easier to catch, as watching him for patterns could allow you to get ahead of him in his route. Failing that, over a few days you can make a pretty compelling argument for him being a bot. Someone online for 23 hours a day only making occasional course adjustments in empty space is almost assuredly not human.

Regardless, small chance with effort is better than no chance regardless of effort.

And you mean to tell me that in a situation where heat damage is chance-based and can occur with any amount of heat, a single cycle of heat on your MWD (something known to produce a lot of heat to begin with, increasing the chances of module damage) will have a 0% chance to cause heat damage?

Iā€™ll give it a try tonight to validate my belief, Iā€™d suggest you do the same. Iā€™m 100% sure youā€™d burn out your prop mod before you caught up to them.