Spent a few days on the Testlive near Asagard (EU1, I built a base on the top of one of the ribs) and I raided Asagard maybe 15 or so times in total and no Battleborn (or any other named thrall) spawn.
Is this intentional?
Has anybody else seen them?
Is the bugged spawn fixed?
Didnt find him but I noticed that armorers III spawn among the settlements nearby, I suspect t4 could also spawn there.
I’ve gotten Beri (Blacksmith) and Janos (twice) from Aasgarth so far… what’s weird is they just pop out of the huts and come running at you – they’re not in plain sight. It’s almost as if they don’t exist until you get near the spawn point and then pop there they both were for me. Janos shouldn’t even be there – he should be at the Wardtowers normally… idk.
He is one of the bugged Thralls.
It is documented here on how to fix it
I also created 3 mods before that posting that fixed his spawn, among others, like this mod here. So I know that forum posting is indeed correct on how to fix it.
Finally, I documented my findings to the devs in the mod discord and have provided my .csv to be publicly available on my mod pages. Anyhoo, just thought I would drop that bit of info off.
Janos has multiple spawn points, Wardtowers, Meadow Watch, Lian’s Watch and New Asagarth.
I’ve personally gotten him from Lian’s Watch and New Asagarth.
Yeah, great work, I was trying to find out if Funcom had fixed that bug or not. I’m thinking about buying the DLC so this is determinative for me, is Funcom the kind of developer that can fix stuff like that or not? It’s an easy fix and it unlocks a significant piece of content (six sets of flawless armour). Vital for any collector and anybody wanting to fight and run and climb in the cold.
Yes? I’m a little confused by this statement. After developing the game from the ground up to where it is now for over 2 years (a year and a half in EA and post release), you are wondering if Funcom is capable of fixing a couple of small mistakes in a data table?
I did what I could about spreading the word. Funcom has a lot on their plate, I’m sure when they have the time to test my suggestions (after all, I am just an amateur modder, I would take my own game development advice cautiously too), they will. There is a lot more that I can’t see that goes on besides those data tables (such as the actual spawn point and other factors), something that is perceived to be simple could very well be more complicated due to factors I can’t see (whether because of coding, or because of lack of experience).
What I mean by that is not “can a coder fix this”, what I mean is “is FunCom the kind of organization which can identify and fix problems like this as they emerge.” This bug has been in the game for a while, at least two hotfixes/patches worth of time and this bug has been identified ever since I got the game. It’s an easy fix, resolves a big problem (flawless vanir armors not being available).
Basically, before the TestLive the status of the bug was “fixed internally”, then the TestLive seems to not have fixed the bug. I don’t know how or where to look to see if the syntax has been fixed in the csv so I ran into asagard to try and get him since I wanted to at least have had it once, since I can’t get it in the regular game. I ran into a couple of Janos’, Thunderheads (the tanner) and a few named Taskmasters in the villages OUTSIDE asagard, but nothing IN asagard.
Yeah like he said, they’ve got alot on their plate now. Im not a fanboy but this game was digging a grave a year ago and now poof. Im not sure they were prepared for the explosion. Just my two centavos.
It’s nearly impossible for a game developer to find and fix all issues on their own. I know that as a mod author, I heavily rely on feedback to find bugs. There is absolutely no way I could get my mods to the way they are without feedback. Outside of that, Funcom’s devs are probably swamped with trying to get new test live builds out with a gazillion different fixes in them to get further feedback on. Fixed internally versus a testlive build are often and almost always different. Testlive they are testing for very specific things, and what is on test live now may or may not include everything that will be there in a future patch.
The bug has been reported, scouted, and an in-depth analysis by myself and the forum poster have been provided. I’ll let them take it from here when they are able to provide quality internal testing and fixing.