over 4 years ago - Kafka - Direct link

I don’t have an update for this yet, I will post when I have news.

over 4 years ago - Kafka - Direct link

Hey just a note to let you know this is still on the table and the team have been looking into it. I’ll let you know if they need any more info thanks for the table!

over 4 years ago - Kafka - Direct link

No news :frowning:
I’ll be poking the team about this again next week (this week is hectic due to update).

We can clearly see there’s obviously a bug but we can’t reproduce it or find the cause yet, needs more investigation.

over 4 years ago - Kafka - Direct link

Here in this thread is faster as I check here every morning/afternoon and other devs check here too.

over 4 years ago - Kafka - Direct link

I do understand, I promise. I’ll follow up with the Devs on this again today. I think I mentioned somewhere this is one of top 5 priority bugs I’ve asked the team to look into, it’s not an easy one so far (which is why it hasn’t been fixed yet).

EDIT: PS. I know how frustrating it would be to read this reply after like 6 months of this, I just don’t know what else I can say at this point :frowning: it’s disappointing all around.

over 4 years ago - Kafka - Direct link

A ticket isn’t necessary thanks @junette

over 4 years ago - Kafka - Direct link

@Karatori please and thank you :slight_smile:

EDIT: please also ask the player if they had any error messages with a “retry” button pop up at all during their Guild Wars matches, if they were playing on mobile while on the move (ie their connection may have temporarily dropped for example).

EDIT EDIT: We still can’t find where these points are leaking out so we’re looking into the possibility of maybe something strange is happening to A battle where the results are somehow partially submitted to the game server so if any guild who gets this issue can find out if members had any weird errors when starting or, probably more relevant, submitting the battle results at the end, please let us know.

about 4 years ago - Kafka - Direct link

We added more logging for this so we could get more information about the issue.
We’re hoping this will help us find an efficient way to solve this issue.

about 4 years ago - Kafka - Direct link

I’m planning on following up with the team on this tomorrow now that we have more data again.
I’ll reply here when I can (but I think tomorrow will be too soon as the team will want time to go over last week’s data and logs).

about 4 years ago - Kafka - Direct link

We’re looking into a potential fix at the moment. I’ll let you know once I have an update.

about 4 years ago - Saltypatra - Direct link

I can confirm that this is still being looked into.

It’s a complex and difficult to pull apart issue that requires the attention of a few developers. Unfortunately this means that there isn’t going to be a quick fix.

We currently don’t have an ETA for said fix, and we are still looking into this when we can.

about 4 years ago - Saltypatra - Direct link

No update. From what I can gather we want to implement a fix first.

over 3 years ago - Kafka - Direct link

Hey, just confirming that the Leaderboards are updated at set intervals, not every time they’re opened.

about 2 years ago - Kafka - Direct link

I’ve followed up with the Dev team again today.

They’re hoping all the server improvements that have been getting made over the past few months will:

  1. Make this bug less likely to occur
  2. Make it easier to fix the bug

We’ve put a different dev on the job so that we have a fresh set of eyes looking at it.
It’s definitely not a simple issue to solve.
I’ve asked if there’s a band aid measure we can take in the meantime - this does carry a risk of further issues so the devs need to look into it more before deciding on a fresh course of action to tackle this bug.

over 1 year ago - Kafka - Direct link

The team have all the info we could find so far about this, if they need anything new that we can’t pull from the logs directly, I will let you all know here.