0000011: Autoexplore item sighting behavior: Autopickup on demand

(0000018)
dpeg (administrator)
2009-11-22 08:49

I once proposed this on SF and still stand by it. The comment back then was that x*Enter allows to do the same but it's more complicated, of course.

As for the key, I suggest to use Space or Enter.

Have to think what happens if marching to that item is interrupted: I suggest it simply gets added to the list of items to be autopicked up.

(0000020)
jpeg (manager)
2009-11-22 12:41

Agreed, also on adding said item to the autopickup list. Alternatively, we might want to create a new "go check out" list usable for corpses (if we don't have that one already), that might be a closer fit. Then again, piles already work that way (right?), so for a single item you will know right away whether you want to pick it up: autopickup list, it is.

(0000036)
Kyrris (reporter)
2009-11-23 14:40

jpeg: It used to. Trunk has recently lost that behavior in favor of travelling over the pile without stopping so you can read the contents. It's very aggravating.

(0000039)
jpeg (manager)
2009-11-23 19:37

I think that was a bug with the new greedy pickup behaviour that should be fixed by now.

(0000040)
Kyrris (reporter)
2009-11-24 00:00

It isn't. It travels to the stacks, but doesn't stop on them. I've set greedy_pickup, so if it retrieves something from the stack, it stops. But if I want to know whether there was an enchanted weapon in the mix, I have to interrupt autoexplore some fifty moves away, go to the ^p screen, and possibly travel back.

(0004140)
dpeg (administrator)
2010-04-12 00:51

Good idea, added to https://crawl.develz.org/wiki/doku.php?id=dcss:brainstorm:interface:interface#easy_picking_up_of_items_when_autoexplore_stops [^]

Kyrris: I just tested with (0.7) trunk and autoexplore will move to stacks of items and wait there. So this issue has been solved along the way.

Issue History
Date Modified	Username	Field	Change
2009-11-22 07:39	Siber	New Issue
2009-11-22 08:49	dpeg	Note Added: 0000018
2009-11-22 12:41	jpeg	Note Added: 0000020
2009-11-23 14:40	Kyrris	Note Added: 0000036
2009-11-23 19:37	jpeg	Note Added: 0000039
2009-11-24 00:00	Kyrris	Note Added: 0000040
2009-11-27 11:19	evktalo	Category	Feature Request => Interface Improvements
2010-04-12 00:51	dpeg	Note Added: 0004140
2010-04-12 00:51	dpeg	Status	new => closed
2010-04-12 00:51	dpeg	Resolution	open => done
2010-04-12 00:51	dpeg	Fixed in Branch	=> 0.7 development branch

Notes
(0000018) dpeg (administrator) 2009-11-22 08:49	I once proposed this on SF and still stand by it. The comment back then was that x*Enter allows to do the same but it's more complicated, of course. As for the key, I suggest to use Space or Enter. Have to think what happens if marching to that item is interrupted: I suggest it simply gets added to the list of items to be autopicked up.

(0000020) jpeg (manager) 2009-11-22 12:41	Agreed, also on adding said item to the autopickup list. Alternatively, we might want to create a new "go check out" list usable for corpses (if we don't have that one already), that might be a closer fit. Then again, piles already work that way (right?), so for a single item you will know right away whether you want to pick it up: autopickup list, it is.

(0000036) Kyrris (reporter) 2009-11-23 14:40	jpeg: It used to. Trunk has recently lost that behavior in favor of travelling over the pile without stopping so you can read the contents. It's very aggravating.

(0000039) jpeg (manager) 2009-11-23 19:37	I think that was a bug with the new greedy pickup behaviour that should be fixed by now.

(0000040) Kyrris (reporter) 2009-11-24 00:00	It isn't. It travels to the stacks, but doesn't stop on them. I've set greedy_pickup, so if it retrieves something from the stack, it stops. But if I want to know whether there was an enchanted weapon in the mix, I have to interrupt autoexplore some fifty moves away, go to the ^p screen, and possibly travel back.

(0004140) dpeg (administrator) 2010-04-12 00:51	Good idea, added to https://crawl.develz.org/wiki/doku.php?id=dcss:brainstorm:interface:interface#easy_picking_up_of_items_when_autoexplore_stops [^] Kyrris: I just tested with (0.7) trunk and autoexplore will move to stacks of items and wait there. So this issue has been solved along the way.

Relationships