shift-tab: autofight_nomove or hit_adjacent?

[galehar]

The shift-tab command is called AUTOFIGHT_NOMOVE, and it calls a lua function named hit_adjacent. It's the same thing anyway right? Actually, it used to be "hit anything adjacent", and I changed it to "autofight without moving". Which means if there's no adjacent monster but one at range and you have something to throw in your quiver, you'll throw it. Which means you can use shift-tab to fire at approaching monsters and fleeing ones too. I find this extremely handy. If you don't, you can revert to the old "hit adjacent" behaviour by setting autofight_throw_nomove to false.

Related to this, there's also the autofight_throw option which has been added recently. Makes you throw stuff by just tabbing. There's even a lua function that you can map to a key to toggle it in-game.

Personally, I think the autofight_throw can be useful for a dedicated thrower. There are some cases (corridor, doorway) where you want to stay put and might want to use the turn for something else than throwing when there's no adjacent monster. However, I'd rather play slower or empty my quiver rather than changing autofight_throw_nomove. Seems like a much narrower use-case than firing at approaching/fleeing monsters.

Feedback and suggestions welcome.

[Patashu]

Could Ctrl+Tab be used for the third flavour of tabbing?

[jejorda2]

There was a suggestion at some point to repeat autofight until a new enemy came into view or hp got low enough to see warnings. Maybe ctrl-tab could go to that one, if it ever goes in.

[Patashu]

There was a suggestion at some point to repeat autofight until a new enemy came into view or hp got low enough to see warnings. Maybe ctrl-tab could go to that one, if it ever goes in.

I'm not particularly fond of this one because there are a lot of other things that might happen that would be cause to stop early - like discovering one of your enemies has a branded weapon (distortion/venom especially), or getting coated in sticky flames, or getting slowed, or...

[galehar]

Could Ctrl+Tab be used for the third flavour of tabbing?

Nice idea. Unfortunately, it doesn't seem to be handled by console. ctrl-tab returns the same key code as tab (9)

[sardonica]

I would prefer <ctrl><alt>Tab to go through the entire dungeon level, killing any monsters until HP is low, butchering them for food if "very hungry," and resting when no enemy is in LOS.

[XuaXua]

I think it would be amusing for tab to transform into autoexplore 'o' when there are no enemies visible.

[sardonica]

I think it would be amusing for tab to transform into autoexplore 'o' when there are no enemies visible.

Making "holding down tab" even more fun and interesting!

[bobross419]

Moar tab is good tab.

[sardonica]

I actually did a series of runs recently with a beserker mino, holding down tab when an enemy entered LOS and not stopping till death or the HP warning.

Got one of them all the way to Lair:8

[Deimos]

I agree with having tab turn into autoexplore when nothing is in sight. There is no reason not to do that.

[crate]

I agree with having tab turn into autoexplore when nothing is in sight. There is no reason not to do that.

Maybe you don't want to go running off after you fight stuff. Tab in zot:5 gets really really dangerous if you accidentally press it after you've killed everything with this proposal.

[Deimos]

True. Maybe it couldn't change to autoexplore until the user lets go of the key? Not sure how that would work.

[bobross419]

True. Maybe it couldn't change to autoexplore until the user lets go of the key? Not sure how that would work.

Seems like a pointless change when auto-explore takes exactly 1 keypress. There are a lot of other auto-explore interruptions ("This is deep water" on an Octopode anyone?) that are way more annoying than having to click 1 extra button after a fight. Not to mention that a lot of the gods that tabbers will be using like corpse sacrificing.

[Blade]

If you want to tab-explore, macro o\{9} to some key. Combining two distinct, useful functions into one dangerous, unpredictable mess (which that macro usually is) is a bad idea.