<!-- [if gte mso 9]> <![endif]-->
<!-- [if gte mso 9]> Normal 0 false false false EN-US X-NONE X-NONE <![endif]--><!-- [if gte mso 9]> <![endif]--><!-- [if gte mso 10]><![endif]-->
I have an issue with multiple toons with the same names on our character roster. I think it may be related to those who claim a character being different from the one that imports from armory. For the most part this is not a big issue, I will just have character bloat and the occasional question from members as to why they have multiple characters with the same exact name tied to their member account. However, when these multiple accounts are tied to raider characters in the rapid raid system it presents a problem. And it is very annoying.
I will list these multiples below, hoping that will help resolve the issue. And, yes, I can remove one, but if it’s the armory one, it of course comes right back when you scan the armory. I cannot tell which of the duplicate toons are the armory imports, and which did not originate from the armory.
As far as the Rapid Raid is involved, if I remove the “wrong” one, then he receives no dkp from the events. And I don’t know which the wrong one is because I cannot see his character ID from the Rapid Raid system. I can only see it when I hover over the character names in the Roster menu. If I leave the multiple toons with the same name in the Rapid Raid system, I end up with 2 toons with the same name carrying DKP. This distorts dkp, obviously. I can mark one as Raid In-Eligible, but if I mark the wrong one (and I have no clue which is the “wrong” one), then the character does not show up in the rapid raid system and he earns no dkp. I have at times left the multiples in and then each night go to the merge dkp menu in Rapid Raid and just transfer all the dkp from multiple characters with the same names to ONE character with the same name. But this is tedious and I should not have to operate this way. I compound the problem when I have to make a manual adjustment to the toon or add him/her manually into an event. Which one should I adjust? I have no clue because the character IDs are not visible from the rapid raid menus.
There should not be multiple toons with the same name and different character IDs in my roster. How do I fix this problem? It is ESPECIALLY irritating when the character is involved in our rapid raid system.
Allerianna ID 19993644 level 100
Allerianna ID 19857271 level 100
Ayaname ID 19993643 level 100
Ayaname ID 19823554 level 100
Bettercruci ID 19881450 level 96
Bettercruci ID 19993645 level 100
Cajunblade ID 19640492 level 100
Cajunblade ID 19627086 level 100
Cajunspices ID 19996846 level 97
Cajunspices ID 19780751 level 97
Danreb ID 19915988 level 100
Danreb ID 19935981 level 100
Draea ID 19915989 level 100
Draea ID 19898254 level 100
Georg ID 19738932 level 100
Georg ID 19996845 level 100
Nanonoko ID 19935972 level 26
Nanonoko ID 19988326 level 26
Pewpewpwn ID 19996847 level 93
Pewpewpwn ID 19800949 level 93
Teodora ID 19837605 level 100 – this is the toon in Rapid Raid
Teodora ID 20010374 level 100 – this one I have marked as raid in-eligible
Whowhos ID 19861793 level 100
Whowhos ID 19857272 level 100
I hope we can resolve this issue. Maybe it’s as simple as me having some setting wrong. I have not had this issue in the past. I think only since WoD. Let me know if I can provide any further information.
Again, I do not know why there is script at the top of the post. When I go into edit mode it is not there, so it’s not something I can remove. I have copied/pasted this thread from Word.
It's most likely code that Word adds in - don't copy and paste from Word, or if you do CTRL+Shift+V instead of CTRL+V to strip out the formatting as you paste.
Well that was too much to simply type into here; I figured I'd have too much editing!
The toons were not added manually.
Well, if I merge dkp from the armory ID to the non-armory ID and remove the armory ID, it comes right back into the roster via the armory scan. If i merge dkp into the armory ID and remove the non-armory ID, then it does not come back. But in the case of Teodora, rapid raid becomes "confused" and he loses his dkp and no longer imports correctly. It's as though rapid raid has internally chosen one of his IDs to track and my confusion arises because I'm not sure which one to recognize as the "proper" one.
If this cannot be resolved, simply allowing me to see all IDs from the rapid raid lists would help me to ensure I always use the ID Rapid Raid acknowledges.
This is the tracker from last night with Teodora as Ebbie is trying to explain above.
GL-1.0v6.23Greymane014242231751424236157Blackrock FoundrySieferrDodickieLellJunsingArlaynaEleanneTalirXelrielArigatoGunjahTeodora-TanarisSmidgettéVanikaRastsanctusCryandisAllagashRaganarStormhawkeAdiynJuliseZâeryLokeyJibbelzCasomorMeteorzCaroleJinnGruulRaid TrackerJuliseLellArigatoAllagashSmidgettéJunsingCaroleVanikaRaganarRastsanctusJinnXelrielMeteorzCryandisSieferrTeodora-TanarisAdiynZâeryDodickieLokeyGunjahEleanneArlaynaTalirCasomorStormhawkeJibbelzHans'gar and FranzokRaid TrackerJuliseLellArigatoAllagashSmidgettéJunsingCaroleVanikaRaganarRastsanctusJinnXelrielMeteorzCryandisJibbelzTeodora-TanarisAdiynZâeryDodickieLokeyGunjahEleanneCasomorArlaynaStormhawkeTalirJuliseRaganarJunsingAllagashSmidgettéArigatoGunjahVanikaLellRastsanctusStormhawkeArlaynaMeteorzCryandisSieferrTeodora-TanarisAdiynCasomorDodickieLokeyCaroleEleanneJibbelzXelrielTalirZâeryJinnCryandisAllagashLellDodickieZâeryArlaynaDodickieCryandisLellAllagashZâeryArlaynaDodickieSieferrVanikaJinnJunsingDodickieLokeyArlaynaCryandisCasomorXelrielTalirAllagashRastsanctusCaroleAdiynArigatoStormhawkeGunjahJuliseDodickieDodickieLellEleanneXelrielTeodora-TanarisSmidgettéZâeryRaganarLokeyJibbelzMeteorzDoomslag GreatbootsRaid Tracker119341:0:0:0:0:0:0:0:100:0:5:2:564:566INV_Plate_RaidWarrior_O_01Boots.blpArmorPlateffa335ee1ZâeryBlackrock FoundryTrash mobFlare-Eyed HoodRaid Tracker113868:0:0:0:0:0:0:0:100:0:5:2:561:566INV_Helm_Cloth_RaidMage_O_01.blpArmorClothffa335ee1Jinn180Blackrock FoundryGruulFlare-Eyed HoodRaid Tracker113868:0:0:0:0:0:0:0:100:0:5:1:566INV_Helm_Cloth_RaidMage_O_01.blpArmorClothffa335ee1Allagash70Blackrock FoundryGruulVest of Forceful FuryRaid Tracker113870:0:0:0:0:0:0:0:100:0:5:2:561:566INV_Leather_RaidDruid_O_01Chest.BLPArmorLeatherffa335ee1Talir82Blackrock FoundryGruulVest of Forceful FuryRaid Tracker113870:0:0:0:0:0:0:0:100:0:5:1:566INV_Leather_RaidDruid_O_01Chest.BLPArmorLeatherffa335ee1Eleanne40Blackrock FoundryGruulGruul's Lip RingRaid Tracker113872:0:0:0:0:0:0:0:100:0:5:1:566INV_6_0Raid_Necklace_1d.blpArmorMiscellaneousffa335ee1Dodickie83Blackrock FoundryGruulPhosphorescent SealRaid Tracker113866:0:0:0:0:0:0:0:100:0:5:1:566INV_Ringwod_D3_1.blpArmorMiscellaneousffa335ee1Zâery100Blackrock FoundryGruulGirdle of Unconquered GloryRaid Tracker113907:0:0:0:0:0:0:0:100:0:5:1:566INV_Leather_RaidMonk_O_01Belt.blpArmorLeatherffa335ee1Eleanne40Blackrock FoundryHans'gar and FranzokVertebrae ProtectorRaid Tracker113900:0:0:0:0:0:0:0:100:0:5:1:566INV_6_0Raid_Necklace_2d.blpArmorMiscellaneousffa335ee1Arlayna40Blackrock FoundryHans'gar and FranzokNeckbreaker ShoulderguardsRaid Tracker113899:0:0:0:0:0:0:0:100:0:5:1:566INV_Shoulder_Mail_RaidShaman_O_01.blpArmorMailffa335ee1Gunjah60Blackrock FoundryHans'gar and FranzokTablet of Turnbuckle TeamworkRaid Tracker113905:0:0:0:0:0:0:0:100:0:5:1:566Inv_misc_trinket6oIH_orb4.blpArmorMiscellaneousffa335ee1Smidgetté40Blackrock FoundryHans'gar and FranzokHardened GreathelmRaid Tracker113910:0:0:0:0:0:0:0:100:0:5:1:566INV_Helm_Plate_RaidPaladin_O_01.blpArmorPlateffa335ee1Smidgetté110Blackrock FoundryHans'gar and FranzokFranzok's HeadsmasherRaid Tracker113904:0:0:0:0:0:0:0:100:0:5:2:561:566INV_Mace_1h_DraenorRaid_D_04Purple.blpWeaponOne-Handed Macesffa335ee1Raganar219Blackrock FoundryHans'gar and Franzok
I have determined the fix for this issue. The issue is a result of connected realms. For the example above, the server Greymane and Tanaris are connected.
What has happened is the new duplicate characters that are created are a result of our new code that takes into account what server the character is actually on. Before, if the character was not from your main site server, it would just assign them with your main sites server. Now, if they are not a member of your main site server, they are created with their actual home server. So, the new duplicate characters are set to the correct server while old are not.
What you can do to fix this is fairly simple.
1.Users Need To:
1. Users need to go to their oldest character (Check the character IDs in the URLS to tell which are oldest, the lower the number the older the character)
2. Check which server the character is set too.
3. Fix the server, it needs to be their actual server, not the guilds server.
2. The Admin Needs To:
1. Merge the NEW character into the OLD character
2. Remove the NEW character from your roster.
This way, when you import your next raid, all of your cross-realm members will be found and imported correctly rather than the system thinking they don't exist and creating new characters. The easiest way for you to tell which characters are new and which are old is to take a look at their character ID's. The lower the character ID, the older that character is.