Printable View
I'm noticing that a few times when I have been killed it's showing up twice in the message box that I've been killed by the same player
e.g.
Joe killed Sarge
Joe killed Sarge
Is this an error/bug (only counting towards one death) or are two deaths actually occurring at the same time? If the latter is the case, what causes it and how can it be avoided?
ta
Sarge
I've noticed it happens normally when there's a delayed attack like fatal burst that happens after death. Seen it happen on other occasions too, and I have no idea what causes that.
Yeah that makes sense. Other possibility is the swarm.Quote:
Originally Posted by Otukura
They need to fix that cuz I counted someones kills after match and those double kills count.
Agreed. Its a nasty bug that needs fixing a.s.a.p.
Yeah, it's been around forever and each time it occurs, it counts as an official kill/death.
The worst I've seen is one player killed by three others simultaneously.
Vs/stomp builds were so powerful they weren't only insta killing you, they were double insta killing you.
For the record, this bug persists. It makes DM scoring a bit unfair. I just won a fight with a double pop at 23. It shouldn't be like that...
Agreed, it's definitely a problem in DM. Man the vs/stomp build messed up pvp on so many levels. I really don't know what the devs were thinking when they implemented it in the first place.
I can just imagine the conversation:
Lead dev: "Hey, we should make a tree with skills that stun, does high damage, knock backs, uses little points to acquire, has little blood loss, and kills one thing twice."
Underling: "Dude, that would just be stupidly over powered for pvp."
Lead dev: "what's pvp?"
Underling: "It's when people fight each other in the game. We gotta kind of make the skill trees balance so there is some variety in builds and play style. If we just make one dominating tree that is better on blood use, gives better survivability, has higher damage for less points invested, and utility mechanics, everyone that pvps competitively is going to use the spec. Moreover, with a different spec will get their asses handed to them, and will eventually spec the tree to be competitive, or stop pvping all together. Thus, everyone will end up having the same build, which takes the whole point out of having skill trees in the first place."
Lead dev: "OMG, I love rodents!!! Throw some of those into the mix!!!"
Underling: "Seriously?"
Lead dev: "Rooooodeeeeents!!!"
Underling: "Would you also like to limit the players sight to 20 feet by taking away option to tilt the camera in pvp?"
Lead dev: "Great idea!!!"
Underling: "I was being sarcastic."
Lead dev: "Sarcasm is the mother of invention. Now that that's settled, let's talk about platinum..."
Hey guys,
Thanks for the head's up on this bug. We're digging into it.
I often wondered why it was limited to 20 feet, but realised why when I started playing on my phone. I usually play with an xbox 360 controller pad on chrome, so I can constantly rotate the camera 360 deg around me whilst keeping a skill charged (e.g. FB assigned to right shoulder button, left thumb on left stick for movement, right thumb on right stick for camera). This is useful when needing to change your field of view all around you whilst moving and charging.Quote:
Originally Posted by Blaquehaaart
However when playing on a phone it's difficult to rotate the camera while moving around and keeping a skill charged. You either have to take your right thumb off the skill button (thus losing the charge and effort of the skill) or take your left thumb of the virtual joystick (thus stopping your movement) to swivel he camera around. The limited range of view is beneficial in this case as it means that your view behind you (if you are unable to swivel the camera due to the above) isn't much less than an opponent's front field of view to your back, meaning you won’t be as vulnerable to surprise attacks from behind.
If everyone could swivel the camera, move and charge attacks at the same time, then expanding the FOV would work, but this isn’t the case. Players with my setup would have a much higher advantage than those on phones and tablets....and after all, this game was primarily designed for them.
This is still happening and i think some players figured out how to do it. One guy double killed me a few times in one match. Coincidence, i dont think so. Plus the player had a really high k/d ratio. Pls fix this soon.
That is true for those that have only thumbs.Quote:
Originally Posted by Sarge
I myself use my index fingers to rotate the camera pretty much all the time while running and holding a charge with my left and right thumb, respectively. (galaxy note, galaxy tab and other androids)
But your point still stands. It's way easier for others and allowing pitching in pvp would yield unnecessary advantage to those being capable of it.
A lot of tactics in both ctf and dm are currently related to this limited fov and in a good way in my opinion. But this is ot in this thread.
Dont want this to be forgotten. Its still happens, and more frequently now. It is now a matter of if u cant beat them, join them. So just about everybody has figured out how to get double kills.
Don't agree, the combo that results in double kills is my usual combo, don't use it just for double kills.Quote:
Originally Posted by monarchival
I do agree this needs to be fixed.
Is it safe to assume that since it's been a month that these double kills aren't going to be fixed?
Some fixes require a code integration process, which can take a long time. The fix for this is being prepared for publish, so expect it soon.Quote:
Originally Posted by robert7204
I haven't actually tried on a tablet yet but can see how your method would work. Doing this on a phone however is almost impractical as a large portion of the screen is covered by fingers and thumbs.Quote:
Originally Posted by Hullukko
Will try it out on a tab tonight.
Sry, last post from me re thumbs and fov in this thread.
???? Still being coded I guess?Quote:
Originally Posted by Bpog
A lot of people are exploiting this bug and its not right. I wish they could get this fixed already. Now theres even 3kills and sometimes 4.
any word on this yet?
?????
So, ur not going to fix it?
This thread has been completely ignored. Smh!
Must be still in the "coming soon" stages??? this has been a serious problem for too long imo.Quote:
Originally Posted by Kremin
Sent from my SCH-I510 using Tapatalk 2