![]() |
#1 |
Knight
Join Date: Jul 2009
Posts: 651
![]() |
Autopickup while running
Is there anyway to enable autopickup setting to work also when you are running? I find it somewhat annoying and cumbersome to be constantly having to move back to an item that you run over while keeping shift down, just to pick it up. Waste of real time, my optimization OCD doesn't like it.
![]() Cheerios |
![]() |
![]() |
![]() |
#2 |
Vanilla maintainer
Join Date: Apr 2007
Location: Canberra, Australia
Age: 56
Posts: 9,350
Donated: $60
![]() ![]() |
OK, so is this a recurrence of this bug (ie you hit run one time and then end up running over and past the item), or something else?
__________________
One for the Dark Lord on his dark throne In the Land of Mordor where the Shadows lie. |
![]() |
![]() |
![]() |
#3 |
Adept
Join Date: May 2020
Location: Argentina
Posts: 189
![]() |
This happens all the time in Android. The port has a fake running mode, every direction is transformed to run+direction.
If there are monsters in LOS, autopickup is cancelled. I think that sometimes if you step back it works. It's normal behavior ? |
![]() |
![]() |
![]() |
#4 | |
Knight
Join Date: Jul 2009
Posts: 651
![]() |
Quote:
Has to do with running/autopickup code I guess. Super annoying to run a whole corridor back just to go pick it up ... walking not running the final step ... |
|
![]() |
![]() |
![]() |
#5 |
Vanilla maintainer
Join Date: Apr 2007
Location: Canberra, Australia
Age: 56
Posts: 9,350
Donated: $60
![]() ![]() |
So what should happen is that any run is interrupted if the player is next to an item. Reading the current code, it looks like the run should be interrupted if the player is about to step on an item (which is the same thing in corridors). How does what you're seeing compare to this?
__________________
One for the Dark Lord on his dark throne In the Land of Mordor where the Shadows lie. |
![]() |
![]() |
![]() |
#6 |
Knight
Join Date: Jul 2009
Posts: 651
![]() |
The interrupt happens, but the annoyance is if you only move with run with fast-in-real-time, the next click won't pick it up even though it just steps on top of it. It is just a quality of life issue, but it is quite annoying as it happens repeatedly. As far as I can tell, autopickup while moving does not consume energy does it? So not sure why the behaviour should be different.
|
![]() |
![]() |
![]() |
#7 |
Knight
Join Date: Jul 2009
Posts: 651
![]() |
Just to return to this issue, I think I figured it out.
So if you start running, step on an item that is on your autopickup (=g, gold, matching, etc.), you are interrupted after move before autopickup. I think if the autopickup would be zero energy cost, then the autopickup should trigger before the interrupt. |
![]() |
![]() |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
hotkey to use running ? | ninmonkey | Vanilla | 4 | October 14, 2014 17:42 |
Autopickup/always_pickup issues | MarvinPA | Sil | 35 | October 15, 2013 20:57 |
Autopickup and squelched items | fph | Development | 5 | October 21, 2011 10:26 |
(not) running into molds | half | Vanilla | 12 | May 24, 2009 09:04 |
Re-thinking running (away) | buzzkill | Development | 2 | March 8, 2009 08:42 |