Results 1 to 9 of 9

Threaded View

  1. #5
    Quote Originally Posted by Exploding Fist View Post
    I'm curious because someone used to have that name at some point in time, since it is associated with a player ID.

    The way the player page works is the player name is resolved to the player id, and then the player id is used to pull all achievement data. The server doesn't expect two to be returned, and the first one is used (which is the old one).

    I can fix this, but I'd like to understand the scenario which made it occur since at some point we'll need to revisit the player resolution/cache code (i.e. auto deleting the old player pointer stored). I'm guessing he deleted the old char and made it again.
    I actually encountered this myself, but I did in fact delete and remake the character twice. (pibbies)

    However I never realized I would run into the issue of multi-caching on both recursion and DA for the old playerID which in hind sight makes perfect sense...

    I guess the best way to solve this "problem" would be to have a script run that would "re-nice" the list of player ID's and nicks at some reasonable interval and delete the non-existent legacy cached version and replace it with the one that's actually present on the API.

    Might be something worth taking a look at, maybe grep the player ID/nick association once a week or so, and probably do it in chunks throughout the week so you dont hammer the API with a crap ton of queries all at once...

    Something along the lines of "A-F" on Mondays, "F-K" Tues, etc.

    I personally havnt dug into the API that much, so I dont know how difficult it would be to pull off, but just thought Id throw the idea out there, although Im sure this is a rare enough occurrence that it may not really warrant a "fix"
    Last edited by Pibble; 05-27-2015 at 06:53 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •