If 40k got caught, you can bet there are another 40k that didnt get caught. The only way I see fair gameplay is Xbox having their own servers apart from the cheating PC users. When hackers are on the server, they affect gameplay on xbox. When I get 65 hits and 1 kill, something is wrong! I will say it again. And it was after the mass ban when my shells actually worked. And it took more than 1 perfectly placed shot. I’ve gotten the Sniper Badge maybe 3 times and its 50% knowing your ballistics and 50% pure luck. The obvious cheaters are camped on the edge of the map. Aimbots seem to always be a perfect center mass shot whether youre doing 47mph 3km away or behind a building. I also am killed by getting 1 shot anywhere on my tank, be it a fender graze or machinegun graze by any player. I cant explain why or how, but if hackers are in the match, I shoot blanks or so to say, my shells are ineffective. The problems with shooting blanks is also back. I have concluded that most if not all of the cheaters that were banned are back with new accounts. But now its been a few weeks and the player count is back up to pre-ban levels and so are the previous problems with the hackers. My shells worked! The players that didnt get caught were laying low. (Xbox) After Gaijins mass ban, game play was actually fun. Until WT addresses the problem it is what it is. I get team killed or hunted, even by team members. Since I’ve called out “aimbot” in match, people have become hostile to me even though I have never called them out by name. I know that the cheaters (narcissists) want you to believe its a skill issue. ![]() Typically.Īlso, I’ve thought that the infestation of modded cheaters are the problem. When this is happening I place #1 or top 10 in match’s because my ammo is working.Ħ vs 6 match’s everything seems to work as it should and typically place #1 without WT download interrupted. Just the spinning circle and a notice 5 files bla bla bla. Once in awhile WT file update wont update. ![]() Now I will tell you what I discovered by doing this. To do this on xbox, you have to constantly change your port and not automatic. The game is broken and I think it would be a good guess that 99% of players experiencing blanks are on xbox. I’m here to tell you, you are doing nothing wrong. I am so sick of people not experiencing this issue to spew about everything “you” are doing wrong. Death by getting grazed anywhere on my tank, repair or a crew member needed to be replaced. Ive gotten where I am in WT by mostly hits and assists, not kills. When other times in 1 shot to the same location it blows up. ![]() It finally did but it took me 6 shots, up close. I think the 2a6 was already shot in the front by my teammate from way off while I was directly behind the tank, and it couldn’t rotate it’s turret at me, so I just kept shooting it expecting it to die. I remember shooting 6 shots into the back of a 2a6 and another time into the rear turret of a BVM, with zero damage, not a single bit of damage at all. I understand your point about spalling, but in these cases with moving the shots all around the tanks and what I’ve seen, nah it shouldn’t be happening. Maybe something with the code needing shots to be made further away I don’t know. Maybe it’s a bug with being so close I don’t know. It’s not all the time but I’ve experienced it time and time again. ![]() A point blank shot 90° to the turret straight on should never be a bounce, especially close up like this. I’ve seen the smoke and stuff from the shot impacting, but it just does nothing, and sometimes I mean absolutely nothing. I’m talking shots to the direct broadside, all parts of the turret especially where ammo is, and areas where crew are. In my A1 SEP I’ve been up close like that on tanks, in this example I would mostly say Leos 2A6 and T80 BVM etc, and with multiple shots just getting no damage hardly at all.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |