Minor bug in 'n' command

[fyonn]

Hiya,

Just wondering if I've found a minor bug in 3.1.2v2. I've got a ranger who's been hit by confusion breath and is thus confused. I had a go at trying to zap the bronze dragonfly with some spare wands of sleep monster I had. obviously the 'bolt' of sleep went in the wrong direction, but I pressed 'n' to keep trying and every bolt then went in the same direction as the first. if I just 'a'imed the wand it would go in a different direction each time.

I tried it with some rods of light too, and the same happened. each time I used 'n' to repeat the last command, it repeated the same random direction. same with firing arrows too. I even exploited it by firing arrows at random until one went in the right direction and then just repeated that killing the fly and a number of air hounds.

can anyone else replicate it?

dave

[konijn_]

Hiya,

Just wondering if I've found a minor bug in 3.1.2v2. I've got a ranger who's been hit by confusion breath and is thus confused. I had a go at trying to zap the bronze dragonfly with some spare wands of sleep monster I had. obviously the 'bolt' of sleep went in the wrong direction, but I pressed 'n' to keep trying and every bolt then went in the same direction as the first. if I just 'a'imed the wand it would go in a different direction each time.

I tried it with some rods of light too, and the same happened. each time I used 'n' to repeat the last command, it repeated the same random direction. same with firing arrows too. I even exploited it by firing arrows at random until one went in the right direction and then just repeated that killing the fly and a number of air hounds.

can anyone else replicate it?

dave

Yes, I've never considered abusing it though, excellent thinking !

T.

[fyonn]

Yes, I've never considered abusing it though, excellent thinking !

T.

I'm a computer security architect. when I see a bug, my first thought is wondering how it can be exploited

dave

[fyonn]

Incidentally, if we're looking at the 'n' command, one thing I might like to see changed is how it works with ranged attacks and targetting. One thing I sometimes do is target monsters with either magic or a bow and just target the closest monster using the apostrophe key "'". pressing 'n' fires another attack at it until it's dead. pressing 'n' again then puts me at the targeting prompt, rather than just targeting the next closest monster.

I'd prefer this latter behaviour, anyone else?

dave

[PowerDiver]

Incidentally, if we're looking at the 'n' command, one thing I might like to see changed is how it works with ranged attacks and targetting. One thing I sometimes do is target monsters with either magic or a bow and just target the closest monster using the apostrophe key "'". pressing 'n' fires another attack at it until it's dead. pressing 'n' again then puts me at the targeting prompt, rather than just targeting the next closest monster.

I'd prefer this latter behaviour, anyone else?

dave

If I am in "target closest monster" mode, I would prefer to switch targets when the close one runs and another steps closer even before killing the first.

I definitely think that 'n' after 'h' should give this behavior. To me, that is clearly repeating the 'h' command rather than repeating firing at a particular target.

[fyonn]

If I am in "target closest monster" mode, I would prefer to switch targets when the close one runs and another steps closer even before killing the first.

I definitely think that 'n' after 'h' should give this behavior. To me, that is clearly repeating the 'h' command rather than repeating firing at a particular target.

yes, I agree. repeating (ranged attack at) closest monster, whether by missile weapon, spell, wand or rod should always be aimed at the closest one, regardless of who moves where. both with the 'h' command and the ' targeting command.

dave

[Nick]

I can see arguments both ways - I often want to finish off the orc I've damaged rather than switch to a new one.

As regards the original bug - fixed in FA. Of course

[Timo Pietilä]

I can see arguments both ways - I often want to finish off the orc I've damaged rather than switch to a new one.

As regards the original bug - fixed in FA. Of course

I think it is fixed also in vanilla nighties. At least that is a old bug and I have a vague memory about it being fixed.