Concerns about the PvP and why it might not succeed, though I want it to very much!

[Hasseo]

If dont know who you are fighting and chat is limited to only your party how will this not solve the problem? Its real hard to troll someone when they dissappear once they leave instance. I fail to see how it could possibly make it worse. worse you can do is follow someone around and instance and single them out. Big deal, people do that in anygame regaurdless of names. Atleast this keeps is isolated to in instance only.

[Sygmaelle]

They'll be addressing it in specific instanced cases. PvP will still be a broken mess. I'm not doomsaying for the game, I'm saying that that particular issue is going to break it.

You should just stop trying.

[Alhanelem]

But that further makes me question the entire point of the fresh meat thing.

Though, if WoW was any indication, the more toxic players won't be deterred to make a character and 'verbally' harass someone (unless they're using the basic account).

The idea is to prevent harssment during the match e.g. curb stomping / tea bagging / etc which I guess isn't as fun if you can't put a name to the face.

During the beta test all chat except party was locked down. There was a likely oversight though in /emote which was not restricted. It was probably a bug and will hvae been fixed (you could /emote a <t> and reveal the target's name as well)

[Borfin]

Well with an attitude like that, of course it will.

Your white knighting and turning a blind eye does nothing to help SE recognize the problem.

And this is a problem that will leave PvP a broken, likely untouched mess - making it a waste of resources, effort and time spent.

Think interrupting was hard to get used to? Imagine juking interrupts in this game. Imagine kiting other players. Melee characters will be constantly on the move because that's what PvPers do. It can delay actions, if even for a second, because the server recognizes you as being somewhere other than your client does, and that delay can mean the difference between a win and a loss.

Kiting when your target is right in front of you, but you're being told it's out of range. Ever try to time a Bane on your primary target when your secondary target's running past? Only really functions if you Bane -after- they're close enough to your primary target, when they would otherwise be out of range if stationary. Frustrating as hell.

Imagine dropping Miasma IIs to kite that melee, but every time you hit the button, nothing happens. He's sitting on your head as you run away from him, but no Miasma II. Or your Bind triggers, but in that timeframe he's run within melee range because the server didn't recognize he was bound - oops, there's an Overpower in your face!

It will break PvP. Honestly these other issues are small potatoes, but PvP is going to be a broken mess because of this. Hopefully, they realize that, because as of now they've released no information to indicate they will be addressing it in the Arena itself.

The end.

[Naunet]

While we're aware some of you don't like the use of an anonymous name like Fresh Meat, the team has decided to go with that for now and don't have any current plans to provide additional options for it.

I know it may seem a minor issue compared to something like positional lag, but I feel like this is a big mistake on the PvP team's part. I don't want to fight against anonymous pseudo-NPCs. I want to fight against actual players. I want to be able to recognize a formidable opponent by name and think, "Awesome, I know this guy. This fight's gonna be good!" The whole Fresh Meat thing kills a lot of the competition and spirit behind PvP.

[Divinemight]

Your white knighting and turning a blind eye does nothing to help SE recognize the problem.

They already recognized the problem. There is a recent official statement in regard to changes to netcode on populated zones only, especially Wolf's den, primals and bahamut's coil. Am I white knighing according to your logic?

Netcode issue isnt something new, it exists in FF11 ballista. It is an issue, yes, game-breaking? Not really. Most of my jobs in FF11 on ballista are close range: Ninja, Thief and Paladin, but i dont really find that netcode delay is game breaking. I dont have have too much trouble landing my weapon skill on target that is kiting me. You can go on and argue that Ballista is not a true PvP, but you need to kill someone to obtain Gate Breach nevertheless.

[Borfin]

They already recognized the problem. There is a recent official statement in regard to changes to netcode on populated zones only, especially Wolf's den, primals and bahamut's coil. Am I white knighing according to your logic?

Netcode issue isnt something new, it exists in FF11 ballista. It is an issue, yes, game-breaking? Not really. Most of my jobs in FF11 on ballista are close range: Ninja, Thief and Paladin, but i dont really find that netcode delay is game breaking. I dont have have too much trouble landing my weapon skill on target that is kiting me. You can go on and argue that Ballista is not a true PvP, but you need to kill someone to obtain Gate Breach nevertheless.

It is game-breaking in PvP.

In PvE it's obnoxious and a major annoyance. In PvP? It will destroy it.

[Divinemight]

It is game-breaking in PvP.

In PvE it's obnoxious and a major annoyance. In PvP? It will destroy it.

My question to you is, have you been playing in FF11 Ballista with exactly same netcode issue? I did and I should be complaining according to your hypthothsis. Unfortunately, I did quite well in Ballista and I also able to provide screenshot of Star Cap as proof. Are you sure you are not here arguing just for the sake to argue? They already announced that netcode will be addressed for zone like Wolf's den. Is that not enough for you?

The discussion of this thread is no longer about netcode as we all know this issue is getting addressed for Wolf Den. Current debate is about whether we should be anonymous or not. Would be nice if you stick to that.

[Alhanelem]

In PvE it's obnoxious and a major annoyance. In PvP? It will destroy it.

In PvP in FFXI there were specific adjustments made in PvP to make it playable- unable to alter server response they increased melee attack ranges so it wasn't impossible to hit people trying to run from you. They've also established that they can adjust response for specific locations but can't do it in the open world because a lower response time would put too much stress on the server. They said they were decreasing the response to .1 seconds (100ms) in specific instances.

As the above poster said, they know about the problem, and they will be making adjustments to address it where they can without causing the very problem they're trying to fix to get worse.

[Borfin]

My question to you is, have you been playing in FF11 Ballista with exactly same netcode issue? I did and I should be complaining according to your hypthothsis. Unfortunately, I did quite well in Ballista and I also able to provide screenshot of Star Cap as proof. Are you sure you are not here arguing just for the sake to argue? They already announced that netcode will be addressed for zone like Wolf's den. Is that not enough for you?

The discussion of this thread is no longer about netcode as we all know this issue is getting addressed for Wolf Den. Current debate is about whether we should be anonymous or not. Would be nice if you stick to that.

What's awesome about discussions is that multiple can be happening at the same time within the same thread. Did you know that?

Incidentally, I was under the impression Wolf's Den was not one of the areas with planned workarounds, so it's good to know they're actually looking at it.