Tweet
Ok I like streamlined superfast playstyles, and couple things about the pathfinder annoys me. I will just try to make the changes for myself if nothing else, but please feel free to give feedback / opinions / ideas.
Search range:
Computing power is insane nowadays. Is there a reason it is limited? Why do I have to manually run through explored areas to be closer to unexplored ones to auto explore again? Total MEH, will try to find where this is set to put it to 255 or something. My first glance found a max_pf_radius set to 100, but I swear it is much less in the actual explore function, will have to check further. Especially since I can mouseclick muuuuch further (I assume the actual 100 radius 500 path steps max).
Doors:
I think having the autoexplore be "careful" isn't really the best option, I prefer it to be autoEXPLORE not autoexplore-but-nah-lets-not-look-behind-that-door-ever. Carefulness should be the player, not the pathfinding algorithm. I already made a shortcut for opendoor next to my explore button, but problem is the autoexplore won't even stop next to the door easily always ... To be honest, for myself, I'd be happy if the explore automatically stops next to a door, but if you press it again (or for first time) NEXT to a door, it will open the door and proceed from there until disturbed as usual. Or at the minimum, if it finds and stops next to a door, if there is no explorable areas found on next action, open it and proceed from there.
Traps:
The autoexplore is sometimes obviously super stupid when it comes to bypassing trap grids. You can literally be next to an open corridor spot next to a trap, and it returns a "confused" message if you try to explore again. Maybe this will be getting too complex for a basic explore function to change though, so not too fussy about this one. MAYBE a "if pathing step = trap, check if any grid next to step1 are empty as well as next to step2 and use that". Again though, not a big issue.
Lets see what I find in the code ...
Search range:
Computing power is insane nowadays. Is there a reason it is limited? Why do I have to manually run through explored areas to be closer to unexplored ones to auto explore again? Total MEH, will try to find where this is set to put it to 255 or something. My first glance found a max_pf_radius set to 100, but I swear it is much less in the actual explore function, will have to check further. Especially since I can mouseclick muuuuch further (I assume the actual 100 radius 500 path steps max).
Doors:
I think having the autoexplore be "careful" isn't really the best option, I prefer it to be autoEXPLORE not autoexplore-but-nah-lets-not-look-behind-that-door-ever. Carefulness should be the player, not the pathfinding algorithm. I already made a shortcut for opendoor next to my explore button, but problem is the autoexplore won't even stop next to the door easily always ... To be honest, for myself, I'd be happy if the explore automatically stops next to a door, but if you press it again (or for first time) NEXT to a door, it will open the door and proceed from there until disturbed as usual. Or at the minimum, if it finds and stops next to a door, if there is no explorable areas found on next action, open it and proceed from there.
Traps:
The autoexplore is sometimes obviously super stupid when it comes to bypassing trap grids. You can literally be next to an open corridor spot next to a trap, and it returns a "confused" message if you try to explore again. Maybe this will be getting too complex for a basic explore function to change though, so not too fussy about this one. MAYBE a "if pathing step = trap, check if any grid next to step1 are empty as well as next to step2 and use that". Again though, not a big issue.
Lets see what I find in the code ...
Comment