There are instances of people triggering daemon hosts and immediately leaving - which results in other people getting the daemon host aggro instead. Can we please make it get aggro’d on the bot that replaces them instead? And get them in a killed state when they rejoin.
Speaking of which, can we also please make sure that when someone crashes/disconnects, they come back with the health before they left? Your game crashes and disconnects constantly, so getting bot’s health inherited is a slap in the face. If you wanted to punish “Auric storm survivor” farmers, this will still do that. If they go down, they’ll still be downed. But if I crash my game at full health, I shouldn’t come back dead or on last wound. Make it make sense.
It’s weird. I had this happen on Heresy and it took some time before I realized what had happened. The deamon was not on the path and suddenly it got triggered.
First I thought the person leaving the match was pissed because someone triggered it, but then the person who died stuck around. So here we are, two players and a bot.
Fortunately the replacement player we got was good and after the rescue all went well.
It could have been. Cause the demon is awakened by steps. You can see that with danger zone mod. If someone walks in the danger zone, it will awake the demon. You see the zone coming from green to orange and… after the demon come for the player inside the zone.,
So, 2 players can go through this zone without a problem and the 3rd that enters it, gets the DH that aggro him.
Tested for you yesterday… I did not wait enough to see the danger zone returning to green. And I have got the DH on me.
An other info… the danger zone is reduced when the DH sleeps. If it is awakened, then here the danger zone is bigger.
Not only this, but Psyker’s electro staff and smite can spread to the DH and the DH doesn’t attack the Psyker but someone else, the player was randomly chosen in my experience, so proximity wasn’t the selection factor.
Also, the bot can be targeted by a sniper with a shot triggering the DH.
You dont even have to leave, you can just be closer to the host when it aggroes and now its on you even though someone else woke it up. I had a guy aggro a host yesterday and the host killed me becauseI was closer when it finally woke up. I think the host should only aggro whoever wakes it up but thats not exactly how it works. Its just noobs not realizing where they can spawn and where not to shoot. I find it hilarious people are willing to leave games as opposed to dying and being rescued as if being rescued is the worst thing in the world. I cant imagine being half way through a mission and leaving cuz i aggroed a host.
Still reminding fatshark this issue isn’t fixed, and worse than ever now that newbies are joining in higher difficulties. Starting to lose count due to how common this is now.
I have agro’d some unfortunately. I try to block and dodge. You can last a long time when you dodge sideways at the right time.
But it will eventually get you and if the rest of the team is occupied you’re toast, but I did have occasions when the team managed to kill it before it got me.
I always apologize and remember the spot it camped.
Having the danger zone mod makes it a lot easier to spot.
Danger zone made me realize that there is a mechanic behind DH and that if you enter in the area around you still have few seconds to come back or go forward.
Now, I understand how and why a player can aggro a DH. Unfortunately, you have no time to explain that in a T5 auric mission.