During several games last evening myself and several other members of the DUST 514 community were all talking about hacking vehicles in a battle.

Currently when you hack an enemy vehicle you simply are granted friendly access to the LAV/HAV or Dropship for however long it takes you to run it off a cliff and blow it up Gumball Rally style.

The assumption was made that if you hacked the vehicle, you could keep it in your assets as you effectively "stole" it from your enemy, much like scamming or more specifically looting occurs in EVE Online.

CCP and fellow DUST players, I propose a change to the current system in which if/when you hack someones vehicle you can recall it and save the vehicle for future deployment either in that battle, or in whatever battle you wish in the future. This vehicle would and should be represented in your post match "Salvage" section, on top of any other salvage you might have received during that match.

This game mechanic is both a way to curb people from spawning tons of vehicles in a match, as well as provide those who hack the vehicle a reward for their effort.

I have brought this up to a CPM0 member and he is in support of it, and I hope both CCP and the DUST community would consider this proposal a good way to curb the mass vehicle spawning and provide people more incentives to work in the "Hacking" side of things for their respective armies.

A little tack-on here - it goes without saying that going this route would mean that you wouldn't be able to call in your salvage if you don't have the skills for it. It would work just as any other item you have in your inventory.

This is a great thread. Let me provide some background.

We have discussed allowing players to directly salvage items - not just for vehicles, on the battlefield. I really like the proposal for the vehicle salvage, where hacked vehicles can be recalled into the hacker's inventory. To do this however, we would have to resolve a couple of technical issues:

1. Rather than making a vehicle usable by a particular team/individual after being hacked, enforce the concept of a new "owner" of the vehicle, so that the vehicle knows where to go to when being recalled.

2. Each blueprint and corresponding item would need to be linked. It wouldn't be feasible (or make much sense) to allow players who have hacked a vehicle that is a blueprint or has blueprints on it to inherit that blueprint. Rather, we would want a recall to place a blueprint's corresponding consumable item in the player's inventory.

This isn't a gargantuan task, but it's not something we can quickly deploy as part of a hotfix.

Thanks for the feedback guys, I will see what I can do.

As far as I know, it was supposed to be this way already.

When I saw the recall feature at fanfest, the first thing I asked CCP Jian was "Can I use this to steal people's stuff?" He said Yes.

I think it's a bug that it doesn't work with enemy vehicles. But it should definitely add the stuff to your assets if you steal a friendly, non bpo vehicle.

Someone try it and let me know?

2. Each blueprint and corresponding item would need to be linked. It wouldn't be feasible (or make much sense) to allow players who have hacked a vehicle that is a blueprint or has blueprints on it to inherit that blueprint. Rather, we would want a recall to place a blueprint's corresponding consumable item in the player's inventory.

This is a great thread. Let me provide some background.

We have discussed allowing players to directly salvage items - not just for vehicles, on the battlefield. I really like the proposal for the vehicle salvage, where hacked vehicles can be recalled into the hacker's inventory. To do this however, we would have to resolve a couple of technical issues:

1. Rather than making a vehicle usable by a particular team/individual after being hacked, enforce the concept of a new "owner" of the vehicle, so that the vehicle knows where to go to when being recalled.

2. Each blueprint and corresponding item would need to be linked. It wouldn't be feasible (or make much sense) to allow players who have hacked a vehicle that is a blueprint or has blueprints on it to inherit that blueprint. Rather, we would want a recall to place a blueprint's corresponding consumable item in the player's inventory.

This isn't a gargantuan task, but it's not something we can quickly deploy as part of a hotfix.

Thanks for the feedback guys, I will see what I can do.

So, you are proposing that a consumable item gets popped out from nowhere? That seems ripe for abuse.

This is a great thread. Let me provide some background.

We have discussed allowing players to directly salvage items - not just for vehicles, on the battlefield. I really like the proposal for the vehicle salvage, where hacked vehicles can be recalled into the hacker's inventory. To do this however, we would have to resolve a couple of technical issues:

1. Rather than making a vehicle usable by a particular team/individual after being hacked, enforce the concept of a new "owner" of the vehicle, so that the vehicle knows where to go to when being recalled.

2. Each blueprint and corresponding item would need to be linked. It wouldn't be feasible (or make much sense) to allow players who have hacked a vehicle that is a blueprint or has blueprints on it to inherit that blueprint. Rather, we would want a recall to place a blueprint's corresponding consumable item in the player's inventory.

This isn't a gargantuan task, but it's not something we can quickly deploy as part of a hotfix.

Thanks for the feedback guys, I will see what I can do.

This is a great thread. Let me provide some background.

We have discussed allowing players to directly salvage items - not just for vehicles, on the battlefield. I really like the proposal for the vehicle salvage, where hacked vehicles can be recalled into the hacker's inventory. To do this however, we would have to resolve a couple of technical issues:

1. Rather than making a vehicle usable by a particular team/individual after being hacked, enforce the concept of a new "owner" of the vehicle, so that the vehicle knows where to go to when being recalled.

2. Each blueprint and corresponding item would need to be linked. It wouldn't be feasible (or make much sense) to allow players who have hacked a vehicle that is a blueprint or has blueprints on it to inherit that blueprint. Rather, we would want a recall to place a blueprint's corresponding consumable item in the player's inventory.

This isn't a gargantuan task, but it's not something we can quickly deploy as part of a hotfix.

Thanks for the feedback guys, I will see what I can do.

This is a great thread. Let me provide some background.

We have discussed allowing players to directly salvage items - not just for vehicles, on the battlefield. I really like the proposal for the vehicle salvage, where hacked vehicles can be recalled into the hacker's inventory. To do this however, we would have to resolve a couple of technical issues:

1. Rather than making a vehicle usable by a particular team/individual after being hacked, enforce the concept of a new "owner" of the vehicle, so that the vehicle knows where to go to when being recalled.

2. Each blueprint and corresponding item would need to be linked. It wouldn't be feasible (or make much sense) to allow players who have hacked a vehicle that is a blueprint or has blueprints on it to inherit that blueprint. Rather, we would want a recall to place a blueprint's corresponding consumable item in the player's inventory.

This isn't a gargantuan task, but it's not something we can quickly deploy as part of a hotfix.

Thanks for the feedback guys, I will see what I can do.

A little tack-on here - it goes without saying that going this route would mean that you wouldn't be able to call in your salvage if you don't have the skills for it. It would work just as any other item you have in your inventory.

And finally, this will allow teammates to hack it back and, should they recall it, it will go back to the original owner.

• Kaze calls in Sica. Enemy Logi LAV with 7000 EHP runs him over.
• Enemy hacks Sica. /owner2/ field change's to enemy's name.
• Enemy killed by Nova Knives by Kaze's teammate. Kaze's teammate hacks the Sica back. /owner2/ field is changed back to blank or null.
• Kaze's teammate recalls Sica. Goes back into Kaze's inventory.

That asking difficult question is easy part I think that the last guy that recall it would be really **** off that it didn't end up in his pocket, he risk his life while recalling it .

This situation is easy in Eve compare to Dust - after the whole gang thing FC shares loot among people that lose their ships during the battle to reimburse theirs losses(if no one lose ship all loot is going to corp "PvP shop", and people may buy this stuff for 50-75% of it's real value).

I would not mind if the entire pool of salvage after battle go to corp assets in Dust, and some director would have to split it among mercenaries(or not - if he is greedy). Today, when I losing HAV on battle there is very small chance that ISK reward plus salvage will make me happy at the end of this day. Corporation salvage-pool could save my day.

What would you say if every hacked and recalled enemy vehicle would go to Corporation-loot-pool? That would prevent people from killing each other just to hack and recall valuable enemy vehicles. Corp loot pool would be a system that allow to reward fairly more than just one guy, because it's not a job just for singiel guy - someone will have to cover guy who is hacking, and recalling vehicle. It would allow to grow corporation assets. We already collect tons of unnecessary items in our assets, so what's the difference if they will go to hends of corporation that may use it in future, or save it for hard times.

It would not be that difficult to make a copy of the blueprint item, or at least I would not imagine it would. I would like to see more salvage than just the random drops we get now, and salvage that is relevant to what the opponents were using. Current salvage does not make sense as you can get weapons that are only obtainable through that method, which begs the question of how did anyone get the first ones. I guess they would change the salvaging system once they release PvE.

No matter what they decide on the salvage system I think the stealing of red vehicles should definitely be added as it would provide some form of reward for hacking as right now it just is not worth it. Currently no WP reward for taking enemy vehicle............

This would and could in fact be a form of espionage and as previously stated add more to the metagame.



I, and those who support this proposal, thank you for your support.

I have received word that CCP has taken a look at this concept and have stated its "definitely an interesting idea" so we may see this down the line.

Talk to your CEO, evemail your CPM representative and tweet at your favorite pair of socks and tell them you want this mechanic.

+1

Maybe make it so only SCOUT class can hack these? since the class is completely worthless as is..

I would suggest that BPO should not be salvageable, only the modules or non bpo items on it. Allowing salvage on BPO vehicles would be very exploitable.