Just as the title says. Why Fdev are you allowing people to use the Blocking Feature to block other players that are a threat to them. So many PvPer's are blocking other PvPer's so they are not instanced with them because they are afraid they might die to these other PvPer's. This makes no sense whatsoever to allow people to continue to do this. This has to be considered an "exploit" at the very least. FDEV step up and say something on this and say something on the fact so many people "combat Log" as well. I get comments all the time from people that Combat Log on me saying that FDEV dont care if we Combat Log...FDEV allows Combat Logging ect. These exploits are all too common in the game today!! Please make an Official comment and/or statement on these things!!!
FDEV why are you allowing use of the Blocking Feature to escape possible player threats??
- Thread starter DeathDingo
- Start date
- Status
Not sure what to make of this post. Saltiness from a frustrated griefer or ganker? In any case, you are beating a very, very dead horse here.
Dah da, da da da da, da da da da.
If someone has good reason for wanting another player blocked they should have to provide proof and submit a ticket to support, and support should be doing the blocking. Giving players this ability is not a good way to go about this and thus some people are abusing it and "exploiting' it. I laugh at these players doing this and combat logging, but I also want these "exploiters" to be dealt with.
Blimey! Where to start...?
What is your evidence for this? Even if it is happening, why shouldn't it be allowed?
Why?
Why?
What is your evidence for this? And even if it is happening, FDev have repeatedly said this is not an easy thing to fix.
OK, you must have lots of evidence then. Share it! Show us all those comments you get from players who have combat logged on you.
They have done. Repeatedly. To the extent that it is not worth saying it again for fear of sucking up too much internet bandwidth. If you'd searched the forums for 'Combat Log', you would see countless threads on the subject.
You did check the forums first, didn't you? Because you'd look pretty silly if you didn't.
What is your evidence for this? Even if it is happening, why shouldn't it be allowed?
Why?
Why?
What is your evidence for this? And even if it is happening, FDev have repeatedly said this is not an easy thing to fix.
OK, you must have lots of evidence then. Share it! Show us all those comments you get from players who have combat logged on you.
They have done. Repeatedly. To the extent that it is not worth saying it again for fear of sucking up too much internet bandwidth. If you'd searched the forums for 'Combat Log', you would see countless threads on the subject.
You did check the forums first, didn't you? Because you'd look pretty silly if you didn't.
You're confusing being blocked with some kind of punishment. There is no need for "good reason", proof of anything or Support to get involved. Players are free to block whoever they wish for whatever reason they wish. It's working precisely as intended, and has no ill effect on the player being blocked.
Think of it as analogous to blocking versus punishment here on the forums. If you believed I had broken the rules and should be sanctioned, you hit report, provide an explanation and leave a mod to deal with it. If you just didn't want to see what I have to say, you're free to block me and nobody has any business telling you otherwise.
Last edited:
Yes, Blocking shouldn't stop/reduce instancing with the player but again there can be very good arguments against that. things may change with new C&P system.
Oh Christ, here we go again...
Well known griefer/ganker upset that people arn't forced to be griefed/ganked by them.
My heart bleeds.
Actually does blocking even work like this?
My heart bleeds.
Actually does blocking even work like this?
It would be too easy to write a scarstic comment after reading the OP, so I wont. but come on really.....
But if people dont want to play with other people and use the block list to do it, well good for them. Personaly I just fly solo (most of the time or PG and from time from time in open) and have yet to use the block list for anything, but if I knew some of the names on this forum were indeed the same names in game it would be rather full im sure.
But if people dont want to play with other people and use the block list to do it, well good for them. Personaly I just fly solo (most of the time or PG and from time from time in open) and have yet to use the block list for anything, but if I knew some of the names on this forum were indeed the same names in game it would be rather full im sure.
Last edited:
I think blocking reduces the chance of player A instancing wilth blocked player B. I was queuing at an outpost for the medium landing pad, few players queuing. I came up with the brain wave of blocking the player and re-logging. Tried this several times, and always got back into instance with the player at the outpost. Gave up and used solo. So I think it vastyle reduces not removes instance likelyhood.
In general, I like self policing game mechanisms that do not tie up expensive support resources getting into "He said, she said", or "He ganked me, she ganked me". Tiresome. The blocking mechanism seeems ideal to me. Misunderstanding well, a few players (those in instance) block you, constant anti-social behaviour, well you end up in solo in open. Seems self policing to me.
The hypothetical irony of 2 PvP orientated player groups blocking each other (well all but the kill squadrons), and competing with the BGS for a resource, and then suggesting on the forums that the BGS should be open only has not escaped me.
Simon
Simon
In general, I like self policing game mechanisms that do not tie up expensive support resources getting into "He said, she said", or "He ganked me, she ganked me". Tiresome. The blocking mechanism seeems ideal to me. Misunderstanding well, a few players (those in instance) block you, constant anti-social behaviour, well you end up in solo in open. Seems self policing to me.
The hypothetical irony of 2 PvP orientated player groups blocking each other (well all but the kill squadrons), and competing with the BGS for a resource, and then suggesting on the forums that the BGS should be open only has not escaped me.
Simon
Simon
Because that is exactly what it is for!
Equally I could ask this question and it is valid as yours:
"FDev, why are you allowing players to use lasers to shoot other players"
Is this really a thing now? I've been campaigning for Blocking to work the way the OP describes for a long time. I haven't seen it said officially. I'm leaving it in my sig until I confirm it.
For me I would use it against griefers, but they've been scarce since FDev took their (exploit-acquired) toys away and they rage-quit.
[I have no problems with genuine piracy - I've done it myself and it adds to the game.]
For me I would use it against griefers, but they've been scarce since FDev took their (exploit-acquired) toys away and they rage-quit.
[I have no problems with genuine piracy - I've done it myself and it adds to the game.]
So, basically what we have here is the equivalent of the 7yo at a party that goes around bursting all the other kids' balloons, and then throws a massive hissy-fit/tantrum because none of the other kids want to play with him and he thinks that's 'unfair'.
OP thinks the problem is other players. OP should look a little closer to home.
OP thinks the problem is other players. OP should look a little closer to home.
The block feature is pretty absurd in intended function, which is a strange combination of chat blocking plus instancing prioritization.
It's effect seems to be uncertain enough to just make decent instancing less likely than normal, without actually guaranteeing that someone won't be paired with you, unless multiple people in one instance have blocked someone.
I've blocked habitual combat loggers and still found myself placed in instances with them when it's certain that others were available.
I've also been blocked by CMDRs, then prevented from getting instanced with my own wing. In this case, we were investigating one of the Thargoid structures and I was in the only combat fit vessel in my wing. A pair of hostile CMDRs destroyed an explorer Anaconda that was with me and then decided they didn't like the tactics I was using to fight them (which were entirely legitimate), so blocked me so I couldn't reenter the instance...which left them alone with my other defenseless wingman who couldn't show himself for fear of being annihilated. Thus we we all forced to leave and return, with me entering the area first, so that I got my own instance that my wing could then enter, otherwise they'd enter an instance of hostiles that their protection was excluded from.
Selective instancing is fundamentally incompatible with the idea of an Open mode.
It's effect seems to be uncertain enough to just make decent instancing less likely than normal, without actually guaranteeing that someone won't be paired with you, unless multiple people in one instance have blocked someone.
I've blocked habitual combat loggers and still found myself placed in instances with them when it's certain that others were available.
I've also been blocked by CMDRs, then prevented from getting instanced with my own wing. In this case, we were investigating one of the Thargoid structures and I was in the only combat fit vessel in my wing. A pair of hostile CMDRs destroyed an explorer Anaconda that was with me and then decided they didn't like the tactics I was using to fight them (which were entirely legitimate), so blocked me so I couldn't reenter the instance...which left them alone with my other defenseless wingman who couldn't show himself for fear of being annihilated. Thus we we all forced to leave and return, with me entering the area first, so that I got my own instance that my wing could then enter, otherwise they'd enter an instance of hostiles that their protection was excluded from.
Selective instancing is fundamentally incompatible with the idea of an Open mode.
Last edited:
- Status