Add some of the major WH alliances to your contacts list. Done?

Right.

Now go into an incursion constellation.

You'll see a whole **** load of WH residents there, as well as lots of nullsec folk.

So much so, it was awkard for me to get fleets as BUGRY are set -10 to most WH alliances

How big is a "major wh alliance?"

I happen to know numerous highsec carebears who's moved into whs since Incursion expansion. Since t3 market is stable, I'm going to take your completely objective first hand observation under advisement.

Add some of the major WH alliances to your contacts list. Done?

You also seem to forget (repeatedly) that the risk in a WH isn't coming from a PVE encounter.

This is one of the dumbest points made in this thread.

You can spam D-scan to reduce your WH risk to something near 0?

His comment read as "If incursions were so good, WH residents would be doing them [instead of WH anoms]"

Which any effort will show you is true.

It's only dumb if you can't read.

You can spam D-scan to reduce your WH risk to something near 0?

The ignorance in game mechanics expressed here is phenomenal.

Cloaked ships? Prebookmarked sites? Good probers?

D-scan provides moderate safety. But as anyone who has spent some time in w-space knows, its not a matter of if you'll get taken down, but a matter of when.

His comment read as....they are so good that wh residents are doing them...

Incursion income needs a nerf.

I'm not sure who you're trying to disagree with at the moment

WH residents are doing them, given that both myself, members of my alliance, and members of WH alliances I've got on contacts lists are going them. Not to mention the number of null-alts you see around.

100mil+ an hour in highsec needs a nerf, on that we will agree (though whilst they're there....)

im not talking about risk vs. reward or WH saftey guys.

i was just curious if i was to log in play for 5-8 hours what would make me more isk a C5 or highsec incursions

the only alliances i would even consider is Talcan United or Norwhals so im sure those guys have security in check

Since everyone is getting out of whs and doing incursions, we must speculate on t3 stuff, prices are gonna rise... Oh wait, they're not.

People move into whs... and they move out... If market trends are to be believed, more people moving in than out.

Again:

a) More reasons to live in a WH than to run anoms, so looking at a general trend is stupid
b) You're ********

The fact that you find people whose corp holds C5/C6 wormholes, as well as null residents in highsec running their PVE, isn't indicative of some issue to you, then?

100-150 mil an hour, which I made soloing C1s with a salvage alt in tow. In my time in w-space,

Yes, I do find the dropping t3 prices and increasing supply of t3 material to be indicative of more people moving into whs than out of whs.

I also see null blobbers moving to empire, and empire carebears moving to null. People move.

You can spam D-scan to reduce your WH risk to something near 0?

Why is it in so many of your posts you have a bias against someone? Null sec blobbers, empire carebears...CCP sucks, etc etc.

Biomass your characters and stop trolling these forums.

Did you ever lived in a WH ?

Most of WH, especialy low class are often camped by afk cloaker, and remember clocked ships are not only ***** frigates today.

You have a cooldown on the D-scan refresh, you can easily miss someone entered in the system, especialy when there is several gates poped.

The only safe mode you can get in a WH is when you know nobody entered in the system since few hours, and you are inside a site (not an anomaly) as you have time to see eventual probes ...

Sure, if you scan very often (every few seconds), you can limit your risk but not avoid them 100%

Why would afk cloaker camp a wh? Clearly, you have actually lived in whs and noticed those evil afk cloakers on local, thus preventing you from undocking.

It's safe if you're not stupid. And there are macros that cycle the dscan for you nowdays, get with the program.

Yes, I do find the dropping t3 prices and increasing supply of t3 material to be indicative of more people moving into whs than out of whs.

I also see null blobbers moving to empire, and empire carebears moving to null. People move.

Faceless forum alt says hello. Also, all my alts and alliance peons like me too, on every one of my posts. And nice drake blobs, valuable contribution of TEST to Eve.

Why would afk cloaker camp a wh? Clearly, you have actually lived in whs and noticed those evil afk cloakers on local, thus preventing you from undocking.

It's safe if you're not stupid. And there are macros that cycle the dscan for you nowdays, get with the program.

It is precisely BECAUSE there is no local, that camping the wormhole works, ******.

You simply find an occupied wormhole, scan down every site, then cloak and wait.

People log on, go do stuff. You can then warp to them without popping probes.

You're clearly ******** mate, keep posting ****. It's amusing to see someone so terribly bad **** post like they have a clue.

Be afraid... be very afraid, 23/7. Because the unseen afk cloaky is always out there, even though he's afk, and whether he exists or not.

I personally have been making 100million p/h running vanguards. There is NOTHING as consistent as incursions for making Isk.

Do they need nerfing?

The answer is no, simply because there is alot of risk involved just as there is in a wormhole space. If a Basi pilot disconnects then the entire fleet can be popped very easily resulting in anything upto 50 billion isk being lost maybe more depending on fleet composition and modules installed.

Competeing in certain sites calls for killing tamas and spawning more Sansha in the hope of the DPS overwhelming the opposing fleets Logis and getting that fleet popped.

I have lived in a C3 for a long time but a C5-6 can't get alot of traffic really and even if they did your running with capitals with triage so that fleet is pretty much safe, Battleships arn't gonna warp in and try for the gank are they? lol...

Leave incursions alone, working as intended.