DUST Search - A Modest Proposal

Sylwester Dziewiecki wrote:

CCP Blam! wrote:

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.

What if:

1. Enemy infantry gonna hack my HAV.
2. My teammates gonna kill that guy before he manage to recall it.
3. My teammates gonna hack "my" HAV and try to recall it(?)

Whose property will be HAV in that scenario?

My teammates can not simply recall my HAV.
And what if 3 guys is hacking enemy vehicle, who of them will be able to recall it?


Author	Thread Statistics \| Show CCP posts - 2 post(s)
Kaze Eyrou ROGUE SPADES EoN. 234	Posted - 2013.05.20 12:54:00 - [1] - Quote Sylwester Dziewiecki wrote: CCP Blam! wrote: 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. What if: 1. Enemy infantry gonna hack my HAV. 2. My teammates gonna kill that guy before he manage to recall it. 3. My teammates gonna hack "my" HAV and try to recall it(?) Whose property will be HAV in that scenario? My teammates can not simply recall my HAV. And what if 3 guys is hacking enemy vehicle, who of them will be able to recall it? Hmmm.... Maybe if the vehicle "remembers" it's original "owner"? For instance, instead of switching the "owner", have two fields for "owners". One is the person that called in the vehicle, the other is changed depending on the enemy who hacked it. Illustration time: I call in a Sica. That Sica has /owner1/ field as "Kaze Eyrou" and the /owner2/ field is blank or null. Now, I decide to recall it. Because /owner2/ field is blank or null, it refers to /owner1/ field and gives it back to that person. Also note that teammates who recall the vehicle do not switch the /owner1/ or /owner2/ fields, so if they recall it, I get my tank back. Kaze calls in Sica. Sica deployed. Kaze changes mind. Recalls Sica. Goes back into Kaze's inventory. OR Kaze calls in Sica. Sica deployed. Kaze dies because of *overpowered Duvolle Tactical Rifle. However, teammates secure field. Teammate recalls vehicle. Goes back into Kaze's inventory. Now let's say an enemy does hack it. The /owner2/ field will change and if that enemy recalls it, it goes into the enemy's inventory. Kaze calls in Sica. Sica drops on Kaze. Kaze died. Enemy strolls up to Sica and hacks it. When the hack is complete, /owner2/ field is changed from blank or null, to the enemy.* Enemy recalls Sica. Goes into Enemy's 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. What do you think?