So I just played a game where the other Ogryn in our team pulled the Daemonhost, potentially on purpose, maybe not, then ragequits/gets kicked mid death.
This then causes the DH to switch to another teammate. Not cool, intentional or not. Pretty bad behaviour to ragequit if not, absolute scumbag if so. Really bad mechanic if they got DC’d.
This is a bad mechanic for two reasons specifically for people playing on PC:
I dont get to see their account name if they exit the game quick or change character. There is no way for me to tell who it was and so I cant block this person. Recent players only shows account names and doesnt show what character they were playing in my game. I have no way that I know of to identify them (if someone has a way please let me know, thx). When I played on PSN a day or so ago, I could see account names. Why can I not see them on Steam?
Why does the DH even switch if someone ragequits/gets kicked mid-death. Such a bad mechanic and obviously open to abuse. Iv seen this happen a good handful of times now and its actually an annoyingly reliable way to grief a team with a low chance of consequence!
It essentially dooms whoever the unlucky next target is, because 90% of people cannot deal with a DH in my experience, me included.
We won the game, but Im left feeling sour at this potential griefer/rager.
Why is this a thing @FatsharkJulia@FatsharkStrawHat
If you would be so kind as to pass this feedback along I would be most grateful.
(I tagged you both because idk who to tag, apologies)
If the person it’s locked onto alt-f4s then just have it leave and re-aggro if they come back.
Cheezing it is really lame too, but better than griefing an innocent bystander.
Same with triggering DH with barrel and have some poor ogryn get eaten.
wouldn’t that mean if a team of 4 accidentally or overzealously aggros one, a player could abuse this mechanic to save the rest? similar to how people rejoined to get a fresh bot
Yes, I already said this in my earlier reply, but better than 10 cheezy zealots go free than 1 ogryn get eaten, you quoted the “re-aggro” part.
Hel you can have DH auto-kill the cheezer in absentia and they come back in hogtied (to where group can votekick or W/E)
Similar to the witch from L4D that goes back to crying/walking around. The daemonhost should stop aggro and begin to wander slowly on a set path (or random!) which would be absolutely terrifying and hard to deal with, but a good alternatively than what @gpkgpk mentioned on the cheese.
Also, its a daemon, I do not see why it cannot also feast onto chaos cultists.
alt+f4 dh cheesers that dont relog into the match. should be force-spawned next time into a warped psykanium without any other option than not to play, be killed by the spawned host and have a 10%penalty substracted from each of their ressources.
I like the idea of someone rejoining after ALT-F4 cheezing and having a the DH they tried to avoid spawn on them and instantly eat them; karma >cheeze.
Was gonna bring this up as well. I know I’ve seen many a griefer do this sort of BS, had a garbo zealot (it’s always a zealot, why is it always a zealot) that just ran around invis spamming and being away from the team. Ran straight into the deamon host, we where nowhere near him because he wanted that. He fought it down to like 3/4th’s HP then died, then instant alt f4.
Suddenly a host is on my ass and you bet your butt if I wasn’t multiple hundreds of hours past getting Auric Storm Survivor I would have just uninstalled. Thankfully as with this example above I just got roasted then got picked up and the mission continued, but the fact you can do this is actually horse, and the solution is so very very simple.
Just have it re-target the bot. I already know Deamonhosts can target bots as their pathing has activated them sometimes within my games and it’s funny to watch them get demolished. If a host’s target leaves, it’s new target becomes the spawning in bot, or it waits until the bot spawns then targets it.
Swift, easy solution. Then just create a flag on a player that’s ‘targeted by deamon host’, and if it’s true when they leave, if they try and rejoin that game they spawn dead, as if they’d been down. Would prevent the griefer from griefing the rest of the team, prevent them from being ‘rewarded’ as they still ‘die’, and keep the rest of the team from getting punished for a single dude hating on their team mates.
Have the Daemonhost be client specific and tied to the active game state of the person who triggered it. So if they leave a game, it also leaves. But follows them into the next so they still get punished for being dumb.
That way you’d get an added bonus seeing those late joiners appear and then get massacred by a chasing daemon confirming that they are useless lobby hopping fair weather teammates before they even have the chance to do nothing.
People have been doing this alot here lately. One time a guy was streaming apparently trolling in vc which i always have muted and he apparently was pulling daemon hosts and quitting the game a rejoining and I swiftly reported him after the game. There are way too many people currently who will accidentally pull a host and leave out of anger which I find hilarious tbh. Who are you ss a player to think youre too good to wait to be rescued because you accidentally pulled a host? I always just apologize and die if i know we dont have the damage to kill it. Sometimes I rage if I genuinely dont know how it was pulled but I dont ever leave the game thats a bit silly in my opinion.
I’ve recently had a game with British Ogryn who pulled DH, died, then started whining in the voice chat that we didn’t warn him and called us Americans (it was on EU server). Then he left. That was T5 Auric.
