These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
123Next pageLast page
 

Ship Replacement Policy Change

First post
Author
Gavascon
need more power inc.
#1 - 2015-08-31 01:02:25 UTC
Where to begin...you lose your ship during combat...
The rules:
1) file a petition
2) CCP will investigate. if the investigation proves there was an error on the CCP side of the server you have a good chance of having your ship replaced.

what is created when a ship is lost?

1) a wreck
2) loot drop
3) salvage
4) insurance payout
5) bounty payouts (if any)
6) skill point loss (if in a strategic cruiser)
7) kill mail

upon reimbursement - replacement - return of ship

1) insurance payout is taken back.
2) ship is put in your hangar LESS the loot drop.
3) skill points are reimbursed.

you receive 3 emails: 1 from the gm informing you they have elected to reimburse, 2nd is from concord informing you "your ship has been salvaged", 3) the insurance company takes back your insurance payout.
CCP will NOT return items that were looted, bounties that were paid or erase/delete/remove the kill mail.

STOP!!!! lets examine the logic for a second.

insurance is paid when a ship is lost. that makes sense.
but, when CCP reimburses - replaces - returns the ship: the insurance payout is taken back.
if insurance is taken back that means: YOUR SHIP WAS NEVER DESTROYED. there's no need for a payout. that makes sense.

but that's where the logic ends on CCP's part. it's a partial solution to a 100% problem.

to get this to a 100% solution the following applies:

if your ship was never destroyed (remember you returned your insurance payout), then:
2) there couldn't have been a loot drop - items dropped need to be returned to the owner, taken from those who took the loot.
3) a wreck was never created - salvage needs to be returned by the salvager
4) bounty payouts never took place - therefore, payouts need to be taken back and restored to the pilot getting reimbursed
5) skill points reimbursed (if a strategic cruiser was lost)
6) lastly, and MOST IMPORTANTLY, the kill mail needs to be erased/deleted/removed because the ship was never lost.

another player would never believe me if i said "my ship was replaced by CCP". why? because reimbursement is rare.
if reimbursement is rare, then go 100% of the way. don't stop part way.

programming creates all the things involved in a ship loss.
programming can remove it when reimbursement occurs.
when a ship is reimbursed, then the attackers will know because the kill mail will be erased.

there have been many changes over the years
this needs to be changed too.

reimbursement = the event never happened.

if you agree, type SIGNED.





JTClone Ares
Deep Space Exploration Corps
#2 - 2015-08-31 01:05:28 UTC
SIGNED
Daerrol
Republic University
Minmatar Republic
#3 - 2015-08-31 01:09:51 UTC  |  Edited by: Daerrol
http://gifsoup.com/view/4570968/cartman-licks-tears.html

This is a relevant and informed response.

EDIT: Your saltyness makes the tears extra delicious
EDIT2: Inb4lock
Tippia
Sunshine and Lollipops
#4 - 2015-08-31 01:11:23 UTC  |  Edited by: Tippia
Nah. That just creates far too many problems for pretty much no gain, and would only ever cause ships to never be reimbursed since the myriad of transactions that will happen cannot be traced or reversed without an insane amount of tinkering that will just annoy everyone involved.

In particular, it seems almost unconscionable to punish other players retroactively just because something bad happened to you.

The current policy works for what it needs to do.
Mr Epeen
It's All About Me
#5 - 2015-08-31 01:18:56 UTC
Or just remove ship replacement under any circumstances. The simple solution is always the best solution.

Type NOFEAR if you agree.

Mr Epeen Cool
Davis TetrisKing
The Vendunari
End of Life
#6 - 2015-08-31 01:37:28 UTC
Gavascon wrote:


STOP!!!! lets examine the logic for a second.

insurance is paid when a ship is lost. that makes sense.
but, when CCP reimburses - replaces - returns the ship: the insurance payout is taken back.
if insurance is taken back that means: YOUR SHIP WAS NEVER DESTROYED. there's no need for a payout. that makes sense.

but that's where the logic ends on CCP's part. it's a partial solution to a 100% problem.



The logic ended when you said "if insurance is taken back that means: YOUR SHIP WAS NEVER DESTROYED.

Your ship was destroyed. I'll repeat that. Your ship WAS destroyed.

Now ii wasn't your fault, so CCP are nice enough that they'll reimburse you the ship. The ship is worth more than the insurance. Think of the replacement ship as the insurance. You don't get both.

Bounty payout is irrelevant. Your bounty pool goes down, someone else gets the isk. The isk for the bounty origionally came from a player, so no isk is generated or lost.

The loot drop part sucks, I can understand that. Here is the only loss I think you can justifiably complain about. It sucks but I can understand it because CCP don't want a net gain from these things as they can potentially be gameable.

The killmail should stay. I suppose it could get flagged as 'reimbursed' or something. In the end though your ship did die.
Brian Harrelstein
Science and Trade Institute
Caldari State
#7 - 2015-08-31 01:42:16 UTC
Gavascon wrote:
Where to begin...you lose your ship during combat...
The rules:
1) file a petition
2) CCP will investigate. if the investigation proves there was an error on the CCP side of the server you have a good chance of having your ship replaced.


do you honestly expect ccp to review every single ship kill manually? they're not going to do that.
Gavascon
need more power inc.
#8 - 2015-08-31 01:50:36 UTC
cup doesn't have to review EVERY ship kill manually. they review losses via the petition system under "combat losses -> replacement". a player has to file (within a certain period of time).
in order for replacement to be valid, there has to be proof of a problem on the ccp side of the server. if not, no reimbursement.
if yes, reimbursement.

it can take several days for the investigation.

Chainsaw Plankton
FaDoyToy
#9 - 2015-08-31 01:51:38 UTC
Tippia wrote:
Nah. That just creates far too many problems for pretty much no gain, and would only ever cause ships to never be reimbursed since the myriad of transactions that will happen cannot be traced or reversed without an insane amount of tinkering that will just annoy everyone involved.

In particular, it seems almost unconscionable to punish other players retroactively just because something bad happened to you.

The current policy works for what it needs to do.

pretty much, in addition if they gave you the mods that dropped as loot they would be potentially duping items

@ChainsawPlankto on twitter

Lykouleon
Noble Sentiments
Second Empire.
#10 - 2015-08-31 01:56:00 UTC
Mr Epeen wrote:
Or just remove ship replacement under any circumstances.

Lykouleon > CYNO ME CLOSER so I can hit them with my sword

Tippia
Sunshine and Lollipops
#11 - 2015-08-31 02:15:05 UTC
Gavascon wrote:
it can take several days for the investigation.

…and in that time, all the things that you want reversed will have changed hands and be propagated through a bajillion intermediaries that will now have their history erased. It's simply unfeasible, on top of being hugely exessive.

How far do you want this history revisionism to expand? Your loss meant someone scooped up your deadspace shield booster — should you get it back because “it never happened” (even though it did)? They sold it on the market for cheap just to get some quick ISK — should that trade be reversed because “he never had that booster” (even though he did)? The buyer used it to run a few dozen missions — should they be reversed because “he also never had that booster” and therefore couldn't run those missions (even though he also did)? He used the income and LP to create a bunch of faction ammo — should the ammo be deleted because “he never actually earned the stuff” (even though he did)? Some of the ammo was sold on the market — should the trade be reversed because “the ammo never existed” (even though it did)? You bought some of that ammo and used it to kill someone — should that kill be reversed because “you never had the ammo” (even though you did)? And that's just a single item from the kill that we're tracing; never mind what happened to the ISK that changed hands at every step of the way (or during the actual kill).

Short of a complete server roll-back, it almost instantly becomes to big to be done at all.


As Davis TetrisKing points out, your idea hinges on the notion that the reimbursed event never happened, even though it did. Since it did, all the follow-on effects also happened, and changing history would mean you have to change all of it or bad stuff will happen. It's not a good idea — hell, even Mr. Epeen's idea of just not allowing reimbursements to begin with is a better solution, and that's saying something — not only because of the absolutely insane effort required by the GMs, but also because it's a system begging for exploitation, fuckups, and value duping. All that for what? Because you're not happy with the compensation?
Gavascon
need more power inc.
#12 - 2015-08-31 02:25:18 UTC  |  Edited by: Gavascon
i love all the responses. all of you are very funny.

let me take a different approach:

there are times when the tranquility server does not function as CCP intended.
when CCP investigates and sees that, CCP "returns" a pilot's ship.

it's not a reimbursement, or replacement. it's the original.
why is it the original? because the server logs say "this never should have happened". as such, no ship was lost (or would have been lost) had the servers functioned as intended.

as for loot drops: returning loot drops is NOT a duplication.
if player A takes 3 modules, then player A has those modules removed from his hangar by CCP (just like the removal of the insurance payout). if player A sells the modules to players B, C, and D, then B, C, D get their money back and the modules are returned to the pilot who's ship dropped them.

bounties are monies put against a player by other players - true. but, those funds are held "in escrow" until payout.
had the servers functioned as intended, the ship would not have been lost and bounty payments would never have been paid.

hypothetical situation:
a pilot is engaged in battle and winning.
suddenly, pop up box.....reads "you lost your connection".....note: the game continues even though you're not there!
you franticly log back into game.....to find, you're in a pod.
file petition -> creates CCP investigation -->> "our server logs indicate there was a problem" (meaning: CCP closed your socket for some reason). result: here's your ship back.
had the connection not been lost, you wouldn't have lost your ship, right?
no loot drop created, right?
no salvage, right?
no insurenace payout, right?
no bounty payments, right?
no skill point loss (if in strategic cruiser), right?
no kill mail, right?

good, now you understand.

the real "tears" that would be created by removing a kill mail are to the ones who did the killing. who, suddenly find they don't have a kill at all.
Tippia
Sunshine and Lollipops
#13 - 2015-08-31 02:51:00 UTC
Gavascon wrote:
it's not a reimbursement, or replacement. it's the original.
why is it the original? because the server logs say "this never should have happened".
…but it did, and so did all the follow-on events, and the original ship is gone. A replacement that avoids duplication is the only option unless you go for a complete roll-back, which is ridiculously excessive for something as small and irrelevant as a ship loss.

The simple fact of the matter is “should” is irrelevant — it did happen. Trying to argue that it didn't leads to broken things.

Quote:
had the connection not been lost, you wouldn't have lost your ship, right?
There's no way of knowing this. All we know is that you lost, and punishing unrelated parties due to counterfactual reasoning is not a constructive (or sane or sensible) way to solve the issue.
Davis TetrisKing
The Vendunari
End of Life
#14 - 2015-08-31 02:57:12 UTC
Gavascon wrote:
i love all the responses. all of you are very funny.

let me take a different approach:

there are times when the tranquility server does not function as CCP intended.
when CCP investigates and sees that, CCP "returns" a pilot's ship.

it's not a reimbursement, or replacement. it's the original.
why is it the original? because the server logs say "this never should have happened". as such, no ship was lost (or would have been lost) had the servers functioned as intended.

as for loot drops: returning loot drops is NOT a duplication.
if player A takes 3 modules, then player A has those modules removed from his hangar by CCP (just like the removal of the insurance payout). if player A sells the modules to players B, C, and D, then B, C, D get their money back and the modules are returned to the pilot who's ship dropped them.

bounties are monies put against a player by other players - true. but, those funds are held "in escrow" until payout.
had the servers functioned as intended, the ship would not have been lost and bounty payments would never have been paid.

hypothetical situation:
a pilot is engaged in battle and winning.
suddenly, pop up box.....reads "you lost your connection".....note: the game continues even though you're not there!
you franticly log back into game.....to find, you're in a pod.
file petition -> creates CCP investigation -->> "our server logs indicate there was a problem" (meaning: CCP closed your socket for some reason). result: here's your ship back.
had the connection not been lost, you wouldn't have lost your ship, right?
no loot drop created, right?
no salvage, right?
no insurenace payout, right?
no bounty payments, right?
no skill point loss (if in strategic cruiser), right?
no kill mail, right?

good, now you understand.

the real "tears" that would be created by removing a kill mail are to the ones who did the killing. who, suddenly find they don't have a kill at all.


Rofl. Nice "in a perfect world" argument.

It's not the original ship. The original ship blew up. "It should never have happened", but it did.

CCP are nice enough to provide a reimbursement system based on what is practical. Replacing the ship is practical. Chasing modules that were lost, looted, fit on new ship, sold, traded, repackaged, reprocessed, blown up on another ship or any other of numerous options is just not practical.

You're also failing to see it from anyone else's point of view but yours. How about my own hypothetical:

Pilot A catchs a ship flying in space.
Pilot A shoots it.
Pilot A loots it.
Pilot A salvages it.
CCP takes away Pilot A's loot, salvage and killmail because apparently part way through the engagement Pilot B DC'd. It wasn't Pilot A's fault that Pilot B's socket closed. Now Pilot A is getting punished for the time spent shooting, looting and salvaging the ship because of a server issue. CCP have created tears for the one who did the killing, Pilot A, even though they did nothing 'wrong'. Why are Pilot A's tears any less important than your own (Pilot B)?

The current system is a lot more fair than the proposal in your original post.
Gavascon
need more power inc.
#15 - 2015-08-31 03:06:06 UTC  |  Edited by: Gavascon
yup, you got it.
pilot a never got the kill mail because pilot b dc'd (but it has to be CCP's fault). maybe pilot b gets away or destroys you in the absence of a disconnect, eh?
if pilot b dc'd because his side lost connection (his internet went out) then the km stands because it can't be verified on CCP's side of the server.

keep in mind: there are 2 sides to this game.
there is our side - CCP is NEVER responsible for what happens on our side of the game.
there's CCP's side - CCP is ALWAYS responsible for what happens on their servers.

i'm not saying tracing loot drops is easy. but it can be done.
Tippia
Sunshine and Lollipops
#16 - 2015-08-31 03:18:14 UTC  |  Edited by: Tippia
Also, if we're going to start to change history based on what “should have happened”, we don't even have to look at that third party to see the problem that notion creates.

You're out flying and come across a bling ship. You engage it, because hey with that loot it'll be worth trying — you're in a T3 and can probably take him. After a long and arduous struggle where you never really seem to have the upper hand, you get a couple of good shots and manoeuvres in so you have the guy locked down tight and soon he's destroyed. Yay! The loot is your and you start flying home to blow it all on hookers and blow faction ammo and exile boosters.


…and then you explode and wake up with less SP in an empty pod with a lossmail on your sheet.

You see, your getting the upper hand was not what “should have happened”, so a GM destroyed your ship and your pod in response to a reimbursement ticket, and also removed the SP you should have lost in your T3 and distributed your fittings to the guy you blew up because it was what he should have earned from the encounter.

Gavascon wrote:
i'm not saying tracing loot drops is easy. but it can be done.
No, it really can't. Even if it could, it would not even remotely be worth the hassle and for such an irrelevant little event, nor should it be done because you'll immediately start punishing people for stuff that they have nothing to do with.
Markus Reese
Deep Core Mining Inc.
Caldari State
#17 - 2015-08-31 03:34:50 UTC
I don't sign.

Reason? Because it is punishing a legitimate player potentially for something beyond their control and possibly even knowledge.

A long time ago, I lost a vulture I used for fleet command when I got hung up in a session change. The two minutes stuck in gate meant that enemy fleet caught up. They saw me, tackled me, blew up my ship and then looted it most likely. T2 battlecruiser, nice salvage.

Yeah, it adds stuff to the system, but in smaller than microscopic amounts. They could take it away from the players who looted me, but what is the point? That player is pissed cause they are on a high note for potentially getting sweet T2 salvage and a nice kill. Let em have it. I am happy I got my ship I lost to server error, they are happy for getting a sweet kill.

To quote Lfod Shi

The ratting itself is PvE. Getting away with it is PvP.

Davis TetrisKing
The Vendunari
End of Life
#18 - 2015-08-31 03:50:26 UTC
Gavascon wrote:
yup, you got it.
pilot a never got the kill mail because pilot b dc'd (but it has to be CCP's fault). maybe pilot b gets away or destroys you in the absence of a disconnect, eh?
if pilot b dc'd because his side lost connection (his internet went out) then the km stands because it can't be verified on CCP's side of the server.

keep in mind: there are 2 sides to this game.
there is our side - CCP is NEVER responsible for what happens on our side of the game.
there's CCP's side - CCP is ALWAYS responsible for what happens on their servers.

i'm not saying tracing loot drops is easy. but it can be done.


Pilot A did get the killmail. Pilot B didn't get away or destroy Pilot A.

"In the absense of a disconnect" who knows what would have happened. Pilot A may have killed Pilot B anyway, Pilot A may have been killed. We don't know. What DID happen was Pilot B's ship got destroyed and Pilot A DID get a killmail.

We can't take it back because it did happen. A person actually experienced destroying the other ship. CCP is responsible and DO make amends for that. They CAN'T erase what happened, so they reimburse the loss to the best of their abilities without making the system exploitable.
Gavascon
need more power inc.
#19 - 2015-08-31 03:56:11 UTC
something similar happened to me out in null a long time ago.
feel bad for ya!

thing is this: you getting hung up in a session change put you at a real disadvantage and your opponents at a real advantage.
an advantage they capitalized upon.

when you filed, CCP saw there was a problem, they granted "reimbursement".

had the session change gone smoothly, you'd have gotten away. no loss mail, no reimbursement.
which is exactly the point i'm trying to make here.
Tippia
Sunshine and Lollipops
#20 - 2015-08-31 04:00:50 UTC
Gavascon wrote:
had the session change gone smoothly, you'd have gotten away. no loss mail, no reimbursement.
which is exactly the point i'm trying to make here.

…and the counter-point is that what happened happened, and can't un-happen because that would break things in spectacular ways for entirely spurious reasons.

So instead, we have the current reimbursement system, which… well… reimburses what can be reimbursed, and that's a far better solution than trying to rewrite history.
123Next pageLast page