Deimos Bounties using wrong reward tables #1700
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As you can see in the Last Mission Results, I obtained 5 Mother Tokens, having only done the Isolation Vault Tier 1 bounty in that session:

However, it should have rewarded 10 tokens instead:

I also noticed that it used
TierATableARewards
instead ofVaultBountyTierATable${vaultTable}Rewards
, which I'm unsure if it's because the optional objective of the Vault isn't implemented yet or if the bounty making service isn't generating correctly.Isolation Vault Tier 2, meanwhile, rewarded 12 tokens:

Instead of 15:

As well as using
TierCTableARewards
instead ofVaultBountyTierBTable${vaultTable}Rewards
.I presume the issue is that since JobTier for the Isolation Vaults are 0, 1 and (presumably) 2, instead of 7/8/9, the worldStateService is passing the wrong reward data to the server on mission completion.
Deimos Isolation Vault rewarding wrong amount of Mother Tokensto Deimos Bounties using wrong reward tablesI have also realized that the tier 2 Bounties, the level 15-25 non-endless one, use instead the reward table for endless, as the rewards they're meant to give:


Were not the rewards even being rolled:
As those are instead the rewards for Endless:


Endless does indeed possess the non-endless Reward Table.
Isolation vault bounties are unimplemented, so duplicate of #388.
What about the wrong reward tables for the non-Isolation-Vault bounties, specifically the level 15-25 one and the Endless one?
Sounds like the kind of issue that will magically fix itself