Shots Fired: A Machinist Guide

[Greywolfamakir]

This is how much time I can get to react for procs with Gauss Barrel on:



Holy shit, it's not easy...0.31 seconds to react...and skill queue looks like 0.5...You can't spam Split Shot and wait for procs...You are fucked right now with GB. It's pretty disgusting.

[VitalSuit]

This is how much time I can get to react for procs with Gauss Barrel on:



Holy shit, it's not easy...0.31 seconds to react...and skill queue looks like 0.5...You can't spam Split Shot and wait for procs...You are fucked right now with GB. It's pretty disgusting.

If you can get an oGCD in while you're casting split shot it'll actually proc it earlier than if you hadn't (for example using leg graze or foot graze right after split shot finishes casting).
Of course this only works if it does proc.

[RazeLandale]

This is how much time I can get to react for procs with Gauss Barrel on:



Holy shit, it's not easy...0.31 seconds to react...and skill queue looks like 0.5...You can't spam Split Shot and wait for procs...You are fucked right now with GB. It's pretty disgusting.

I wonder if cast times on slug and clean and instant split shot would be the answer. That gives you time to react to slug shot procs and while it'd be hard to react to clean shot procs...you wouldn't need to. You can go straight from slug shot back to split shot, if you got a clean shot proc it can hold(So like, 1, 2, 1, 3, 2... with all procs and a generic control setup). It'd make more since for the big hits to be the ones with the cast times anyway.

One might argue too much mobility, but gauss limiting mobility is kinda a joke anyway. If you don't have procs when it's time to move you have feint, or just turn gauss off and back on. I hope as much as the next guy that se owns up and goes 'alright, gauss/wm were a failure, they're gone', but if it's not going anywhere I think this would help a lot making it feel more playable.

[Doraymon_Prime]

This is how much time I can get to react for procs with Gauss Barrel on:



Holy shit, it's not easy...0.31 seconds to react...and skill queue looks like 0.5...You can't spam Split Shot and wait for procs...You are fucked right now with GB. It's pretty disgusting.

I wonder if cast times on slug and clean and instant split shot would be the answer. That gives you time to react to slug shot procs and while it'd be hard to react to clean shot procs...you wouldn't need to. You can go straight from slug shot back to split shot, if you got a clean shot proc it can hold(So like, 1, 2, 1, 3, 2... with all procs and a generic control setup). It'd make more since for the big hits to be the ones with the cast times anyway.

*cut some message off for 1000 words*.

i think the answer is to allow slug shot proc to stack 2 times
1.split shot -> split shot -> notice that slug shot proc from 1st split and even if this split also proc it, it not matter since it will stack 2 times-> slug shot -> split -> clean shot or slug depend on proc

if someone agree with this and have good English writing skill, please write the proper recommend for it

[Jeckyl_Tesla]

Is anyone else here having problems with ACT not parsing their Wildfire?

My ACT is registering it's use, but not it's damage whatsoever.

[jk315904]

Is anyone else here having problems with ACT not parsing their Wildfire?

My ACT is registering it's use, but not it's damage whatsoever.

Yes, I have been having this issue as well even with network parsing, it will register for the first wildfire but any Wildfire after that it will not.

[Velhart]

Is anyone else here having problems with ACT not parsing their Wildfire?

My ACT is registering it's use, but not it's damage whatsoever.

Let it run through your firewall, run as administrator, and keep network parsing up.

[Jeckyl_Tesla]

Let it run through your firewall, run as administrator, and keep network parsing up.

I have all of that already set up. IT was working before, but has suddenly stopped. I've fully updated and sorted everything out.

[Tsilyi]

This is how much time I can get to react for procs with Gauss Barrel on:



Holy shit, it's not easy...0.31 seconds to react...and skill queue looks like 0.5...You can't spam Split Shot and wait for procs...You are fucked right now with GB. It's pretty disgusting.

how much sks do you have as machinist? From the looks of things your lodestone is bard atm so I'm not 100% sure how accurate it is. with 540 sks on my machinst i don't have this kind of problem with such a small window :O is it your latency?