This isn't exactly the same thing, though. Changing corps in space/mid-flight is an exploit because you can get someone CONCORDed because of it. CONCORD does not operate in low-sec and the only penalty you have is a relatively minor sec-hit which can be repaired in less than an hour.

Whilst shooting WT PCOs that had just left RF the WTs swapped ownership to a neutral corp causing fleet to take sec hits and GCC for all PCOs that were destroyed. If they had been even more cunning they would have changed it to a FW corp forcing us to take standing hits as well.

CCP post in this thread now confirms intended game design, so here is the helpful guide to decreasing hostile standings and security status. Remember all you need is to get one pilot -5 and their logi chain will GCC during normal combat so these security losses do matter.

Apparently although intended mechanics this may somehow still be an exploit so until we have further confirmation use this guide at your own risk.


FW players here is how to make a hostile fleet take a standing hit, security status loss and GCC if they want to destroy your structures


1. Set up PCO and use as normal, ideally in hostile space to gain maximum attention


2. Set up an alt corp in the hostile miltia (you probably already have one or two spare anyway)


3. Wait for the eve mail saying the PCO has been reinforced


4. When the hostile fleet start shooting it at after RF ends you swap ownership to the hostile militia corp and watch them all (including logi because CCP still haven't fixed that bug) take a large standing hit, security status loss and GCC.

You can either do this early on in the fight and give them the option to disengage or try and do it last minute, the WT red star remains on the targeted item so they probably won't notice in time.


5. Rinse and repeat untill hostile players start running out of standings.


6. ????


7. Profit and laugh at CCP's complete ineptitude at game design and continued neglect for FW

If you intend to keep the possibility of switching ownership while it's under attack, then in my opinion you absolutely *must* prioritise fixing of the FW standings loss bug. It's been with us for more than a year anyway which is Not Good, and with this mechanic it has become extremely exploitable as noted above.

Ok so an update on this, we are going to deny transferring ownership while the customs office is being attacked using the normal 15 min cool down on aggression. The real problem here is that players can be tricked into taking a security status hit or entering into combat outside of a wardec without realizing it.

Transferring ownership after a POCO has been put into reinforce for example is still valid and while this does allow owners to force an aggressor who they are at war with to take a security hit they will still be able to decide before hand if they want to do this and not unknowingly engage an owner they are not at war with.

I have hassled people today so that we can get this onto TQ this week but that will ultimately depend on QA checking it so fingers crossed.

Great... we can decide beforehand if we want to go gcc as we return to the poco of a corp we wardeced to find it in new alt corp hands.
We place a new wardec on the alt corp, get the pleasure of shooting it from 100% to reinf again. Comeback next day to finish it what will we find? That its been transfered to a new or old alt corp we are no longer at war with.

You fix the sudden standing hits, it dosent take away the problem with the poco hoping.
No. People that RP 'No GCC Ever because its against the law!' or FW people that will receive WTF standing hits and unable to fight an enemy because they gone gcc and cant remote rep etc eachother? People that play it by the books by using wardecs should not have to sit back and watch things hop around freely in an neverending tail of wardecs.
No its not the security hit iam arguing against or the rpers pov or even fw peoples pov. Its the principle that the mechanic as you intend it is broken. GCC means your a lawbreaker and you should NOT have to be that to perform an action against an enemy.

Do away with gcc or make it mean nothing! if going GCC is required in order to accomplish a task in the game it shouldnt come with the downfalls currently associated with it. Patchwork Fixes Aint Fixes when the Mechanic remains broken.

Edit
The simplest soloution for the 'Valid reasons to transfer':

TransferPocoScript:

If(MyCorp.InFactionalWarfare==Yes )
If PocoToTransfer.IsDamageD or isReinforced
Return "No you cannot transfer a damage or reinf poco while in factional warfare, ride the storm out chicken"

Elseif(MyCorp.InFactionalWarfare==No)
If Poco.TransferToCorp is InList(MyCorp.AtWarWithWho)
return "Yes, you can transfer poco to a corp your currently at war with, nevermind decshields thats a separate and hard cracked issue"
else
return "No, you cant sadly transfer the poco to that corp since its not one your at war with"

That would in essence, with littleish coding make it so that you cant transfer a poco around madly. You can give it as tribute to a corp/alliance your at war with, long as your not in fw(because then you transfer it to militia alt corp :P).

That or a 36hr transfer timer when at war could be simple things to sort the problem =)

Thanks. Peace and Good Night Iceland.