Page 1 of 1

Bounty Payouts Issue [f]

Posted: 11 Jul 2019, 21:21
by Alexandrea
Twice Bronx was sent to the SR now
and although our charries both took part in at least one of the trips,
Lucyfur, Alexandrea (and Alex's thrall, Kitty)
only received zero amounts for a cut.

eta
from Alex's alert log
07.10.19 You received a $0 bounty share for your part in the death of Bronx.

Subject: The New Bounty System (proposed first draft)
Lucy Fur wrote: I crippled a target but received no reward, and noticed they were still on the bounty list. Wanted dead or alive should indeed just be wanted dead. Someone else decided to finish off the poor crippled target... ouch.
Even after that, I didn’t receive any share of the reward, which may be a bug. Aren’t the rewards supposed to be shared out? (Not any personal bounties on the hit list, just the reward on the Most Wanted list)

Re: Bounty Payouts Issue [?]

Posted: 20 Jul 2019, 11:06
by Azraeth
What was the payout supposed to have been?

Re: Bounty Payouts Issue [?]

Posted: 21 Jul 2019, 00:16
by Alexandrea
1st time killed
Alexandrea wrote:
2: Bronx [Lvl:19]

Wanted Dead or Alive
Notoriety: 50.0
Reward: $57,000 (max today: $57,000)

2nd time killed

Alexandrea wrote:she's back from the SR and already back on top of the most wanted list.


1: Bronx

Wanted Dead or Alive
Notoriety: 33.0
Reward: $37,620 (max today: $37,620)

Image



Re: Bounty Payouts Issue [?]

Posted: 23 Jul 2019, 15:27
by Alexandrea
1h 32m ago: You received a $0 bounty share for your part in the death of Trinidad.

unsure what it was when she went down but when I looked last night it was $54,000

Re: Bounty Payouts Issue [?]

Posted: 23 Jul 2019, 17:12
by Lucy Fur
I can also confirm that $0 bounty has been received

Re: Bounty Payouts Issue [?]

Posted: 25 Jul 2019, 21:23
by Alexandrea
Got a payout on Bronx this time but her bounty was 54,000 and Alex's share was just 5 bucks... O.o lol
but Bronx had been chewed on by Fae out in the wilderness so maybe they all got a cut too

Re: Bounty Payouts Issue [?]

Posted: 02 Aug 2019, 15:57
by Mooncalf
I believe this is fixed, but I've added a debug message just in case this happens again.