Moris are great but survivors dodging them aren't
I bring moris every match I play as killer. They spice up the game allowing me to enjoy killer more. Survivors can disconnect in the loading screen and stop the match forcing all of us to go back to the lobby. It's a waste of time.
Survivors and killers should receive a disconnect penalty if they leave like this. They can bring offerings to sway the match and I don't leave. I do the same but they leave. Plus there are 4 of their offerings to my 1. It's a way to disrupt the game.
Comments
-
There's no real way to say if it crashed or was just canceled by the taskmanager, maybe it wasn't even the internet that was just gone for a moment, so they can't and won't punish them for that.
That being said I don't dodge games like that and I never use moris, so that's a problem I can't tell how often that happens.
3 -
lmao every time I bring a mori during twisted masquerade atleast 1 person dc
0 -
Free win tech? 😏
1 -
almost as if people want to get BP. Look at surv points, they need all the BP offerings they can get.
4 -
You should not expect that people will stay if you dont bring an Event Offering as Killer during the event. Survivor Queues are basically instant, they dont really lose much when quitting in Loading Screen.
And from my experience, if a Killer does not bring an Event Offering, this Killer is usually very sweaty and not fun to play against at all, since they are the kind of person to not bring an Event Offering because Survivors would benefit from them, while enjoying to see 4 Offerings on the Survivor Side.
You will most likely get less DCs in Loading Screen after the event is over.
8 -
I was disconnected during loading due to my comp crashed (for some reason only on DBs) few times in a row. How can you decide if one disconnected because of offering, or had other problem?
Btw. You are not loosing offerings if someone disconnect during login
0 -
Straw men arguments.
0 -
Did you just see other people use that word but never really knew what it meant? Because by the way you use it here that seems to be the case... So let's go over those posts and see if you are correct...
- Questions how often the issue happens in general so that there might not necessarily be a reason to act if the issue happens not often as well as how to prevent it from a technical standpoint without punishing players that don't fall under that category. Both of them seem to valid arguments against your standpoint.
- Kind of agrees with you, so I guess this one is excluded, however does not provide anything but their own experience.
- Ironic/humorous comment that does not provide anything of value for the conversation.
- Ironic comment about possible reasons as to why people DC. While it may be a possible cause we cannot be for sure, however from a logical standpoint it seems reasonable to assume that, we would need to have a comparison to before or after the event to know for sure. But it is still on topic and therefore fine.
- Basically going into detail about the before presented argument for it being tied to the event currently and player expectation based on offerings... Reasonable given a mori or strong map offering usually imply people wanting to win.
- Basically reffering to statement 1 that from a technical standpoint it might be rough to not also impact players you don't want to impact. As well as a reason why the issue might be non issue, basically you don't lose much and not every team will DC on you for that, so while it might be an inconvenience it might not be too bad.
So overall I would say your statement is false. While they did not agree with you, they showed why your idea might be
a. Problematic from a technical standpoint because it also potentially influences players it is not supposed to influence.
b. Linked to the event, so only be a temporary issue.
So I fail to see where the strawmen arguments are, they explained why your idea is problematic without necessarily ignoring your arguments.
1 -
Its like bringing that one dish no one likes to a party and wondering why no one ate it.
3
