I still don't like it but +1 for the great write up man. thanks for the info

I think the problem is they can't figure out how to make BPOs not get transferred.

Interesting point. They need to make those turn into single use items if hacked.

Or have BPO vehicles disappear at the end of the match. It would make BPO vehicles less of a juicy hacking target. You might get some modules off a BPO LAV through. I always add some shield extenders on mine.

I don't think BPO's should be deployed on the battlefield full stop ... when you deploy a fitting that uses a BPO it should simply deploy as a BPC ... as it would if you had manufactured a single run from the BPO or BPC (if you understand how they work in Eve)

Basically your fitting as deployed on the battlefield shouldn't contain BPO or BPC information (since these are blueprints used to manufacture an item) ... it should just contain 1 unit of that item, whether it was made from a BPO or a BPC is irrelevant ... once recalled or at the end of the match your personal assets are recalled in the current way, but hacked assets are converted back into BPCs and added to your loot window.

Edit : This is yet another case of DUST screwing around with the way things work in Eve to try to incorporate them in DUST, but completely botching it up because the mechanics aren't there yet to incorporate it properly !

If you know already then dont read this. This is for those that are new to this or those who have not figured it out.

Don't worry CCP, I'll explain this one. Consider it a freebie.

To understand this problem, you need to know about an issue that has existed since open beta and probably even longer than that.

Since I can remember, there has been a controversy as to what happens to a hacked vehicle. For a vehicle that gets destroyed, the answer is simple, the vehicle is gone and cannot be returned to anyone.

But what if the vehicle survives the match????
Questions been brought up like, Should the ownership be switched to the red dot that hacked it? what if they do not have the skills to drive it, should it be added to their inventory anyway? What if it gets re-hacked by a bluedot, should it get returned to the original owner or be transferred to the new blue dot? and if they do not have the skills to drive it, should they be allowed to keep it?

CCP has yet to make any changes to how hacking affects assets.

As of now, a vehicle remains under the ownership of the person who called it in. If it is hacked by an enemy, and it survives the match, it returns to the original owner. Likewise if a blue dot hacks it back, that blue dot can not recall it into their inventory. Only the original owner.

So if you haven't figured out the connection yet, here it is:

Because of the current settings, if a vehicle is hacked, the game still considers it under control of the blue dot that called it in. Which means that you will be SHOOTING at a FRIENDLY VEHICLE that is being DRIVEN by an ENEMY instead of what we usually think, SHOOTING at an ENEMY VEHICLE. This is why people get kicked.

This makes it more difficult to fix because its not a simple matter of telling the game that a vehicle gets hacked it becomes an enemy.

Before CCP can fix the friendly fire problem, they first need to change what happens to a HACKED VEHICLE. You can not just say that the vehicle becomes an enemy. Vehicles can be controlled by either side. The color changes based on whose in it. but the vehicle itself does not change.

I think there was some lore as to how mercs interacted with vehicles. hacking vehicles is simply unlocking the door because the tank for example, wont just let anyone go in. You can not hack the vehicle's systems until you are inside.

so their are two things you can do with this, this is my possible fix. Adding a second hacking cycle. The first hack (outside hack) changes who can enter the vehicle. If an enemy hacks the vehicle, it will keep you from getting in, and you will need to hack it back before you can recall/jump in.

If an enemy successfully hacks the vehicle. They can jump in the tank, but still cant use it. because the vehicle's ownership still belongs to the person that called it in. Once inside, they will begin a second hack that will switch ownership. This allows the original owner an opportunity to regain control. If the enemy achieves the 2nd hack, they now become owner of the vehicle and gets added to their inventory if it survives.

More importantly, with the ownership changing, the game will read the vehicle as becoming an enemy.

A simpler fix will be to simply switch ownership from the first hack but then we go back to arguing as to what should happen to a hacked vehicle and I dont want to start that.

But i hope I atleast explained clearly as to why you get kicked for shooting at a hacked vehicle.

If you know already then dont read this. This is for those that are new to this or those who have not figured it out.

Don't worry CCP, I'll explain this one. Consider it a freebie.

To understand this problem, you need to know about an issue that has existed since open beta and probably even longer than that.

Since I can remember, there has been a controversy as to what happens to a hacked vehicle. For a vehicle that gets destroyed, the answer is simple, the vehicle is gone and cannot be returned to anyone.

But what if the vehicle survives the match????
Questions been brought up like, Should the ownership be switched to the red dot that hacked it? what if they do not have the skills to drive it, should it be added to their inventory anyway? What if it gets re-hacked by a bluedot, should it get returned to the original owner or be transferred to the new blue dot? and if they do not have the skills to drive it, should they be allowed to keep it?

CCP has yet to make any changes to how hacking affects assets.

As of now, a vehicle remains under the ownership of the person who called it in. If it is hacked by an enemy, and it survives the match, it returns to the original owner. Likewise if a blue dot hacks it back, that blue dot can not recall it into their inventory. Only the original owner.

So if you haven't figured out the connection yet, here it is:

Because of the current settings, if a vehicle is hacked, the game still considers it under control of the blue dot that called it in. Which means that you will be SHOOTING at a FRIENDLY VEHICLE that is being DRIVEN by an ENEMY instead of what we usually think, SHOOTING at an ENEMY VEHICLE. This is why people get kicked.

This makes it more difficult to fix because its not a simple matter of telling the game that a vehicle gets hacked it becomes an enemy.

Before CCP can fix the friendly fire problem, they first need to change what happens to a HACKED VEHICLE. You can not just say that the vehicle becomes an enemy. Vehicles can be controlled by either side. The color changes based on whose in it. but the vehicle itself does not change.

I think there was some lore as to how mercs interacted with vehicles. hacking vehicles is simply unlocking the door because the tank for example, wont just let anyone go in. You can not hack the vehicle's systems until you are inside.

so their are two things you can do with this, this is my possible fix. Adding a second hacking cycle. The first hack (outside hack) changes who can enter the vehicle. If an enemy hacks the vehicle, it will keep you from getting in, and you will need to hack it back before you can recall/jump in.

If an enemy successfully hacks the vehicle. They can jump in the tank, but still cant use it. because the vehicle's ownership still belongs to the person that called it in. Once inside, they will begin a second hack that will switch ownership. This allows the original owner an opportunity to regain control. If the enemy achieves the 2nd hack, they now become owner of the vehicle and gets added to their inventory if it survives.

More importantly, with the ownership changing, the game will read the vehicle as becoming an enemy.

A simpler fix will be to simply switch ownership from the first hack but then we go back to arguing as to what should happen to a hacked vehicle and I dont want to start that.

But i hope I atleast explained clearly as to why you get kicked for shooting at a hacked vehicle.

Vehicles and everything on it should transfer when hacked. I don't think that there will be a major issue with AUR vehicles. I mean it's easy to hack a vehicle run it in front of a tank and the person lose the vehicle anyway. The question is what about those BPOs. I would say every BPO item gets transferred to a player after the match as the nearest equivalent normal item. Easiest way to handle BPOs.

Getting kicked is horrible though. I mean do I not destroy the tank that's killing everyone for fear of getting kicked? How do I even know if the tank started out as a blue?

I'm not sure if transferring ownership is a good idea. What about the modules installed in the vehicle? Do those transfer aswell? And what if people just use this to sell Aurum vehicles? What happens with BPOs?

I think that a simpler solution would be to consider that if you allowed the enemy to hack your vehicle, it should act as if you had already lost it. That would punish them for putting themselves in that position. What happens now, apart from kicking players in FW is a bit a contradiction. If i hack some guy's vehicle and i keep it intact until the end of the match, i'm helping him. Why would i do that?