Btw, here it is for CH devices (part of it actually).


Gauss Hack?
#21
Posted 26 March 2015 - 07:16 AM
Btw, here it is for CH devices (part of it actually).
#22
Posted 26 March 2015 - 07:17 AM
Johnny Z, on 26 March 2015 - 07:02 AM, said:
Not anything significantly better than what anyone else could do with a little practice. If anything, you've made the weapon worse by forcing it to fire at the end of charge, as you can't delay the shot to adjust aim further or cancel the shot by holding it. Ripping out game mechanics just because some tiny segment of the community uses macros to no real beneficial effect is a far more effective way to hurt regular players.
#24
Posted 26 March 2015 - 08:09 AM
It is called Server Side Authentication.

Go hack a client side .PAK file and see how it works out. Easily enough done for sure.

Edited by Almond Brown, 26 March 2015 - 08:10 AM.
#25
Posted 26 March 2015 - 08:38 AM
I guess it does not make any difference if I charge or I do not played in Beta without and now with it. I can deal with it. The change was made with the 3rd September 2013 Patch - so it is long ago. I think most people who use gauss, just adapted enough.

#26
Posted 26 March 2015 - 02:05 PM
mogs01gt, on 26 March 2015 - 04:41 AM, said:
Also, the charge mechanic gives the Gauss a small advantage when hill humping or peaking around objects. You can pre-charge the weapon, peak around, aim and then release. It's a bit faster than doing the same thing and then clicking.
macro's just click for you they don't change the charge time (ore remove it) if that hapens its not a macro its a hack...
the only thin a macro douse is make mouse clicks / key strokes on a pre determined time skeme..
example;
>pres mouse key 1
>delay 60 ms
>release mouse key 1
>delay 460 ms
>pres mouse key 1
>delay 60 ms
>release mouse key 1
as you might notice this is a horible way to fire a gauss rifle as it gives you a load less controle when you fire (it will fire 0.5s later, even if you are not on target at that moment...)
#27
Posted 26 March 2015 - 02:19 PM
Karl Streiger, on 26 March 2015 - 04:24 AM, said:
ib4 close
It isn't allowed, but regardless it wouldn't even work.
Weapons fire is server authoritative, so if you modified the client to get rid of the delay it would only affect the predicted Gauss shot on your end, which will be replaced by no Gauss shot ( the cooldown would reset ) as soon as your client receives the data telling it the shot didn't actually happen.
I'm not sure what the other hacking prevention measures in this game are, but I do know this kind of hack is easily detectable and could conceivably result in an automatic ban.
#28
Posted 26 March 2015 - 02:36 PM
Satan n stuff, on 26 March 2015 - 02:19 PM, said:
Weapons fire is server authoritative, so if you modified the client to get rid of the delay it would only affect the predicted Gauss shot on your end, which will be replaced by no Gauss shot ( the cooldown would reset ) as soon as your client receives the data telling it the shot didn't actually happen.
I'm not sure what the other hacking prevention measures in this game are, but I do know this kind of hack is easily detectable and could conceivably result in an automatic ban.
from what i understand, to hack things like weapon cd/ charge time/ GH ect... u need to hack PGI's servers ore be neo ...
#29
Posted 26 March 2015 - 02:41 PM
#30
Posted 26 March 2015 - 02:50 PM
Mcgral18, on 26 March 2015 - 04:22 AM, said:
It doesn't show the charge, but there most certainly is one.
I wish they fixed that.
They eventually got around to fixing "DCed spec mode" where your initial spec mode map location was "totally off" and only took movement from the mech to fix itself (since the mech was DCed, it would never move to update the map, thus the bug).
It would be easier to understand when/where people decide to charge their Gauss when you're specing others (people can record it obviously, but it's not live in-game which would be preferable), but it is what it is.
Edited by Deathlike, 26 March 2015 - 02:51 PM.
#31
Posted 26 March 2015 - 03:00 PM
Server-side authority and all that jazz.
You can have some fun dicking around in the testing grounds though.
#32
Posted 26 March 2015 - 11:48 PM
mogs01gt, on 26 March 2015 - 04:57 AM, said:
Awesome... so that kind of macros make people bad with the gauss
What if you lose LOS to the enemy while macro is charging that gauss rifle, waste that ammo to shoot ground? or friendly mech gets into the firing line, shoot it in the back?
#33
Posted 27 March 2015 - 05:41 AM
It's rare, but there was this little gem from a few weeks ago:
Somehow, an enemy (Jager I think) just peeking over a hill on Caustic managed to score a perfect dual gauss head shot against my Catapract... while I was well over 1km away.... moving full speed perpendicular to his line of sight... up a hill... Right, because that's normal. What backed it up was how he then carefully landed every other hit perfectly on my right torso (again, despite the range, speed, twisting, and everything else) until I was behind cover. Our team quickly lost the rest of that match as team mates mysteriously died suddenly from headshots, all of the gauss rounds landing on one location, etc.
There was at least one of them involved in this, but it may have been 2 or 3 of them. I probably should have reported them, but "repeatable, suspiciously accurate fire" isn't a clear offense in the game. Sure, maybe they were actually just the best gauss rifle users in the world, or just very, VERY lucky, but still, it does make you wonder.
Edited by oldradagast, 27 March 2015 - 05:43 AM.
#34
Posted 27 March 2015 - 05:48 AM
oldradagast, on 27 March 2015 - 05:41 AM, said:
It's rare, but there was this little gem from a few weeks ago:
Somehow, an enemy (Jager I think) just peeking over a hill on Caustic managed to score a perfect dual gauss head shot against my Catapract... while I was well over 1km away.... moving full speed perpendicular to his line of sight... up a hill... Right, because that's normal. What backed it up was how he then carefully landed every other hit perfectly on my right torso (again, despite the range, speed, twisting, and everything else) until I was behind cover. Our team quickly lost the rest of that match as team mates mysteriously died suddenly from headshots, all of the gauss rounds landing on one location, etc.
There was at least one of them involved in this, but it may have been 2 or 3 of them. I probably should have reported them, but "repeatable, suspiciously accurate fire" isn't a clear offense in the game. Sure, maybe they were actually just the best gauss rifle users in the world, or just very, VERY lucky, but still, it does make you wonder.
Just want to point out that 1k Gauss hits are not too hard, and the Cataphract has extremely large side torsos to aim for. The headshot was probably a lucky one, however. People are quick to cry hack, but unless there is evidence to support it - and I mean actual evidence - then accusations should stay out of the picture.
Edited by Pariah Devalis, 27 March 2015 - 05:49 AM.
#35
Posted 27 March 2015 - 05:55 AM
Pariah Devalis, on 27 March 2015 - 05:48 AM, said:
Just want to point out that 1k Gauss hits are not too hard, and the Cataphract has extremely large side torsos to aim for. The headshot was probably a lucky one, however. People are quick to cry hack, but unless there is evidence to support it - and I mean actual evidence - then accusations should stay out of the picture.
I know, I know - but like I said: when you've played countless games against a wide variety of foes and suddenly behavior and events in one match are vastly unlike anything you've seen before, it is only logical to be suspicious. I've never seen a game with such absurdly accurate gauss fire at all ranges, twisting be danged, like that one. Maybe it was luck, maybe it was an odd confluence of skilled gauss players on the other team working together, or maybe it was something else. If I had know it was a hack, I would have reported them, or at least requested PGI look over the game for possible cheating, but I didn't.
I've had lucky shots before - for example, I once decapitated a Locust once with a snap-shot pair of PPC's at a crazy angle while we were both moving - but I didn't proceed to follow that up with a bunch of other "lucky" shots in the same match.
So, again, it could have been skill, luck, odd server behavior, or something else.
Edited by oldradagast, 27 March 2015 - 05:57 AM.
#36
Posted 27 March 2015 - 07:11 AM
Curccu, on 26 March 2015 - 11:48 PM, said:
What if you lose LOS to the enemy while macro is charging that gauss rifle, waste that ammo to shoot ground? or friendly mech gets into the firing line, shoot it in the back?
I dont know. I dont use that ****. I have no issues using the Gauss with the charge mechanic. Once you get used to it, it becomes irrelevant. The mechanic only hurts new players.
#37
Posted 27 March 2015 - 08:11 AM
Sarlic, on 26 March 2015 - 04:45 AM, said:
I am not sure. Why would anyone just joke about it? It does not make sense.
It can be trolling, but if it's trolling that would be awkward.
I've seen new players asking people in-game how they could get out of 3rd person mode. 'Alt-F4' is an extremely popular answer (and close to the real thing too). The past 2,5 years I've even seen that remark work in 3 cases when the inquisitive new player disconnected shortly after recieving this 'helpful answer'. Trolls will be trolls.
#38
Posted 27 March 2015 - 08:12 AM
One long running Poll says 80 percent of MWO players want the Gauss Rifle de-sync mechanic removed or altered and that fits the rarity of it's use compared to ACs and Lasers. PGI is not doing their job which is to fix the Gauss Rifle so most players like it and can use it and don't feel the need to macro it or whatever is going on here.
#39
Posted 27 March 2015 - 08:21 AM
Lightfoot, on 27 March 2015 - 08:12 AM, said:
The issue isnt BT design or if players like it or not. The issue PGI attempted to resolve was the ease of use with a PP FLD weapon that was vastly superior to all other ballistics.
Edited by mogs01gt, 27 March 2015 - 10:36 AM.
#40
Posted 27 March 2015 - 08:24 AM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users