Original Post — Direct link

Playing on Xbox Series X and I finally built the barracks at my new village in England and I noticed a glitch with Jomsviking recruitment.

Every, and I mean EVERY Jomsviking that shows up for recruitment has the exact same gamer tag, CachouMTL, associated to it. I have recruited recruited six Jomsvikings at this point across multiple days and all of them ended up in my barracks as available crewmates and then show what the correct gamer tag they belong too. This has zero effect on the next Jomsviking that shows up as the gamertag is again the same. I can also verify that this gamertag CachouMTL is not a player I am a friend with but some random player unconnected to me on Ubisoft or Xbox. This is EXTREMELY annoying as I am hoping to find my friends Jomsviking some day.

I know getting a Friends Jomsviking is random, and it SHOULDN'T be, but now I have no way to know if a friends Jonsviking has shown up unless I spend the silver to recruit them and see where they show up in my barracks. After all I assume the pre-generated names are not unique to us so my Jomsvikings name is probably out there 1000 times.

over 3 years ago - UbiKobold - Direct link

Greetings, and I am very sorry for the late response. The Game team was also able to reproduce this issue and has been working towards a fix for a future update. Please keep an eye out for further updates regarding this, and thank you all for your continued patience!

over 3 years ago - Ubi-Wan - Direct link

Hey all! I'm sorry to hear the issue persists. We're still looking into the cause of this issue, however we're curious of a few things. We've seen reports that once recruited, the names of these Jomsviking's origins update to the actual player who uses them, as in this is mostly a visual error. I'd like to know if that's consistent to today? A few players have reported restarting the game, or waiting some time whilst checking before/after recruitment may resolve the issue.

about 3 years ago - Ubi-Wan - Direct link

@Lady_Phantom40 - Thank you for providing this workaround! We'll be sure to add this information to the report.