Glad to have helped, though just be warned its not confirmed but sometimes pet attack first will screw up and have weird side effects I only use it on water or flying mobs.
Not sure why it does it, just keep an eye out and report in detail any errors or bugs you get so they can be fixed.
The only issue I have seen so far is one of the bots keeps getting stuck in a "returning to battle" mode. I assume this is due to the rail system after they die; however, this particular bot has yet to die nor did I set the rail. The only thing I noticed was that the Bot window was set to Element Client(the one with the problem) and another one of my windows was set to Element Client4. After exiting Prophet and reentering it, it did not grab my Element Client bot window, instead it grabbed Element Client4. I verified that the offset.ini had the correct window info for Element Client and not Client4. I went ahead and changed the window anyways to something completely different and have not had the issue since.
better 3.0 than 3.1, 3.1 always stuck returning battle or moving to corpse, i'm disbale moving to corpse but the bot still moving to corpse
Look at my post above, I have seen the same thing when running multiple bots with the "same" window name. Element Client, Element Client1, Element Client2... Renaming it to something else completely (BlahBlah BotName, Another Botname) seems to resolve this.
Look at my post above, I have seen the same thing when running multiple bots with the "same" window name. Element Client, Element Client1, Element Client2... Renaming it to something else completely (BlahBlah BotName, Another Botname) seems to resolve this.
I made a post about this quite a while ago with a solution, lemme dig it up
Quote:
hehehe I use textpad lol.
Oh yeah, when giving the bots titles, make sure they are 'unique' (and also don't have anything else opened with the same title of course). The bot uses WinGetProcess($APP_TITLE) and the default title match will detect any title that contains whatever is in $APP_TITLE.
So if you have one bot titled "bot" and another titled "bot2", when it is searching for the title "bot" it might detect either of the two clients, as both titles contain "bot". Therefore it is best to name one "bot1", and the other "bot2" to prevent any such issues.
using Opt("WinTitleMatchMode", 3) at the start of the code should solve this problem though.
Look at my post above, I have seen the same thing when running multiple bots with the "same" window name. Element Client, Element Client1, Element Client2... Renaming it to something else completely (BlahBlah BotName, Another Botname) seems to resolve this.
Yes, you are right you can't leave any window name as Element Client if you are planning to run more then one.
My mates and I have run into this a couple of times while running this. Sometimes, after loading the mob list it will simply skip the mobs your trying to target. It only seems to happen with specific mobs and it always follows the same pattern. Insert the mob and select mob name and it will "tab" through the mobs like normal. However, rather then attacking it will simply keep targeting until it finds one it likes and attack it. Sometimes this skips multiple mobs (all except the original one you targeted and added ) until it finds the one it likes. The only solution that I know of is to select all of the mobs in the area and add them, then hunt by name seems to cycle and identify correctly. Knowing PW from the devel side (I used to run HNG PW) I thought it might be related to how the mobs are "different" in the elements file. Since each type of mob (sacrificial, normal, magic resistant) is actually a different mob spawn in the elements the name may not be "exactly" the same. It may look the same to the client/bot but there are slight variances in the translation (etc).
Having said this, I am using the 3.1 on the same mobs that 3.0 seemed to have a problem with and I have not had to add all the mobs. I will try and report any mobs I see with this issue, maybe I can look through the latest elements and see if there is truly any issues with these mobs. Although I have yet to have the "work around" to fail me.
Ok the bot targets like this, to not be technical every mob has a specific code attached to it identifying it. By tabbing through the mobs near you the bot is searching for the specific mob you selected (looking for that code again) When it finds a mob that matches to one of the codes in the list it will attack it. If you want it to attack every mob in the area either add the mobs you want to attack then select "Hunt By Name" Or pick every individual mobs. Really you only need 3 mobs selected in the list to bot at a comfortable pace.
Ok the bot targets like this, to not be technical every mob has a specific code attached to it identifying it. By tabbing through the mobs near you the bot is searching for the specific mob you selected (looking for that code again) When it finds a mob that matches to one of the codes in the list it will attack it. If you want it to attack every mob in the area either add the mobs you want to attack then select "Hunt By Name" Or pick every individual mobs. Really you only need 3 mobs selected in the list to bot at a comfortable pace.
Yes sir, I completely understand this. I was just saying for 'certain' mobs this isn't working. I have only found a few (read that as 2-5 different mobs) of these throughout the world. I have more then a little know how in the back side of PW (database, mob creation, mob spawning, map editing) and I was just sharing my thoughts on the issue
