R67 problems - crashing leaderboards, invisible PvP scores

user311

Some explanations would be appreciated.

It seems like the time slicing has allowed me to see a large range of players such as those that would give me +3 and those that would give +50. Some times I feel nice and dont want to hit a guy whose 1297 (so as not to mess up his progression) and othertimes I might see someone at 875 and hit them so they can retaliate and hit their progression. I think that removing the opp score makes the game more individual-centric and less about the community as a whole. We need those targets to catchup to and brag and give props on.

"Hey Pentagoon, good job on that +35 score. You're really killing it tonight"

GrumpySmurf1002

Pentagoon wrote:

PUBLIC RELATIONS HI-FI DUDE: Why wasn't this in the release notes?

If it turns out to be a bug, it wouldn't be in the notes.

There's a thread in the bugs forum as is: viewtopic.php?f=9&t=20407

Unknown

I'm assuming this is part of R67 patch notes (need formal confirmation tho) :
"..Default starting opponents in Versus play now always report the correct amount of "current points" they have."

Imo, this is a minor issue, coz before patch "opponent score" not representing the actual value, it could display 1100 while the actual could be 2100 or 700.
And we need that "opponent score" to speculate their "current point" that we will received.
Now we don't need to speculate, coz the "current points" dynamically changed and reflect the actual value. So what's the problem?

Before :

After defensive wins :

Ebolamonkey84

tobi69 wrote:

I'm assuming this is part of R67 patch notes (need formal confirmation tho) :
"..Default starting opponents in Versus play now always report the correct amount of "current points" they have."

Imo, this is a minor issue, coz before patch "opponent score" not representing the actual value, it could display 1100 while the actual could be 2100 or 700.
And we need that "opponent score" to speculate their "current point" that we will received.
Now we don't need to speculate, coz the "current points" dynamically changed and reflect the actual value. So what's the problem?

The current points have not been accurate for me. An alliance mate ended up in one of my nodes worth 19 points. I checked his score from the leaderboard and it was actual 70 points higher than mine, so he should have been in the high 20s at least.

Unknown

If the points you win is actually accurate to within say the last 5 minutes this is much better than before since most of the time the 'current score' of your opponent is something that has no relation to reality anyway. Not sure why they decided to get rid of it, but the current score was never that useful due to how far it lags behind your opponent's real score.

MarvelMan

Im pretty sure the next change will be to remove the points you will win from the match screen. We'll just get a random number added to our score after each battle.

At least that will fix the issue of skipping match after match after match that is worth 10 points.....

Unknown

MarvelMan wrote:

Im pretty sure the next change will be to remove the points you will win from the match screen. We'll just get a random number added to our score after each battle.

At least that will fix the issue of skipping match after match after match that is worth 10 points.....

Change the points to an indicator of trivial, easy, normal, hard, and deadly!

Unknown

@Penta, Just notice, this changes indeed a head shot to "Battle Chat".
It seems that devs, technically know how "it" works.
Embrace it,, what else can we do.

Pentagoon

GrumpySmurf1002 wrote:

Pentagoon wrote:

PUBLIC RELATIONS HI-FI DUDE: Why wasn't this in the release notes?

If it turns out to be a bug, it wouldn't be in the notes.

There's a thread in the bugs forum as is: viewtopic.php?f=9&t=20407

Thanks GrumpySmurf - I missed it while scanning the posts in the support forum. Very helpful.

Pentagoon

I started a separate thread on general chat about the missing PVP scores. I don't think this is a bug until a developer confirms that it is. I'm getting more pissed about it the higher I get in my bracket today.

viewtopic.php?f=7&t=20467

FaustianDeal

Its possible the 'score' was removed because there is a deeper change going on here that wasn't as well communicated. I think the release notes only indicate that you will see the correct amount of current 'points'... which could now be different than the enemy team's current 'score'. I'm wondering if this is a subtle change so that the point values you are awarded are going to be locked in when that enemy team is loaded, regardless of how they move between being loaded and being hit? (Possibly an attempt to reduce network load by skipping the back-forth to adjust points?)

This could also be a funky way to attempt to address ongoing complaints about points lost during ladders, since someone who slotted an X-Man into a node 800 points ago can't cripple them for 50 much later in an event?

Has anyone left a node long enough to see if points change? Or has anyone coordinated an unshielded attack after R67 to see if the points awarded/deducted have been fiddled with too?

Accident-eLe

Seed teams still don't acurrately reflect pts....so nice update

Unknown

I was going to say this was a pointless change..............but that seemed a bit lame

Anyway unless I missed something this is simply a more opaque version of the current system. I might know that a 30 point target neans the server thinks they are 70 points higher than me but many won't. And the actual points awarded for a win seem to depend on up to date scores as now so may be distinctly different to what the screen shows.

Beast1970

To update the crash bug, it is acting different than the last leaderboard bug. I had the leaderboard open in Trial by Combat when it ended, and that caused a game crash from inside. The workaround of taking screenshots at the event end won't work this time to track scores for your alliance.

Dayv

My Trial By Combat time slice has ended, and I can view the scores for it without crashing. It will be interesting to see if this changes when the last time slice ends.

y2fitzy

I'm having the crashing problem too, Nexus 5

Pwuz_

DayvBang wrote:

My Trial By Combat time slice has ended, and I can view the scores for it without crashing. It will be interesting to see if this changes when the last time slice ends.

Must be nice. Mine crashes as soon as I try to access the page for Trial by Combat.

Unknown

Pwuz_ wrote:

DayvBang wrote:

My Trial By Combat time slice has ended, and I can view the scores for it without crashing. It will be interesting to see if this changes when the last time slice ends.

Must be nice. Mine crashes as soon as I try to access the page for Trial by Combat.

Same.. first time its ever happened to me, hope its the last

Unknown

Crashing here too when I try to view past event. Galaxy Note 2014, Android 4.4.2.

chris0001

Crashing in middle of match for me, Trial by Combat....Which equals a loss! For an update with several bugs I'm very suprised they actuall forced the update! IT crashed several times on me last night...