Too Many Losses After BGs/Arena #99


  • Defect
  • Enhancement
Open
Assigned to xilcoy
  • Forge_User_07643683 created this issue Feb 26, 2019

    I think I noticed another issue yesterday.

    After I played 4 battlegrounds and later about 8 arena games I got a "score" of 86-64 for that day.
    I definitely didn't die that often. Maybe my own Feign Death counts as a loss in instanced PvP content? 

     

    Everything is fine in WPvP though. 

     

     

  • Forge_User_07643683 added a tag Defect Feb 26, 2019
  • Forge_User_07643683 posted a comment Feb 26, 2019

    Follow up:


    Gonna test it this evening to find out what the problem might/could be.

    Is it possible to turn off the "Stats-Counter" in BGs and Arena? 

    I'm asking because the respective options "talk" about warnings but no stats. 



    Edited Feb 26, 2019
  • xilcoy posted a comment Feb 26, 2019

    Well... I did start counting each player who attacked you within 5 seconds as being lost to. So in a bg if you were being attacked by 10 players just before you died it would record 10 events. Maybe that's what's happening? Before it only recorded the person who most recently touched you.

     

    There's a couple of other ways I could handle this:

    • Change pvp encounters to record multiple names for a single event --hardest
    • Blame the character who caused the most damage --not too bad damage amount is already recorded but it would be inaccurate in some cases, It would probably need a timer to wipe out damage from players you haven't seen in awhile
    • Revert to previous behavior and record player who last touched you --easy
    • Leave new behavior as is --easiest ;-)

    What are your thoughts?

     

    As for disabling the PvP Events, I thought there was already an option to disable in battlegrounds... But it looks like there's only an option for disabling all data gathering, which would disable the warning window as well. I'm guessing you don't want that though. You can manually disable "PvP Data Gathering" for now, but I'll add an option for it.

  • xilcoy posted a comment Feb 27, 2019

    I added a few more options in a PvP log tab of the configuration, and made the default the old behavior.

  • Forge_User_07643683 posted a comment Feb 27, 2019

    Well, ofc I'd prefer the recording of multiple names/chars for an event. ^^

    That would definitelythe most accurate solution in order to keep stats correct. 

    E.g. niw it looks like I already died 5 times in Tiragardesund. Actually it was only twice but killed by multiple Hordes. 

     

    I understand tha this might be the hardest to work out. 

     

    To me it's just important, that numbers of wins and losses are as accurate as possible. 

    It happens very rarely that I get killed and if that happens then usually by multiple enemies.

     

    I like it that I can see (by comparing time of that loss) whether it were multiple enemies when moueovering a map note (if that contains a loss). But to me that is of secondary priority. 

     

     

     

  • xilcoy posted a comment Feb 27, 2019

    Alright I'll see what it takes to do multiple enemies per event. It will probably be a week before I can get to that because I'll be busy this weekend.

     

    For now if you use the latest alpha it should have the old behavior: blame the player with the killing blow. But you have the option to instead blame the player who did the most damage, or record an event for each attacker when you die. You also have the option to disable PvP stats in battlegrounds, arenas, and combat zones.

  • xilcoy self-assigned this issue Feb 27, 2019
  • xilcoy added a tag Enhancement Feb 27, 2019
  • Forge_User_07643683 posted a comment Feb 27, 2019

    Thanks mate!

     

    Ah, and no worries, if one or another thing takes a bit longer. So far you are much, much, much faster as I could've ever expected. 
    Whenever I wanted to try to provide you some log regarding an issue, I saw it already fixed by you. ^^


To post a comment, please login or register a new account.