EVE General Discussion

Seriously, are you just trying to be dense as a kneejerk reaction to being wrong?

The situation used both mechanics, at the same time. Don't ignore facts.

I dont agree with taking bumping out . Im a pvper ,so i know bumping is an essential part of pvp. However there should be a way to call a GM if youre
1 Your in high sec and not being bumped by a war target
2 getting bumped in a manor like this so he can insta ban hammer the offenders and place the bumped freighter/orca etc in a station.

If you used an alpha fleet like the good old days theres nothing to complain about.

I gotta get some locator agents so I can gank this guy every time he undocks.

Im saying theres a way to kill a freighter with 30 catalysts besides uainsg an exploit

You can flame me all you want the video Speaks a million words .

Yea Im crying . LOTS of tears mmmmmmhhmmmmm

Game Mechanics 101

All Mechanics have uses that arent intended
This is a thread about CCP'S intent
Do they agree with you or me
Well find out when they rule on the Petition
But for now its up for discussion

Maybe your But Hurt Because My Ubber PVP Ship Personally Pillaged your Fail Pilotted one when you were AAA (Tripple EYY) ?

GOON TEARS THREATENNING CCP BUT IM A COWARD NOOB LOL
By Sion Kumitomo

Dear CCP:

I love spaceships. I love the sandbox. The sheer possibilities afforded by the near-limitless options and the organic player-driven content are things you just can't find anywhere else. So what I say next, I say out of deep concern. Though you might find it hurtful, it is not meant to hurt.

Incompetence like this ruins your sandbox.

By 'this', I mean the re-mapping of the node in Z9PP during the battle yesterday. The battle in Z9PP started with the destruction of a TEST ihub around downtime, and over the next twelve hours, the system saw varying levels of continued conflict. At peak, local was near 2000 pilots with more set to join the fray. That is, the battle itself was still in the process of escalating. All of this was abruptly ended by the incompetence of your engineers. Further escalation of the battle would have seen hundreds of capitals lost, and supers perhaps fielded or lost. It would have been a battle to remember, a battle that would have graced headlines, a battle pilots would have recalled with pride, or with horror. And that's just the start of what your mistake cost you and thousands of players.

I've seen allegations of t20 levels of conspiracy by various parties, but I think we both know that's not the case. You didn't do this out of malice—I'm certain it was just as you said here, a mistake. Mistakes are fine, everyone makes them. But making the same mistake repeatedly means you aren't learning from them. GSF's own dread fleet was saved by a similar node remap a scant couple of weeks ago, a similar missed opportunity to showcase the vibrant and violent nature of EVE.

But incompetence is worse than malice.

As a company that thrives on occupying a niche in the MMO market, it is in your best interests to prevent this from ever occurring again. These kinds of massive battles and the surrounding narratives are what give you free publicity, both through word of mouth and in the gaming press. If you don't hold your people accountable, and if you don't strive to ensure that checks are in place to prevent this, you're not just hurting the players involved directly, you're hurting the whole game—including yourselves.

You cannot risk your reputation becoming 'lol CCP', nor can you afford to pass up the windfall that massive battles generate for you. What astounds me most is that something like this, something so precious and important to your business model, is something that doesn't have multiple checks in place to prevent just such an event from occurring. This wasn't “just a fight”. These events and others like them are what drive the whole of EVE. It should come as no surprise that players expect pvp to matter in a game built around the integral idea that pvp matters.

Why you wouldn't protect these events as much as you are able is quite utterly beyond me. I don't mean to denigrate other aspects of the game, of course, but let's be honest: the biggest draw of EVE is the possibility that you will have a part in something major. And when it comes to that, very little equals a huge war-turning battle, the murder of a capfleet, or the destruction of thousands of ships. Remember Asakai? That now infamous system and so many others like it are the beating heart of this game. Massive battles are your piles of gold, their stories your frankincense, and their widespread impacts your myrrh.

You can't make pvp matter without making it matter when it matters the most. You cannot allow typos to undermine your game and the potential of EVE, not when it is something so important to your business model.

I don't want a witch hunt. No one does. You've already given us answers as to what happened, and I commend your openness. Communication lets all of us know what transpired and is a great starting point. But it is just that, a starting point. Moreover, what was offered was merely an apology, whereas what you require is action towards a permanent solution. My sincere hope is that you address this issue and communicate to us how it has been addressed. Failing that, I suspect we'll have our answers during the next major fleet battle.

But remember, CCP, this isn't just about the fights. As stewards of the sandbox, you are accountable for it, and it is your reputation and your game that are at stake. So for your sake and ours, the remapping of a node with an active battle must not be allowed to happen again.

Your players understand these implications, CCP. Do you?

I'm mildly curious why you're all on the same page throwing "intent" around like it means something. You can't reference a single instance of CCP mentioning anything even remotely similar, so.... Do Goons have some sort of internal memo on the topic? Is it just a convenient loophole to cling to? Too many lawyer dramas maybe? Perhaps you just like my rambling on the topic?

Inquiring minds want to know.