Main > Gameplay

burst rounds in flamethrower

<< < (3/5) > >>

Sprayer:
Interesting how threads concerning this topic pop up regularly. I wonder if "burst" and "flamethrower" are words too hard to type into the search?

--- Quote from: sparklerfish on August 17, 2014, 02:36:30 pm ---[...]
Dragon Tongue Light Flamethrower
Primary Damage: Fire 1.2
AoE Damage: None

Burst rounds multiply AoE damage by 1.5.  So, what's 0 x 1.5?
[...]
--- End quote ---
Also, the burst description nowhere states the AoE damage is boosted by 1,5 (which would make buffed burst LJ OP) but the actual Area of Effect is increased.

To mister lvl5/1/1 there (whose ignorance I actually do find excuseable):
The closer you are to enemy ships with your flamer the harder it becomes to burn litterally every component at once. So you either can focus on one component to add as many firestacks as possible, sway your aim and spread the stacks out so all components burn but take less damage than one or two would or use burst ammo and aim at your primary targeted component and hit more/every component while not loosing too much dps on the primary.

Buchou:
I remember reading somewhere on here (sorry, can't remember exactly where) that the flamer has an AoE radius purely for adding stacks. The AoE damage is 0 upfront, but is useful for adding stacks of fire around the target. Burst increases the range of the AoE so I'd assume it would enable you to light an entire pyramidion on fire, for instance, by aiming at the centre, due to spread and AoE combined. 

HamsterIV:
I was contemplating burst flame throwers recently and a question came to mind:
Could a larger AOE flame particle stay on a target longer thus causing more stacks as it passes?
Say this Ascii art represents three normal flamer particles over three updates with * being a component
( )   ( )   (*)
  ( )   ( ) *( )
    ( )   ( )* ( )
And this represents burst ammo over the same three updates
(  ) (  ) ( *)
  (  ) (  ) (* )
    (  ) (  )*(  )

The * is calculated as a hit in more updates. I know muse stated that one component can't be hit by the same projectile twice in the case of balloon damage bleed through, but that is a single hit calculation done on one update tick. Can a flame particle do a hit on the same component twice in different update ticks?

sparklerfish:

--- Quote from: Sprayer on August 18, 2014, 03:57:59 am ---Also, the burst description nowhere states the AoE damage is boosted by 1,5 (which would make buffed burst LJ OP) but the actual Area of Effect is increased.

--- End quote ---

Sorry, I misspoke about the multiplier, but since there is no AoE damage listed at all, I figured that burst would not affect it.  If there is no AoE damage, it can't have a radius, can it?  I was corrected and appreciated the information.  You don't need to be rude or condescending.

Even if it's a distance modifier and not a damage modifier, I still was unclear on how you could place any sort of multiplier on an AoE of *nothing*.

sparklerfish:

--- Quote from: Sprayer on August 18, 2014, 03:57:59 am ---Interesting how threads concerning this topic pop up regularly. I wonder if "burst" and "flamethrower" are words too hard to type into the search?

--- End quote ---

Also, I tested your theory by typing those exact words into the search, and found no relevant threads.

Sorry you find my curiosity inexcusable.

I wonder if "burst" and "flamethrower" are words too hard to type into the search to first confirm whether doing so is even remotely helpful before being rude to someone with a question?


edit: I stand corrected.  I found one mention in one of the very LAST results in the search.  SO SORRY TO WASTE YOUR TIME WITH A THREAD ABOUT SOMETHING THAT HAS BEEN ADDRESSED.  I am deeply sympathetic to the amount of time you lost in your life by voluntarily clicking a thread and reading it.

Also, the post I found was old, and I know that the flamethrower has been changed many times, so I wouldn't have had any idea if that were still accurate or not.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version