Wormholes

My unhappiness wirh the sleeper farming meta is that it is often destructive in terms of social interaction within the corp rather than constructive. It leads to cliques and some being included and others not. Perhaps if sites were less predictable and more likely to result in dangerous situations a more team based meta would emerge.

Here is what I am thinking. First, make the sites rare and life limited whether run or not. For example imagine that a site is rare enough to be cherished and despawns after 1 to 3 hours. Our brave adventurers would then feel they have to run the site at the moment that they appear, utilizing whoever was around rather than waiting for an ideal moment and the ideal crew. Then when the site is completed an escalation site spawns in the static or perhaps in another randomly selected wormhole accessed through the unstable rift. When that one is completed yet another escalation can spawn in a similar manner resulting in a dynamic nomadic experience of activity in environments which are less pristine and more unpredictable than is the norm today. If capitals are viewed as required provide some sort of unstable rift portal or other means which allows the ones used for the site (but not others) to travel to the next site and then later return in a manner outside the normal travel mass limits. Functionally it could be as simple as using a rift as an unconvientional cyno of some sort. Also, if the next site is in the static, it would be rather foolish to crit it beforehand. A dynamic situation such as this proposal would be more team oriented than the current situation.

I'm going to throw my 0.02 into this cluster**** of a thread.

First off, commenting on other peoples posts:



1. Interesting, but hardly effectual. More than likely the pheonix will start to become the flavour of the week to run cap escalations, as range doesn't matter, as long as its within the max.
2. Useless. Running 3-4 painting huginns will make any ships signature so huge that it won't matter.
3. More interesting, could be good, but realistically, the fleets will overcome with sheer numbers.
4. MJD is useless, it's so rare to really do much other than a quick web. And again, this points to using the pheonix. If they MJD away



I agree with the increased spawn rate on WHs, though I would do a different approach. I would increase the number of floating connections immensly. I would have something like 100-150 c5/c6<->c5/c6 roaming statics, and maybe 70 c4<->c5/c6 roaming statics added to the WH charts. This would allow for more action.

On a second part to this, I would also increase the number of high class WH space frig holes, because those are essentially impossible to close. And we all know how much a fleet of bombers can do to a cap escalation.



Yes you can, it's called pheonix. All it would do is shift the people using nags now to pheonixes... and in what 3 months training time, we'd be back at the exact same spot.

Also, I would like to point out Missy Bunnz as a great source for this information. In my few months with TP way back in the day, I learned a lot from Missy. It's helped my game tons.

Now, as to the changes I would make

1) You cannot escalate a site for 4 days in a row anymore. I would allow 1 cap escalation on a site total. You could still farm the site for 4 days, but you'd only get 1 full set of cap escalations. If you want to roll the site out, and hope a new one spawns, go ahead and do it.

2) My comments about the number of WH connections posted a bit higher up. The increase in the number of WHs will allow for groups to notice these things go on, and allowing for less impunity while running cap fleets/marauders/static sites etc.

3) I would allow for traditional escalations in Shattered only WHs, by that I mean, you can get upto 4 days worth of escalations from a site in shattered space. This might encourage groups to do incursions into a shattered for a few days at a time to dramatically boost isk, with the risk of getting caught.

4) I would buff the sites: Oruze Osobnyk, Quarantine Area, and Strange Energy Readings. All three of these sites have random triggers. I would keep the random triggers, and make sure that they can happen at any time (not just killing the last ship of a particular class) in order to increase the difficulty in these c5/c6 sites. Ideally they should be worth 10-15% more than the Core sites.

5) I would add new sleeper rats that have offensive EWAR capabilities, such as jams, sensor damps etc. I would make them reasonably effective (jam rate of 20-40%, sensor damp effect of 30-50%, etc) which would require more maneuvering and such to accomplish the sites. This would only apply to escalation battleships.

6) In heavily escalated sites, I would put in a delay timer between the escalations of 60 seconds to 3 minutes where the escalating capital HAS to stay on grid for that time. This would only apply to 2nd-3rd-4th order escalations at the same time.

So for example, my corp as 4 dreads and 2 carriers, and 3 webbing lokis on the standby.

FC calls for 1 carrier to go in, and set up triage. Then 30s later, the webbing lokis are told to warp in. Once this is up. FC calls for the rest of the capitals to escalate. About a minute and a half later, the remaining caps (5 dreads and 1 carrier land). The game has a timer running, which has 45 seconds left before the next escalation spawns. After the 45 seconds, the next escalation spawns. 1 Minute and 50 seconds later, wave 3 spawns. and 30s later, wave 4 spawns.

7) In combination with point 6, I would increase the buffer of the escalated battleships by 40%, which means they can't be one-shotted by less than 3 or 4 dreads. Also, as in point 5, these escalated battleships will be using offensive EWAR on all appropriate targets (siege/triage are still immune).

Theres only 112ish c6's are you saying make c6's have dual statics on one of those being a c5?

Doublepost

Alone

That would have taken about... two months, plus two PLEXs to dual train my scanning alt who is nowhere near flying a marauder, or for that matter anything bigger than a Proteus.

Dersen has all BS at 4, so he'd only have been idling for 1 month.

EDIT: Besides, I don't do the lone wolf thing well. I like flying with small groups of people.

It seems like the WH dwellers are the last "real Eve" players. They don't want their items protected in citadels. They call for an isk nerf in their part of space.

You don't hear these things coming from null seccers and that is the problem. wH will be more risk less reward and null sec will continue to get safer and have added ways to make isk to keep the complainers quiet.

I think you should keep the potential income the same but vary the ways to make it. I don't want WH guys to be the last authentic Eve players and be the poor kids on the block as a result.

When you're running anoms/sites, sleepers from other anoms should move to the one being run, adjacent system's anoms' population should migrate over to answer their brethrens' distress calls. With some serious pve activity next door, closing the hole to stop *your* sleepers from running towards your neighbours should be the least you have to do.

Might be interesting if you suddenly face 40 sleeper BS - *to deep*, he yelled.

As far as I can tell WH space is getting quieter.

Increase the content/isk in lower class wh's and then maybe people will move up to higher class.

Where the risk's are greater but so is the reward.

No I ******* didn't. I said something along the lines of "what do you think of us removing them" because I wanted just to see what you people thought. I have no plans or intentions of touching capital escalations. They are not even an area of the game I work on or want to work on. To many other things for me to be doing.