minor bug - can shoot but not target

[PowerDiver]

Thanks to overpowered randarts, I have a heavy xbow with might+3 that lets me shoot 20 squares away. But the targeting code won't let me target that far. I can hit if I can aim using direction keys.

So should the range be reduced or targeting be changed?

[Tiburon Silverflame]

Interesting problem.

Best solution would appear to me to be:

a) Targeting examines all your spells and equipment, and determines the max range for any attack.

b) If something has a shorter range, you get an Out of Range warning. I know this already exists for some attacks.

My feeling is, there's probably insufficient smarts in the targeting.

[Derakon]

I'd say that a better solution would simply be to cap the max range on missile weapons so it doesn't exceed your sight range.

[PowerDiver]

I'd say that a better solution would simply be to cap the max range on missile weapons so it doesn't exceed your sight range.

There is always detection instead of sight. Or ESP. I have no idea whether the monster I shot was in sight range.

Spells have a maximum range. Targeting is set up based on that range. It is only with the new ranges and an x7 launcher that the problem appears, I believe. I am pretty sure that sight range exceeds spell range, but that may be a confusion on my part about targeting in the past.

I think the question is whether missiles should be capped at spell range. I think that, at least with attack-then-target mechanics, targeting should use the range for the attack rather than let you choose out of range and then give an error. Of course, that doesn't apply to my problem of not being able to target in range, but it would probably get fixed coding for the general situation.

[Timo Pietilä]

Spells have a maximum range. Targeting is set up based on that range. It is only with the new ranges and an x7 launcher that the problem appears, I believe. I am pretty sure that sight range exceeds spell range, but that may be a confusion on my part about targeting in the past.

Spell max range is your LoS range (not counting splash damage). Any spell requiring targeting stops two squares short of that max range, but any LoS spell affects max range.

Testing x7 launcher gets exactly max visual range (20 grids), but targeting is possible way longer away than that. I just tested by targeting a grid about 300 feet away (ten grid off visual range). Game complains that "Target out of range. Fire anyway [y/n]" and when pressing y it shoots but obviously doesn't reach target.

[PowerDiver]

Testing x7 launcher gets exactly max visual range (20 grids), but targeting is possible way longer away than that. I just tested by targeting a grid about 300 feet away (ten grid off visual range). Game complains that "Target out of range. Fire anyway [y/n]" and when pressing y it shoots but obviously doesn't reach target.

I'm not talking about positional targeting. When you cycle through monsters in basic targeting, I did not get the option to target the monster I could shoot down the corridor.

[Timo Pietilä]

I'm not talking about positional targeting. When you cycle through monsters in basic targeting, I did not get the option to target the monster I could shoot down the corridor.

OK. I wondered what kind of problem you had because I haven't that problem myself. Testing confirms that you can't automatically target something that is further than two grids short max visual range: shoot nearest says "no available target", and pressing "*" which should automatically select nearest doesn't select anything.

[Tiburon Silverflame]

If you set targeting range == max range of any attack, and the target is out of attack range for that attack, then an alternative is to treat this the same as when you've got "repeat last target" as a default, but that last target moved out of range or even broke LoS.