NRDS Compliant Anti-Gank Permit

Good Lord how do these silly rumours start? Please tell me so i can set things straight. Otherwise your just making stuff up.

Edit: Also moved this over to the Crime and Punishment section.

4 Likes

Learn to read, miner. If the policy on pre-spawning CONCORD changes, it will be enforced for everybody, not just you.

3 Likes

Then why does CODE get away with continued pre-spawning? They use it every time that they gank.

Even if it’s not every time any time it is used is considered a violation, correct?

Gankers “get away” with pre-spawning CONCORD because it’s been stated by the GMs to be within the rules. By the same token, miners should be free to do it too. You and I are fighting on the same side right now. Have you failed to see the irony? There is no conspiracy.

4 Likes

You were the one who turned it in a conspiracy. Trying to create reality from nothing. Just like Kannibal Kane and CODE.

Did you know that I’ve been banned before for simply “pulling concord”? You don’t understand what is happening in this thread. We’re trying to get clarity for all our sakes, so that people don’t find themselves unable to play a game they’ve supported for years just because some developers think it’s best to shroud stuff like this in mystery.

@CCP_Falcon

3 Likes

image

please don’t, you jumped on the bandwagon that is was an exploit because a misinformed ISD said it sounded like an exploit…

2 Likes

So is pulling concord still allowed? This thread is confusing.

Because it’s not an exploit, nor is prespawning Concord at your location as a defensive tactic.

While the original ISD poster urged caution they are not a CCP employee, they are a volunteer moderator and thus may not know the ins and outs of areas of the game outside their ingame area of expertise.

TBH they may have been better off not using their ISD account to comment, as evidenced here some will take an ISD comment on game mechanics as being the word of CCP.

Until a GM says differently the current policy should be as stated by GM Lelouch.

Are people really being this dense on purpose?

Preposition Concord is not an exploit.

Prepositioning containers and ships so concord may go after them prior to the criminal is an exploit.

Really, it’s not that hard. All the ISD was trying to do is warn that prepositioning corncord is fine, but going any further puts you in exploit territory and may lead to a ban.

Is it really that hard?

So until clarity has been achieved then CODE Pulling CONCORD to delay CONCORDS arrival by performing other ganks in the system should be a ban able offense.

Here is the recent Pull of CONCORD in Eudama that CODE performed right before its gank on the gate.

Now if CODE isn’t Pulling CONCORD then how are they able to effectively gank a target?

Once they are ganked at the first station they warp away from the station in their pods to one of their Citadels where the Faction Police are not able to warp to deliver to them the consquences of their -10 sec status.

So if CODE isn’t actually trying to avoid being CONCORDED, which is an exploit, why do they pull the Faction Police to an NPC station and allow their ships to get destroyed and then warp their Pods to their Citadel and then to the gank?

Why doesn’t CODE simply warp from their Citadel directly to the gank?

Why isn’t the Citadel of CODE considered to be -10 security status as well seeing as how it like the ship and capsule of CODE are both vessels that the Capsuleer with the -10 sec status is contained in and can be attacked at any time? The Citadel is just another vessel that the -10 sec status pilot is contained in and should suffer the same consequences of the player owned ship and power owned capsule because the Citadel is a player owned structure unlike the NPC station.

Then there is the mechanic of tethering the pod to the Citadel which would transfer the aggression and criminal timer to the Citadel much the same way that aggression is transferred to a neutral remote repping ship that is repping a CODE ship that committed a gank.

The GM statement clearly says otherwise. Moving Concord is fine, the 6 seconds that they gain is within normal programmed parameters for a Concord response, thus it is not a delay; if they gained more time it would be considered to be an exploit because it would be outside the programmed response times.

Once they are ganked at the first station they warp away from the station in their pods to one of their Citadels where the Faction Police are not able to warp to deliver to them the consquences of their -10 sec status.

So if CODE isn’t actually trying to avoid being CONCORDED, which is an exploit, why do they pull the Faction Police to an NPC station and allow their ships to get destroyed and then warp their Pods to their Citadel and then to the gank?

Faction Police and Concord are not the same thing, when gankers undock under a criminal flag it is Concord that responds. The Faction Police just chase them around and shoot at them because of their low security status, not any flags that they have active.

Why isn’t the Citadel of CODE considered to be -10 security status as well seeing as how it like the ship and capsule of CODE are both vessels that the Capsuleer with the -10 sec status is contained in and can be attacked at any time? The Citadel is just another vessel that the -10 sec status pilot is contained in and should suffer the same consequences of the player owned ship and power owned capsule because the Citadel is a player owned structure unlike the NPC station.

Then there is the mechanic of tethering the pod to the Citadel which would transfer the aggression and criminal timer to the Citadel much the same way that aggression is transferred to a neutral remote repping ship that is repping a CODE ship that committed a gank.

Corporations don’t have a security status, a Citadel is a corp asset and thus doesn’t inherit flags from anybody using it.

That said it would be tres amusing if they did inherit flags, much mirth and merriment would occur.

1 Like

Then CODE is obviously prepositioning CONCORD when they go flashy red somewhere for 15 minutes prior to a gank.

I have watched CODE in Eudama go flashy red and have warped from gate to gate to see where they were ganking at with no signs of a wreck or a kill mail that would coincide with an actual gank other than ganking a friendly neutral to preposition CONCORD which is an exploit.

If CODE isn’t warping directly from the NPC station or their Citadel to the gank target then why are going flashy red before the gank?

CODE is hiding behind the gank mechanic in shooting neutrals as a form of a gank to preposition CONCORD prior to their actual gank. You don’t undock 20 rookie frigates to gank a neutral. Everyone in Eudama knows which stations CODE is holed up in so why are there rookie frigates being ganked outside of the stations where CODE is located?

Why don’t you see expensively fit ships leaving these stations or trade being conducted at those stations where CODE is holed up either. The reason being is that CODE uses them as staging areas and conduct any type of business in those stations would be certain to get ganked.

Perhaps you should look at your overview settings and figure out what flashy red means. I have not see flashy red in ages but mainly because I changed my overview so flashy red is a war target.

1 Like

A Citadel is a shell that surrounds CODE. It is no different than the capsule surrounding the - 10 RID CODE Clone, it is no different than the ship that contains the capsule that contains the Code Clone that is -10 Red is Dead Security status.

So while any CODE member is in the Citadel and is flashy red the Citadel should be able to be attacked by other Capsuleers in the same manner that a CODE Catalyst is attacked during a gank.

The Faction Police should also be able to attack the Citadel while CODE is located in the station due to the transfer of security status from CODE to the Citadel much the same way that security status is transferred to a ship with a CODE -10 Capsuleer contained within it.

Because as a matter of fact if CODE was to abandon their ship in space it would still get attacked by the Faction Police.

Once your security status drops below certain thresholds, the empire faction police will start hunting you when you enter high security system. Any cloaking device fitted to your ship will also be disabled based on the same criteria, so you cannot cloak up to avoid the faction police.

So why are Citadels being allowed to in essence “cloak up” the CODE member to avoid being attacked by the faction police?

So until clarity has been achieved then CODE Pulling CONCORD to delay CONCORDS arrival by performing other ganks in the system should be a ban able offense.

The GM statement clearly says otherwise. Moving Concord is fine, the 6 seconds that they gain is within normal programmed parameters for a Concord response, thus it is not a delay; if they gained more time it would be considered to be an exploit because it would be outside the programmed response times.

Link to where specifically any GM has stated what you just posted.

-10, docks in a freeport citadel just outside Jita.

Much merriment ensues as the freeport comes under attack because it’s inherited a flag from somebody that is docked in it.

Yeah you didn’t think that through did you? You don’t blow up a house full of people just because one is a burglar .

2 Likes

The GM post has already been linked.

Concord response times are well documented, in a 0.5 it is 19 seconds +/-1, if Concord are spawned elsewhere in the system it is 25 seconds +/-1.

The GM stated that prespawning Concord is not an exploit. Delaying or avoiding Concord is; gankers do neither, they don’t avoid Concord, and they don’t manipulate their response times outside of the programmed timescale that is an inherent part of the Concord mechanic.

1 Like

Just because you claim this and wish for a citadel to be defined this way, doesn’t make it true.

2 Likes

Link to the post instead of saying that is has already been linked. You made the comment you have to provide the link to support it not what someone else posted.