DSRyan

That's where the "community" is doing things wrong... 1) Closed Source (Understandable), but if you're going to have it closed source at least make the bot modular so that there is a core which contains all of the core functions, like moveto(), getcoords()... etc and then everything else is done by scripts, this would make the bot way more flexible and stable as features, fixes and entire routines can be worked on by anyone, rather than just 2. It would mean that the suggestions I made here and in the other post, I could add for myself and more importantly for the community. 2) Working on the wrong things first... pathing, chickening, avoidance, NPC use, stashing should all be priority followed by recipes, map rolling, master quests and finally progression. Progression is a long and laborious task to do. It doesn't take anyone long to do it themselves, it's a waste of developing time to prioritise these. It's also the wrong way of focusing in terms of a business perspective (money for alk) as you want to perfect the main functionality before you work on the big scripts.

Hi, Currently we have no option to avoid breaches, some people are wanting the bot to chicken on breaches, I propose: A better, superior and ultimately more efficient option would be to create an x by x "do not enter" box around the breach. If the next movement is supposed to go through the box or into the box, the avoidance system would recalculate a new set of coords, close to the box but outside. Currently the "Chicken on monster names" only supports chickening, I think this should be revamped to have some more functionality. One feature you could add is [ignore] which if appended to the end of a monster name: Voll, Emperor of Purity[ignore] would make the bot just ignore the monster, as if it doesn't exist and as such would just bypass it. Another feature would be basically the same as breach avoidance that I just mentioned, so we could add: Voll, Emperor of Purity[50] for an example which means it would be a 50x50 box around Voll's original/first detected coordinates and it would path around that 50x50 box. The two above options could be put together so you have Voll, Emperor of Purity[ignore][50] which means it would stay 50x50 away from the original coordinates but if the boss comes out and follows the bot would still just ignore the boss and under normal circumstances it would get away and leave the boss all on his own.

Being that everything is based on coordinates the logic behind scaling it up/down shouldn't be too difficult so I'm not sure why this wasn't an option from the start. Of course I don't know the exact inner workings of the bot so without seeing the code I could be completely wrong. EDIT: Untested but you could probably edit the coordinates.ini file and update all of the coords, however it would certainly be much easier just scaling the coordinates The logic required would be something like: # Hardcoded resolution just for the example, however this bit should be grabbing the window/dekstops resolution. $WinHeight = 1920 $WinWidth = 1080 $WinResolution = $WinHeight & "x" & $WinWidth Switch $WinResolution Case '640x360', '852x480', '720x405', '848x480', '960x540', '1024x576', '1280x720', '1366x768', '1536x864', '1600x900', '1920x1080', '2048x1152', '2560x1440', '2880x1620', '3200x1800', '3840x2160', '4096x2304', '5120x2880', '7680x4320', '15360x8640' ;16:9 $UpdatedXCoord = ($WinWidth / 1920) * $XCoord $UpdatedYCoord = ($WinHeight / 1080) * $YCoord Case '320x200', '640x400', '1280x800', '1440x900', '1680x1050', '1920x1200', '2560x1600', '3840x2400', '7680x4800' # 16:10 $UpdatedXCoord = ($WinWidth / 1680) * $XCoord $UpdatedYCoord = ($WinHeight / 1050) * $YCoord Case '640×480', '800x600', '960x720', '1024x768', '1152x864', '1280x960', '1360x1024', '1400x1050', '1440x1080', '1600x1200', '1856x1392', '1920x1440', '2048x1536', '3200x2400', '4000x3000', '6400x4800' # 4:3 $UpdatedXCoord = ($WinWidth / 1440) * $XCoord $UpdatedYCoord = ($WinHeight / 1080) * $YCoord Case '1280x1024' # 5/4 $UpdatedXCoord = ($WinWidth / 1280) * $XCoord $UpdatedYCoord = ($WinHeight / 1024) * $YCoord Case '768x1024' # 3/4 $UpdatedXCoord = ($WinWidth / 768) * $XCoord $UpdatedYCoord = ($WinHeight / 1024) * $YCoord Case '1360x768' # 85/48 $UpdatedXCoord = ($WinWidth / 1360) * $XCoord $UpdatedYCoord = ($WinHeight / 768) * $YCoord Case Else #Throw up an error regarding unsupported resolution. EndSwitch I haven't bothered with the very rare aspect ratios but I've done most of them, I've also done most of the common resolutions.You could quite easily setup a function to feed original coordinates in with the resolution and return the adjusted coordinates using this method.

A bot's main purpose is to do automated tasks with as much efficiency as possible yes, this is efficient. If someone wants lots of chisels or glassblowers baubles then this is very very efficient for them, just because you don't need a use for it doesn't mean others won't need a use for it. I could say the exact same thing about clearing corrupted areas or activating essences or many of the other options, just because I don't use them doesn't mean they shouldn't be an option for the users. It's not distracting for users, they can simply decide yes or no for that option/feature. It's also not distracting for developers either as the logic behind both of these is pretty simple and easy; especially comparing the complexity to the likes of chaos recipe and as such shouldn't take long at all to add. The bot isn't open source as as such I can't dive into the code and tweak to my liking, that's why options like this should be available.

For you they're stupid, but for some users they may want them. If you feel it's a waste of time there's no need for you to use that specific feature. That's why it would be an option... Yep, exactly. It would make the stashing system way customization for the user, allowing them to have their stashing exactly as they like and want.

Hi, I'm wanting a revamp of the stashing system to make it overall way more human like but more importantly much better over time. What I'd like is the ability to define what tab each item in the picket goes to, obviously this could still be blanket stash by assigning all uniques to one tab, all gems to another, all cards to another, all rares to another... etc Currently the picket has items like: [Type] == "Portal" [Category] == "Map" # [StashItem] == "true" [Rarity] == "Unique" # [StashItem] == "true" [Type] == "Albino Rhoa Feather" # [StashItem] == "true" What I'd like it changed to look like would be: [Type] == "Portal" [StashTabs] == "3" [Category] == "Map" [StashTabs] == "4" [Rarity] == "Unique" [StashTabs] == "1, 2" [Type] == "Albino Rhoa Feather" [StashTabs] == "5" It would need some picket lines for chaos recipes, currency and several other things but that shouldn't be hard at all, just reuse the current code and instead of making it check the config file/gui make it check the picket file. [Category] == "ChaosRecipe" [StashTabs] == "6, 7" To humanize this more you should do it so it to cycle through stash numbers in a random order, comparing the found items with the picket and then any item that has been found to go into the current stash number would be stashed. To humanize this more, you could add a 95%~ chance of stashing each item on it's first stashing routine and then make it repeat the stashing routine but this time make sure it has a 100% stashing chance. I'd also like to request some more recipes.. - Automatic recipes for Gavels + Whetstone + Level 1 map to get a chisel. - Automatic recipes for superior flasks to be collected until the stash tab has 80%+ worth of flasks stored, it should then selectively pick the right flasks to 40%, but obviously it can't be lower than 40% and then sell these to a vendor to get glassblower's baubles. - The same as above, but for gems could be done too. I'm sure there are other good vendor recipes that I'm not aware off.

There's no need to be rude about it... maybe he didn't know that? His request still has some validity. Like divination cards, I store mine on their own stash tab and I too would like it. This would be perfect, I want gems with % quallity to go to 1 tab, gavels to go to 1 tab, chaos recipes to go to 1 tab, currency to go to 1 tab, uniques to go to 1 tab, rares to go to 1 tab, normal gems to go to 1 tab, superior flasks to go to 1 tab