It is this kind of behavior that we will be fixing in the May 17th patch, not just for the Long Tom but for all strikes.
Change To Long Tom Damage
#1
Posted 02 May 2016 - 01:41 PM
It is this kind of behavior that we will be fixing in the May 17th patch, not just for the Long Tom but for all strikes.
#2
Posted 02 May 2016 - 01:54 PM
#3
Posted 02 May 2016 - 02:06 PM
#4
Posted 02 May 2016 - 02:08 PM
Quote
I still think this should be removed for Art and Air strikes as well.
Consumables clearing out cockpits… even if it’s just a 1-time thing every 25 games… it sucks big-time for the person who got cleaned out by a consumable…
One that has a very poor visual effect – takes too long to show up, and lasts too long after the strikes hit.
But this is just an opinion that doesn’t matter, so what evs. It's cool I guess.
#5
Posted 02 May 2016 - 02:21 PM
Because that's still a 267M face killing zone
Although, instead of being a 267-286M Sphere of Death, it's now RNGeesus who decides your face blows up?
#6
Posted 02 May 2016 - 02:24 PM
#1 you knew the code was screwed up but they decided it was still a good idea to set it at a high damage value
#2 after multiple complaints and grossly obvious stats you lowered the value but not enough to even make a difference
#3 how you even got to this point after 1 and 2 is beyond me.... testing or even playing one game with it at any stage would tell/show you it was broken and needed fixed
#7
Posted 02 May 2016 - 02:26 PM
Into the trashcan of history it shall go!
Let scouts uncover e.g. repairpads or rearmpads or alternative spawnpoints for the invasion groups instead as third objective.
Rick
out
#8
Posted 02 May 2016 - 02:29 PM
It gives teams a reason to Scout.
#9
Posted 02 May 2016 - 02:31 PM
#10
Posted 02 May 2016 - 02:40 PM
But maybe instead of the amount of damage, if the frequency between barrages was increased and some more time added between smoke and hit, it would make it more acceptable.
Anyway any mech within 75-100m should take heavy damage.
#11
Posted 02 May 2016 - 02:40 PM
There's something about keeping people on their toes, but with the few minority of units/players equipped to deal with them (and you need organized teams from the get-go), it stands to murder 90%+ of the population that don't know how to mitigate them properly.
Just changing the cooldown from 2 minutes to 4 minutes (every other scanner sweep) would actually help the situation out.
Edited by Deathlike, 02 May 2016 - 02:41 PM.
#12
Posted 02 May 2016 - 02:40 PM
#13
Posted 02 May 2016 - 02:47 PM
Still only a short warning and a little smoke?
Still not time to flee or seek cover? (cover?)
Still absurd enorm radius?
Still 1 Mechs dead and 6 other without armor, left as living corpses to be farmed?
Skillcrow-Mode and this terribel bad stupid Gamedesign-Desaster-Highlight "Long Dumb" has ruined my motivation to play FW. Why must PGI F... Up Phase 3 so badly? So many good ideas and then they destroy it with Skillcrow-Mode and Long Dumb.
I do not find the words without get banned. And your event... I know what you can do with it....
Remove Long Dumb!
#14
Posted 02 May 2016 - 02:58 PM
I'd just have liked the LT to not deliver a single nuclear blast and instead been an actual artillery barrage the controllers could fire like consumable ones, with a greatly increased area of effect and number of impacts + a moderately higher damage per impact.
The vorpal artillery was only good for making sure people stuck to scouting when a world hit 90%.
Quote
Maybe if PUGs actually realized that Skillcrows against other IS 55-tonners are called "target practice" and stopped bringing Urbanmechs for recon, this would change.
#15
Posted 02 May 2016 - 03:00 PM
#16
Posted 02 May 2016 - 03:03 PM
Every MW before had the possibility of killing the Long Tom Armor - in-game.
That also would need a scouting and Lance Attacking in-game - not out in a "seperate" game.
I also think you have misunderstood the wishes of the people to have for a LongTom available. I know no one who wanted to have another Strike comin from nothing out of nowhere. People wanted to field their Long Tom in Mechs or atleast within an artillery piece. That brings in opportunity, but its not undefeatable - so you have to protect that piece.
Before i have seen LongTom killing 27 Mechs in agame - you should make it in the leaderboard and it would stand on top.
And yust btw an originially Long Tom mad yust 30 DMG on a single target, so this is still an very good targeted barrage of 10 Long Toms at once
Edited by BlackHeroe, 02 May 2016 - 03:11 PM.
#17
Posted 02 May 2016 - 03:06 PM
Only a potential Sphere of Death
Praise be RNGeesus
#18
Posted 02 May 2016 - 03:17 PM
Quote
Vs. PUGs, a pack of Streakcrows cleans house.
And there are far more PUGs in Scouting than unit lances right now. This goes triple for IS defenders vs. Clan, who generally have derp pilots swarming in to die by the dozens. Like I said. Urbanmech recon forces.
Quote
Mech-equipped LT's are a "artillery cannon" that deals less damage and far less reach than a real LT arty piece.
If it gave you an on field LT battery, though- that'd be pretty darn awesome. Even it simply was a six-pack of destroyable cannons that would fire at sensor-locked targets at random.
Edited by wanderer, 02 May 2016 - 03:20 PM.
#19
Posted 02 May 2016 - 03:34 PM
MoonUnitBeta, on 02 May 2016 - 02:08 PM, said:
Consumables clearing out cockpits… even if it’s just a 1-time thing every 25 games… it sucks big-time for the person who got cleaned out by a consumable…
InnerSphereNews, on 02 May 2016 - 01:41 PM, said:
It is this kind of behavior that we will be fixing in the May 17th patch, not just for the Long Tom but for all strikes.
Edited by Void Angel, 02 May 2016 - 03:34 PM.
#20
Posted 02 May 2016 - 03:38 PM
InnerSphereNews, on 02 May 2016 - 01:41 PM, said:
It is this kind of behavior that we will be fixing in the May 17th patch, not just for the Long Tom but for all strikes.
This exact behavior is exhibited by overheat damage, with the exact same results - a single tick of overheat damage can one-shot a 'mech's head component. Any chance we could get that fixed as well, particularly if the code does happen to be similar?
11 user(s) are reading this topic
0 members, 11 guests, 0 anonymous users