This is not a call out... just a screen shot from pvp

I took a look into this and from what I can see using the players in this screenshot:

Adrian is choosing all the battles with the highest VP rewards
ROB17 is choosing all the battles with the lowest VP awards

It does look balanced from the data I could see.
Because if ROB17 chose the harder battles this point gap either wouldn’t exist or would be much more narrow.

I’ve passed on the feedback about the point scaling according to hero level, but right now the big gaps I’ve looked into seem to be caused by the “easy” battles being chosen most of the time by the lower scoring player.

So if the designers do take this feedback into consideration and do tweak it, you’ll probably still see some decent sized point differences just based on the battles being chosen by each player.

I’ll get back to you folks oonce I have any news about this though.
Just wanted to acknowledge the feedback though and let you know I’ve been reading what you’re saying and passing it on

PS. if anyone has some horrendous opponent/VP choices on their opponent selection screen they want to share in relation to this feedback that would be really helpful!

Nope, I checked his PVP data, he has higher options than 50VP battles.

But that’s why the opponent screenshots would be helpful to help me point out the scaling better. I’ve passed this all on without screenshots though as well.

Thank you @Dwuemka !!! this is a great example, I’m including it in my feedback report

Just an update:
It’s possible these discrepencies are unintended (bugged).
The team are looking over it all at the moment and will get back to me once they find out why this discrepency exists.

I try to pass on major issues/feedback like this as quickly as possible while seeking more information. So for example, the screenshot was helpful from Dwuemka because it means I don’t need anyone to run server tests to get the info we need, but I was able to pass on what the community was saying before having this information.

It also means that as a team - if someone on the team sees the report and knows exactly what is happening, it means cutting time to look into it because the information reached someone who knew what part of the code/design to look at.

I will never withold important information from the team, and we continue to gather as much information as necessary after informing them to assist until it’s resolved.

The feedback was:
Higher level players receive far less VP in their opponent selection than players lower level than them and it’s causing a large scoring discrepency.

Everything after that is us investigating details and non-judgementally working out where the discrepency is coming from, with evidence. ie. the Leaderboard screenshots showed what was bothering everyone, but it didn’t tell us what was happening. It was just showing that discrepencies existed - and we still need to find exactly where those are, with evidence.

And you are all super fast so I can ask you for a screenshot, before a designer or programmer can run tests, or check the implementation and design of the feature. So I will always ask for screenshots if it’s easy for you to grab and we always appreciate it!

Having said that the team still need to check the implementation of VP and the live game data now to find out the source of the issue, but the screenshot just helps, because I can show them hey these are the opponents and here is the discrepency on the leaderboard.

Following up on this with the team.
I know they’ve been working on streamlining some stuff which will give us back more time to use on other things, so I’m hoping when that is finalised this will be prioritised more.