I had a game of team snipers tonight to chill after a lot of ranked games.
Appreciating the no-naming policy, my team finally versed an actual cheater. This man did not care one bit about hiding his habit. He definitely had aim-bot, walls and auto trigger.
Account has 0 friends, 23 games, set to private, ignored all messaging.
In snipers on Streets he pulled 32 kills, 28 headshots, 70% accuracy and his teammates stopped playing because it was pretty obvious. died twice and had no positional skill or situational awareness. He just sprinted around all game like a kid who snorted daddy’s sherbet whip sniping with 90-180 degree instant spawn kills haha. It was nuts.
We could only kill him (twice) when he was COD reloading and is to inexperienced to know he could YY and refire. I don’t think the guy even swapped to shotgun once.
We all reported in XBL and on Halo Waypoint Support with evidence. Well that’s my anecdote…
When it comes to ping manipulation there’s ping reduction, and ping tampering in this regard. Geofiltering is which is tampering and is officially against TOS, swapping out router models and Ethernet adapters on a PC or port forwarding is ping reduction and is allowed.
Reducing ping to be lower reduces perceived latency and improves overall actionable performance and likelihood of success.
Hypothetically manipulating ping to be higher increases perceived latency that negatively impacts your overall actionable performance, for the possibility of winning the occasional gun fight that revolves around cover.
The latter is an clear net negative in favor of a niche dice roll used in the manner that you suggest, so I’m going to say that it’s definitely a stretch.
Using NetDuma, DumoOS, plus efforts in openWRT to geofilter from a separate piece of hardware (your modem) would also be considering tampering much like changing the windows hosts file to geo filter.
Forcing high ping by throttling your upload rate while keeping healthy download rate will not provide you a strong advantage due to the “shooters advantage” approach. Due to recognised latency the game will provide you benefits in lag compensation (shooting someone as they’ve just passed a corner on occasion) but when you duck or hide behind something, everyone else sees it as though you have not done that yet for likely an additional BR trigger or ~150ms.
Big Brains will max throttle upload during a grapple hook or good power slide. That is some real rubber banding haha
I should restate my initial question once more in relation to your own statement though:
I’m interested in your evidence, not a collection of other players clips that only at face value purport your claims. I’m aware this game has glitches and bugs, I’m looking for evidence of you (@M1STA_WU1FY) being shot through a wall as you claim it happens frequently and that you have evidence of your own.
Like I said, I already have entire montages of it. I am finishing one right now from just stupid stuff that happened this week. Why do you STILL think this isn’t a problem when everyone but you seems to experience it?
Edit: Here, this is just a handful more from this week https://www.youtube.com/watch?v=X882SoVQevg
Ok right off the bat, you got needler’d dude, nothing fishy at all.
Second clip the bullets did not go through the wall, but rather through the doorway and you received damage through the wall. This is more in line with the latency phenomenon shown above.
Watching more it seems like you’re experiencing a ton of packet loss more than anything in the worst examples. Honestly my experience even in the occasional 150ms+ ping situations is nothing like what you’re experiencing, noticeable input latency at the absolute worst. My games are buttery smooth network-wise.
You have a ton of really bad experiences on display here, you really do, like it’s bad bad. The last time I experienced an experience that bad it was packet loss leading to rubber-banding, teleportation, and hit registry situations. I discovered my Ethernet cable was kinked, had frayed connectors and my onboard port was fried. If this is happening as frequently as you claim, are you certain it’s on 343’s end?
It could also be closed ports on your wifi as well. I’m just spitballing here.
Like dude, I don’t think anyone is having those issues as frequently as you are. It could be partially on 343, but I think you got stuff going on your end as well.
Right hand on the Bible, I’m have yet to experience even a fraction of the best case bad scenario that’s in the first montage alone, no lies, my experience is near flawless in an online context. I would definitely make sure it’s not on your end, because the frequency alone is enough for me to think it’s on your end. The occasional issue is expected, and even purported, but your clips and claims and frequency are anomalous from what I’ve seen.