Yes. However any comeback retort featuring Lagertha tends to instantly afflict me with the emotional equivalent of male PMS
What to do about Griefers
- Thread starter Cmdr Green Skin
- Start date
PS
Sandro Sammarco:
"Secondly, during any transition where matchmaking is at work (so basically, hyperspace jumps, entering and exiting super cruise) you are much less likely to be matched with the blocked Commander.
Blocking becomes weaker when it comes up against friends (and next year, player wings), because if a blocked Commander is in the same session as a friend (say, because they haven't blocked the Commander, the blocking effect is overruled by the friendship matchmaking.
Outside of this case though, blocking should work fine."
That's the original design. You can find it by clicking on Stigbobs signature which he carries everywhere.
Sandro Sammarco:
"Secondly, during any transition where matchmaking is at work (so basically, hyperspace jumps, entering and exiting super cruise) you are much less likely to be matched with the blocked Commander.
Blocking becomes weaker when it comes up against friends (and next year, player wings), because if a blocked Commander is in the same session as a friend (say, because they haven't blocked the Commander, the blocking effect is overruled by the friendship matchmaking.
Outside of this case though, blocking should work fine."
That's the original design. You can find it by clicking on Stigbobs signature which he carries everywhere.
![[VR] Mad Mike](https://forums-cdn.zaonce.net/data/avatars/m/27/27910.jpg?1553527108){kind=avatar}
The ramming thing is a pain it is clearly an exploit. FD would certainly have a decent system for recognising when a ramming incident was an accident, Vs when it was done intentionaly and have a plausible in-game response if they could. Problem is that sort of thing is hard to pull off. The same griefers would likely find a way to get around what ever system FD put in place, so the result would be inconveniencing 99% of players and still not solve the problem.As long as you are going less than 100ms he gets a fine and bounty, obey the ststion rules and you wont get in trouble
It went through a few iterations.
Originally it was intended to block comms and have an impact on instancing, it was released just blocking comms, then it got added instancing effects overridden by the friends list.
Now it sounds like they've beefed it up to an actual full block of instancing and comms.
Which is probably a good idea.
fair enough. i'd argue high-waking could be used in the same way (possibly even more effective) but ... yeah.
my opinion? menu logging is just obnoxious per-se.
wait and see. what i can see in the patch notes for now doesn't really say much:
it could be irrelevant or it could be that the whole wing is grief-blocked from that instance, how about that?
you can't have a block function without at least some of these drawbacks when more people is involved, not even without malicious intent. this brings me back to my initial point which was not to contradict you but to point out how moot all this is. both menu log and blocking just blur the line where frontier failed to take responsibility of their own decisions and fix their stuff.Mentioning block is always fun.
High waking is vastly slower as it requires much more travel time (than none) to get back.
Sent you a PM as the videos would probably fall under naming and shaming.
Since I play alone and private group I live happily and also socially with other human players, with non-suicidal thoughts, including human players pirate role
We all have our views on what is & isn't an exploit, it's FDev's view that matters.
Play to the rules as they are. Campaign for the rules to be changed by all means, but if you can't 'win' because your opposition is doing something you will not do (play in solo for example, or station camping) then you need to either be better than them, or define a way to 'win' that works to your advantage.
But I also think that anyone playing in a way that means others might not want to instance with them shouldn't be so reliant on instancing for their content.
Play to the rules as they are. Campaign for the rules to be changed by all means, but if you can't 'win' because your opposition is doing something you will not do (play in solo for example, or station camping) then you need to either be better than them, or define a way to 'win' that works to your advantage.
But I also think that anyone playing in a way that means others might not want to instance with them shouldn't be so reliant on instancing for their content.
Everyone should follow their own version of Wheatons law and not really worry about everyone elses.
Robert Maynard
Volunteer Moderator
.... more especially given that a players choice of who not to play with takes precedence over that of those players who rely on other players for their gameplay.
The problem with that is that they cannot avoid your version.
Sounds fairly well absurd that exclusion takes precedent over inclusion in a multiplayer-only game's Open mode.
Robert Maynard
Volunteer Moderator
I was referring, in the first instance, to the very first choice that a player makes when starting a session - which mode to play in.
My mistake then.
Robert Maynard
Volunteer Moderator
Not really - I was using this fact to show the game design that Frontier chose to implement means that players can't demand that other players play with them. This follows in Open as well - with the block feature and the 15-second menu exit.
Its pointless worrying about something you can't change. Plenty more players out there.
Its not a multiplayer only game. Inclusion is the default position in open mode, however inevitably some people simply won't get along so allowing a further specific opt out is the only sensible course really.
I've been referring to players that may want to play with each other, or who would at least be indifferent to it, being excluded from doing so, in some circumstances.
I don't feel I, or anyone else, should have to explicitly opt into contact via friends or wings in Open, to ensure that someone else's block doesn't prevent them from meeting. My friend's list is already getting difficult to manage and I'm perfectly capable of coordinating with people outside of wings. Most Open players depend upon fairly unfettered instancing to meet potential friends and wing members in the first place.
As steenpass mentioned earlier, if block could only exclude the blocker, this wouldn't be an issue, but that's not how block works.
Likewise, there is abuse of menu logging that occurs, not because the one logging doesn't want to encounter these other CMDRs, but because they want to harass them with impunity.
They can detect clogging if its reported I understand, but there have been campaigns to get menu-logging banned by reporting menu-logging to support. This may have downgraded its importance due to support being deliberately flooded with loads of false positives.
There already is a shadow server where persistent cheats/griefers get dumped temporarily and permanently. Some of the people banned there are cloggers based on their own words.
The shadow server means they can play the game but don't effect the BGS at all.
FDEV are too nice to name and shame so you won't see it here and I can't post links. However reddit and elsewhere have examples of cheats groaning about their bans to the shadow server and outright (including cloggers). One individual lost a beta-backer account and over 200 euro's of replacement accounts to a blanket ban across all their accounts.