789 - Player can become ungrouped combatant
What steps will reproduce the problem?
1. Unknown
What is the expected output? What do you see instead?
The player him/herself should always be of combatant type "Self". Somehow, however, my main character ended up in the dbCombatants database (if that database is character specific: his own dbCombatants database) as type "Ungrouped". Presumably a timing error is going on, here.
What version of the product are you using?
5.0.5a
Do you have an error log of what happened?
N/A
Please provide any additional information below.
Proposed solution: add the player him/herself to Recount:GroupCheck to force the player to always be of type "Self".
| User | When | Change |
|---|---|---|
| CMTitan | Oct 29, 2012 at 16:17 UTC | Create |
- 1 comment
- 1 comment
- Reply
- #1
CMTitan Nov 04, 2012 at 11:51 UTC - 0 likesThis has happened to me again, this time while doing some scenarios with a guild-mate: first scenario I was in my own group, second scenario I no longer showed up. This suggests more than just timing is going on. Two possibilities come to my mind: 1) scenarios playing tricks on the group detection (not sure how, though) or 2) the introduced separation of group and instance group being the culprit.
Either way, the proposed solution will probably fix it by effectively working around these issues.