Ignoring or harming PvP in game design is contributing to ganking

Depends of viewpoint of attacked. To me that kind of behauviour leads to getting added to block list.

One of the reasons I think putting blocking tools in the hands of players was foolish.

If you play in Open, you may well have crapped up my instancing while retaliating against someone else for entirely legitimate play you simply didn't care to understand.
 
Another difference was that the player could reload from any stored save game at any time, only losing the progress since the last load.
Yes, but you couldn't make a career of it since you had to reload. Nowadays, all you lose is the rebuy of a ship which, with the current meta (and by "current", I mean "God knows how many years now", means three minutes of running a delivery mission..
 
One of the reasons I think putting blocking tools in the hands of players was foolish.

If you play in Open, you may well have crapped up my instancing while retaliating against someone else for entirely legitimate play you simply didn't care to understand.

When you log into open you are accepting the fact that you can be Blocked at anytime, by anyone. If you can't handle that fact, play in Solo, or start your own PG with 'no blocking' rules.
 

Deleted member 121570

D
One of the reasons I think putting blocking tools in the hands of players was foolish.

If you play in Open, you may well have crapped up my instancing while retaliating against someone else for entirely legitimate play you simply didn't care to understand.

Or they could have crapped up your instancing for blocking someone they just didn't want to play with, regardless of any perceived legitimacy or not of whatever gameplay.

Seems to me that blocking as a concept is just fine. Instancing is where the crap lies.
 
Yes, but you couldn't make a career of it since you had to reload. Nowadays, all you lose is the rebuy of a ship which, with the current meta (and by "current", I mean "God knows how many years now", means three minutes of running a delivery mission..
Really?
How many delivery missions can pay 45 million in 3 minutes? I'm obviously in the wrong systems!
 
Blocking should be available for … 'social interactions', but not affect instancing at all.

If you log into open you agree to everything ED offers, including PvP. It you daon't want to, join a non-PvP Group.
 
While one Dev has indicated that a majority of players play in Open (with Solo and Private Groups both having "significant portions" of the player-base), another Dev has indicated that Frontier are "well aware" that the majority of players don't get involved in PvP.
You say Fdev have "indicated ther is more players in Open" but do not stipulate when. Are there recent published evidence of this?
 
Or they could have crapped up your instancing for blocking someone they just didn't want to play with, regardless of any perceived legitimacy or not of whatever gameplay.

Seems to me that blocking as a concept is just fine. Instancing is where the crap lies.

Crapping up my instancing, for any reason, is not just fine.

This is a multiplayer game, and in Open, a direct one. Allowing one player to arbitrarily and unilaterally exclude others from their CMDR's instance, which may include many other CMDRs who have no issues at all with the individual being excluded, is the the only way a block could work, and is pretty crappy in conception.

If you don't want to play with someone who isn't breaking any of the game's rules, you should keep your CMDR out of Open, not take it upon yourself to tell me who I can and cannot encounter while your CMDR is around.
 
One of the reasons I think putting blocking tools in the hands of players was foolish.

If you play in Open, you may well have crapped up my instancing while retaliating against someone else for entirely legitimate play you simply didn't care to understand.
All I see is unprovoked attack, it is not my duty to find out reason of such behauviour. If one does not take time even for issuing one liner comms, well its their problem. Not mine.
 
All I see is unprovoked attack, it is not my duty to find out reason of such behauviour. If one does not take time even for issuing one liner comms, well its their problem. Not mine.

An you make it a lot of other people's problem too, even if they have never interacted with your CMDR.
 
When you log into open you are accepting the fact that you can be Blocked at anytime, by anyone. If you can't handle that fact, play in Solo, or start your own PG with 'no blocking' rules.
You arr absolutely right. We all have to accept the rules of the game, whether we like them or not. I'd kindly ask anyone to think twice before blocking though and not just block someone for "ganking" in open as it will mess with third parties also.
 

Robert Maynard

Volunteer Moderator
I'd kindly ask anyone to think twice before blocking though and not just block someone for "ganking" in open as it will mess with third parties also.
Yet the players doing the "ganking" aren't expected to think twice about what they do as them being blocked may mess with third parties too?
 

Robert Maynard

Volunteer Moderator
Blocking should be available for … 'social interactions', but not affect instancing at all.
It's Frontier's choice that the block feature blocks instancing (and it has only ever been strengthened and made easier to use over time), just as it was Frontier's choice to permit each player to shoot at anything they instance with.
If you log into open you agree to everything ED offers, including PvP. It you daon't want to, join a non-PvP Group.
Which includes menu exit and the block feature - as there are no limitations on their use.
 
Everyone has as much right to block anyone, as gankers has right to attack anyone. So whats the problem? Okay I'm all up to restricting blocking function if we also put PVP flag policy in open. Happy?
 
Choose better associates than gankers and such and you have no problems.

No one has to be an associate of those you've blocked for them to be negatively impacted by your decision, nor is it your place to tell anyone who they should or should not associate with.

Indeed, if they were an associate, chances are their friending of that CMDR would outweigh your block. However, in the case of those not on a friends list, your block could easily exclude them. I should not have to friend everyone in the game to have a fair shot at encountering them. There are plenty of CMDRs I do not want on my CMDRs friends list that I am entirely happy to encounter should they find themselves in the same place at the same time.

The problem is being instanced with CMDRs played by people like yourself, who do not care that they crap up other people's game, and the existence of mechanisms that give them control over other players.

It's Frontier's choice that the block feature blocks instancing (and it has only ever been strengthened and made easier to use over time), just as it was Frontier's choice to permit each player to shoot at anything they instance with.

Which includes menu exit and the block feature - as there are no limitations on their use.

None of this is in dispute.

It's still a bad system subject to considerable abuse.
 

Deleted member 121570

D
Crapping up my instancing, for any reason, is not just fine.

This is a multiplayer game, and in Open, a direct one. Allowing one player to arbitrarily and unilaterally exclude others from their CMDR's instance, which may include many other CMDRs who have no issues at all with the individual being excluded, is the the only way a block could work, and is pretty crappy in conception.

If you don't want to play with someone who isn't breaking any of the game's rules, you should keep your CMDR out of Open, not take it upon yourself to tell me who I can and cannot encounter while your CMDR is around.

I understand your viewpoint.
Utlimately though, it's fine by the rules and tools allowed. Again, it's a failure of the crappy instancing mechanics in the game, rather than anyone's choices. Folks can do what they like, either way. Too bad for anyone blocked. Don't get blocked and it's not a problem.
 
Back
Top Bottom