About Gauss And Moving Forward - Feedback
#341
Posted 07 September 2013 - 07:07 PM
Can I please have my old gauss rifle back?
#342
Posted 07 September 2013 - 10:06 PM
Also its now terrible for sniping as I need to lead the target even more waiting for it to charge up etc. Now its better for brawling.
Edited by Vyviel, 07 September 2013 - 10:07 PM.
#343
Posted 07 September 2013 - 11:59 PM
Arturus, on 07 September 2013 - 01:09 PM, said:
Odd...
You can assign it to mouse buttons. Just assign a weapon group of your choosing to that mouse button in the game control settings, move the Gauss to that weapon group in a match, and voila. You can assign as many weapon groups as you have buttons for. Personally I use button 4 on my mouse.
Edited by Guido, 08 September 2013 - 12:03 AM.
#344
Posted 08 September 2013 - 02:26 AM
I think reducing the amount of micromanagement the weapon requires a bit by making it automatically charge to full when you click the fire button will make it easier to use in complicated builds, while still making it hard to aim as you'd need to either hold the fire button to time your shots or track your target while the gun is charging. There is also the issue of new players not knowing how to fire the thing at all, which I don't think can be easily fixed by a tutorial as a lot of new players won't bother doing them. For these players a one click charge would work rather well as the Gauss would always fire when ready unless the player deliberately holds the charge.
There is also the issue of using multiple Gauss rifles, though at the moment only a few mechs can do it effectively these builds avoid the issues associated with using a Gauss in combination with other weapons completely. I think a linear increase of the charge delay based on the number of Gauss rifles being charged will be enough of a disadvantage to prevent abuse of these builds, something we'll need if we're ever going to see mechs with the tonnage and hardpoint layouts to effectively wield three or four Gauss rifles. ( The Annihilator 2A for example. )
Solving this problem now greatly increases the number of potential new mechs, as certain mechs would otherwise be blatantly OP if introduced.
#345
Posted 08 September 2013 - 03:58 AM
#346
Posted 08 September 2013 - 07:11 AM
Fans MWO despair.
#347
Posted 08 September 2013 - 07:38 AM
Lord Perversor, on 07 September 2013 - 08:53 AM, said:
Simple, he can no longer alpha strike like a monkey. He now actually has to use his brain to shoot ... or write macros.
#348
Posted 08 September 2013 - 07:42 AM
Liquidx, on 07 September 2013 - 01:47 PM, said:
And I say the implementation should be improved upon and make it a core component of the Information Warfare aspect of the game. Click on my sig for some ideas.
#349
Posted 08 September 2013 - 08:12 AM
In a heated exchange its too distracting to try and keep track of the weapon cooldown AND the charge, AND the loss of the charge if you hold it too long.
It needs a strong audio cue to indicate its fully charged.
Previously aiming the gauss with the slower projectile speed required more skill than the current one as you had to lead your target, this "ima charging mah cannon" mechanic isn't really a good way of addressing the balance issues with this weapon.
#350
Posted 08 September 2013 - 09:50 AM
Hexenhammer, on 08 September 2013 - 03:58 AM, said:
That would actually be a trick that might some of the best chances to remove a critical one of the boating advantages. If everyone has to chain-fire, then boats can no longer deliver massive, converging alpha strikes.
Though 0.5 second would only really work for PPCs, Gauss, and AC/20. Other weapons, and particularly lasers, would probably need a shorter delay.
Of course, it doesn't remove the other drawbacks of mixing weapons - incompatible recycle times, different projectile speeds, special snowflake mechanics like the Gauss charge.
#351
Posted 08 September 2013 - 10:03 AM
#352
Posted 08 September 2013 - 11:20 AM
#354
Posted 08 September 2013 - 11:35 AM
Revorn, on 03 September 2013 - 03:43 PM, said:
In many Matches i see Ligths scoring 800 dmg and 3-4 Kills, Uhmm... Maybe they are verry talentet and skillfully Pilots, but it looks somewhat wrong to me. Imho.
If a light does 800 points of damage in a match, he deserved it. It's not that easy to make and far from it. As for 3-4 kills, I get that once in a while in my Jenner, but they were mostly opportunity kills, where I basically finished off a 'Mech by alpha-striking his weakest and most damaged torso or leg. I've had a few kills that were all mine a few times too, but for the majority of the time, I get more assists than kill with an average of 300-400 points of damage in a match. That's fair I think. The most I've got in a single match was 650 points of damage. I had 3 kills and 7 assists and lots of components destroyed.
I'm curious as to what exactly they want to change in lights. Paul mentioned something about doing to lights what they did for mediums, but I'm not sure what he was referring to. Anyone knows? (PS. I was away for the most part since open beta started up until a few days ago).
#355
Posted 08 September 2013 - 05:07 PM
#356
Posted 08 September 2013 - 06:18 PM
And that brings me to... It sure would be nice to pick the maps that you're willing to play on with the currently selected mech before you hit "go" on the find match launcher. It sure would make playing the game more enoyable if you could pick the mech, color scheme and even loudout in alignment with the maps. Who doesn't want to see mechs with alpine camo on an alpine map or jungle cammo on Forest Colony.
And where's the maps that have day changing to night and vice versa. Why can't we battle at River City as the sun is coming up...
#357
Posted 08 September 2013 - 07:59 PM
Let me preface this: As a fellow game developer, I understand you have a *lot* on your plates...
I have removed all Gauss Rifles from all mechs that previously had them. The ONE mech that I lament this change on the most is my 1X Cataphract. That was not a jump sniper at all, it couldn't physically be one. Now, you have basically made the weapon broken. I tried this out for 5 matches, and frankly...I normally do 200-300 damage per match (not great, not terrible) and after this change, I would guesstimate roughly half of my Gauss rounds that should have fired did not. This mechanic is broken...the timing is screwed up or it simply doesn't work sometimes.
So, I am totally disappointed that a far better solution wasn't thought out to "fix" whatever issue you had. If the Gauss is an issue at short range...why have the AC/20 do 20 damage? Frankly...I felt that ER PPCs were the short range issue...and the fact that you guys keep turning a blind eye to the most seriously overpowered energy weapon is baffling. The Gauss Rifle was working as it should have been all along. The ER PPC is *the* issue for high damage alphas...2 of those do 20 damage at *greater range* than Gauss Rifles, the projectiles fire faster, the energy damage is pinpoint and instantaneous. It is *clearly* broken, yet fails to be addressed *constantly*.
Addressing something that wasn't broken, and turning a blind eye toward something that is clearly out of balance is just mind boggling. I hope you find an alternative to solving the issue you were after...and it should involve "nerfing" an outlier...*not* something that wasn't broken. You can boat PPCs all day long...you *cannot* boat Gauss Rifles! Sure an extremely slow Jagermech can do it, with no other weapons if they carry enough tons of ammo to matter...but that isn't really a viable build, even under the old system.
-my $0.02
Edited by Gyrok, 08 September 2013 - 08:03 PM.
#358
Posted 08 September 2013 - 10:20 PM
#359
Posted 08 September 2013 - 11:40 PM
h0wl, on 07 September 2013 - 06:51 PM, said:
I'm honestly sorry I paid for the Phoenix package. Pretty funny after you buy the highest level they come out with more mechs to buy. Real class act PGI.
So get a refund.
#360
Posted 09 September 2013 - 05:53 AM
I can understand the logic of it but you applied it to the wrong "Type" of weapon. A Sniper needs his weapon to fire "now" not in 1.5 seconds or any other delay length.
Just... No!
3 user(s) are reading this topic
0 members, 3 guests, 0 anonymous users