Cast from out of range problem

I'm not sure if this is a problem for other DGs or not, or if this is a product of lag, but I found that if you play regulus and use mark on a distant enemy so that reg persues, you won't be able to issue a snipe command on that target without first issuing a move command - it doesn't seem to abort the attempt at marking until you actually catch up to and mark the enemy.

I'd expect that the snipe command to abort the mark command.

1,547 views 3 replies
Reply #1 Top


I'm not sure if this is a problem for other DGs or not, or if this is a product of lag, but I found that if you play regulus and use mark on a distant enemy so that reg persues, you won't be able to issue a snipe command on that target without first issuing a move command - it doesn't seem to abort the attempt at marking until you actually catch up to and mark the enemy.

I'd expect that the snipe command to abort the mark command.

This happens whenever you try to use two different ranged abilities on the same demigod. It happens with UB and Spit/Grasp as well. (Grasp is actually classified as ranged because it's range is 5 meters, instead of 4, which makes it not quite melee)

Reply #2 Top

I would classify this as a usability issue then. Since move orders can cancel an 'old' cast, so should casting a new ability.

This one has screwed me out of easy kills...

Reply #3 Top

As said UB has the same prob with spit and grasp. Damn annoying and should be fixed. As said it costs you kills