No unit collision in PvP like there is in PvE is odd imo

Rbquin244 Profile Options #1

0

Let me start by saying I have a 38 slayer and warrior. I think there is a problem with how PvP mechanics work and how warriors deal damage. Wars are very combo based to maximize there dps. Using Traverse Cut as an example, when dpsing a mob your character does not travel threw the mob when using skills (this makes sence, if you use a skill and are aimed at the target not off to the side or dodged you should collide with it and not pass threw it). You also can't run threw the mob w/ out dodging threw it. So why the second you flag for PvP or duel can you still run threw PC players? It doesn't make sense to me. I can understand why we can run threw each other when we are not pvping as to avoid annoying collisions while in towns ect. It is pretty much impossible in pvp to hit a person with more then one traverse cut as the skill thrusts you forward so much after one hit even aimed precisely by the second you have passed threw your enemy and are stuck wildly swinging for 12 more hits mean while being blown up. I am just wondering why the devs decided to take unit collision out of PvP? Even if I stun my target any skill I use i.e. blade draw, rising fury, reign of blows, even basic attacks after one swing I pass right threw my target. Imo PvP collision should work the same way it does vs mobs it only makes sense to me. I would like others input on the matter please. Maybe I'm just crazy but, if I have a stunned target and line up a perfectly aimed traverse cut or even basic attack I should not just pass threw them after one swing if I miss them then yes I can see that but just like when facing a mob in PvE if I'm aimed on my target I should keep hitting them I think.
Rengeki Profile Options #2

0

i thought that only happened in towns...
Rbquin244 Profile Options #3

0

It has been happening to me out of town too as of late... maybe im bugged?
Atlas04 Profile Options #4

0

1
Favorable
Puella.Magi.Sayaka Lvl.44
Mount Tyrannas (PVP)
Elin Warrior
Could be lagging, that can lead to all sorts of problems. There is defiantly collision in pvp otherwise my leaping strike would never land on my target. I would just soar right over them.
Indomitus Profile Options #5

0

Probably bug? No collision in PvP would be stupid for such a game.
Goliith Profile Options #6

0

It's a bug, I've never experienced that except for when within or very close to a town.

Just last night at the end of the beta I was dueling and there was full on collision.
cunningStunts Profile Options #7

0

Yes its a latency issue, maybe not with you or your opponent, but with the movement and attacks registering into the server. The only place you wont have collision is INSIDE of a town.
Cavo Profile Options #8

0

I fought a slayer on saturday in the open world as a lancer, I was blocking his combo attacks, but after two attacks he would be moving through me and hitting me even though I was blocking because he was now technically on the other side of my shield. If that is a latency issue with the server, it kind of needs to be fixed otherwise lancers are going to be pretty ineffective at keeping back melee in pvp situations.
Idiom Profile Options #9

0

It should only be in towns... try dueling in the world and there's definitely collision.
Garthvader Profile Options #10

0

1
Favorable
Sushieho Lvl.60
Tempest Reach (PVE)
Human Warrior
BTW this entry is entirely for collision in BG as the only other place I have run into the issue is in town but not in duels out of town.

I have the same issue. I will pounce and hit the target then initiate traverse cut via the combo and 90% of the time it will travel through the target registering no hits. Further I will do it in a crowd of people in BG and it will register NO hits. I will follow up with blade draw and it will charge forward through the target and again register NO hits. Warrior in BG is broken as far as collision goes. It is basically a crap shoot, sometimes you will hit a combo but most of the time you WILL NOT and you have to take extra measures to special aim those moves. This makes PvE and PvP aiming for warrior ENTIRELY different. THE COMBOS DO NOT ACT THE SAME WAY. Its annoying but I have learned to deal with it for now and have done fine in BGs but there are many matches where I want to punch my monitor. I submitted a ticket for this and I will copy their response below. I doubt they will bother to address this issue even though I think its a MAJOR oversight.

Pasted from my ticket:

You said... 08/30/2012 08:09 AM
PvP for the warrior is broken in Battlegrounds. Just like when you initiate a dual in a town, the collision detection seems to be turned off. Therefore, half of the warriors moves DO NOT connect the the enemy you are aiming them at. This is a HUGE flaw that you guys overlooked and it has totally ruined my pvp experience in the game. When I do Pounce, traverse cut, blade draw combo which is one of the warriors best combos, only pounce connects half the time. Traverse cut generally goes right though my target and blade draw only 10% of the time ever hits ANYTHING because it is a charge forward move and since you guys FORGOT to enable collision detection goes directly through the target and misses. For a game so reliant on AIMING the aim does not matter if your hit just goes through everything. PLEASE fix this.

Response:
This is something I've noticed with PvP in any class, not just the warrior. You do have to be a bit aware of the distance in which your attack reach, if the character is too close and it's a further reaching attack such as pounce it does risk going through. I have put in a report about the collision in any case so that it can be looked into, as I do understand this could cause frustration.

Please let me know if you have any other questions!

For The Federation!
Alyssa “GM Koboshi”
EME Customer Support - Specialist

They write it off as being an aiming issue but I disagree because you can't mistake aiming when I am barreling into 5 other players with a pounce traverse cut blade draw combo and not one hit registers. So either it's MAJOR game breaking lag or they F'd up collision detection period imo. Hope that sheds some light lol.



Edited by: Garthvader 9 months ago - Reason: forgot to note something