EVE General Discussion

Yeah, that won't get abused at all.

"Ok Bob, we have ten guys in this mining fleet, the gank fleet is ready. Join our fleet with your wardec and the gank fleet will warp in and kill everybody."

That is lame

Typical example of CCP having a good idea and then nerfing it into something 'meh'.

How's it different from a booster in a POS or an unscannable* one in a safe?

And who uses CS for off grid boosting? That's what T3 are for.

*assuming nobody's got a virtue set and perfect skills.

It's a bit different. It's more like a neutral RR ship with war targets. A neutral boosting t3 alt is just as bad. It's insanely lame. If you are affecting the fight then you better gd well be on the grid as the fight and be shootable.

To be fair, at least you have a possible chance to kill that guy legally anywhere in EVE, you don't if he is a neut yet he is fighting your war. So in all fairness, that guy +1 you 0.

Which is why I phrased it the way I did, the war target joins a non-war fleet. But just to be clear:

You are not in a war with anybody, and you form up a mining fleet, but nobody in the fleet is at war with anyone. Someone with a wardec joins the fleet from an invite from one of the other fleet members.

The idea that everybody in the fleet suddenly inherits the war dec means that, if planned right, a bunch of players from the opposing fleet could suddenly sweep in and kill the entire fleet without warning.

Now then, how do you propose the pop-up box be handled on that?
Does the fleet get to vote to not let the war-decced player in?
Do they get to auto drop if there is a player joining (would suck to take a bio break and miss the announcement)?
What if the fleet commander is in on the whole thing and warps the fleet TO the enemy fleet and 'joins the war' during the warp? Once in warp the whole group is screwed.

Just to be clear, if you join a war-active fleet, then I agree with you that you should be warned and you are a dumbass that should be a valid target. It is the opposite system that becomes the problem.

thank you for the asnwer Greyscale. atleast now we know what to expect and to not expect.

In my point of view it was going to get in to the inferno patch since something happend in the first patch
making the pods stay red of people who GCC in empire.

In answer of the neutral CS or T3 booster. if they are in a pos or safed up atleast you can move system
or buy a virtue set and probe them. <-- ways to counter

with a neutral CS or T3 booster you just see them jump with you to the next system and all you can try to do
is all go in suicide ganking bc's and loose sec status + 15 minute GCC meaning you can't even fight
there main gang that the alt was boosting in the first place.

Since these Booster are in so called leading places in a fleet ( squad, wing or fleet commander ) its dumb there
staying neutral .

Once again Greyscale thank you for the answer and Protip on this subject keep the players informed on things your
thinking to change.

Code for: We're going to wait until we're nearly finished, so that when all of you read about it and freak out about how messed up it is, it's too late in the development cycle to change it.

To various questions:

Was this ever going to be in Inferno?
No, not even a little bit Masterplan and Frellicus reimplemented the existing design pretty much from-scratch for Escalation so it's safe to work with (which is why there was sporadic Crimewatch funkiness after that patch); given that Escalation and Inferno are about about apart, and it takes about two weeks to tidy up fallout from one patch and we allow two weeks of "100% testing" before the next one, that would mean they'd have had approximately one lunch break to implement the entire redesign, which was never going to happen

Why isn't this already finished - what else are you working on instead?
Nothing; see previous answer regarding all the back-end groundwork that's been keeping us busy.

Why haven't you told us what you're doing?
Here's the presentation from Fanfest that explains pretty much everything.

No, I mean apart from that
That's not a question.

Pedant.
Yes. Anyway, the reasons are that 1) we're juuust about done planning all the work for it (see above re: two weeks' tidy up after a release), so until we lock down roughly what we're expecting to deliver there's really not a lot of point talking about it, and 2) if we talk about features that are coming later on in the year in a devblog a couple of weeks before Inferno, I would expect that to cause some [british]mild confusion[/british].