>>288
I have a long list of TODOs, here is a WIP
-Right click if we found a bitmap but there are "x other options", and click the fishing spot only
(not for objects because there could too often be "x other options". bitmaps are more certain and will always overlay
-Get first point in webwalk paths and turn the camera
- use "Walkstep" instead, and add chance to turn camera on early and ending points, even if screnwalking
- Investigate the events in webwalker to do this, possibly (put a low % chance)
-Add checking for resources i.e. feathers and quitting on none
- In future, make it sell fish and bu ymore resources :))
-Add a mode to use the color detection and TPA mean to use colored boxes
on fishing spots instead of BMPs. May be weaker in areas with multiple
types of fish/spots e.g. catherby, but will be more accurate in general
to hit the fishing spots, and most places have only one type. plus you
can set runelite to only highlight specific fish you last fished.
-Make banking step be done with "states"/"stages" with ability to detect them, and store it as a variable per run. then it can start at any point
-Make the states/stages exit after each stage back to the main loop so antibans and other procedures like combat checks, etc can be run.
-Move to all srl.* funcs for randomness, etc
-Add bitmap for new locations
- barb village trout/salmon
- barbarian fishing (members)
-Add a color finder for the water texture (or lava, in future, make it per-location
-Use this to check if its nearby the detected fish bitmap, to increase confidence
-Make all data for each location stored in a structure (record)
- preferred camera angle for facing fish spots
- fish bmps
-custom offset, just in case we can detect an area that is not the center
- item names
- webwalker locations (bank, fish spot)
- resources (i.e. feather/bait)
-Detect combat and run to bank
-Add "Strategies", so it will randomly select whether to do certain things with some randomness based on username as seed, skewed heavily to the "better" ones.
- rotate (or not) camera towards clicking points
- keyboard or mouse for rotating camera
- SNAKE or NORMAL strategy for shiftdrop/deposit
- bank all or right click each
- left click use menu or right click climb
- add (or dont add) certain antibans
- mm2ms or scroll zoom to find certain objects
-Make the "reaction" as part of an antiban, and add it to the start of each procedure in the main loop. track it as a time, increasing with a fatigue based on the running time. So it will keep looping and not "reacting" to things it needs to do if it does not have the reaction time. and reduce it each time a procedure runs, with a truncated gauss.