Sylwester Dziewiecki
BetaMax. CRONOS.
72
|
Posted - 2013.05.20 12:11:00 -
[1] - Quote
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?
|
Sylwester Dziewiecki
BetaMax. CRONOS.
75
|
Posted - 2013.05.20 21:13:00 -
[2] - Quote
Kaze Eyrou wrote: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. |