What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[help request] How to make the bot not just skin 2 mobs, and then go fight more?

Status
Not open for further replies.
R

roneo1

Member
Joined
Mar 21, 2014
Messages
480
Reaction score
20
Is there any way to prioritize skinning unless of course a mob is attacking you? It always skins only 2 mobs because there's mobs around to attack, I've looked through the bot settings and cant seem to find how to do this, is there a fix for this? I've googled around the problem and I've seen many other users with the same problem but no solution, someone has a fix to this?

Or is there at least a way for the bot to not attack mobs within a certain range as long as they're unskinned mobs?

Anyway you get the issue, I'd like to not pull more mobs as long as there are unskinned mobs around, if a mob attacks me I guess thats fine to attack it back but it shouldnt pull if there's stuff to skin.
 
honorbuddy wont skin while in combat, the only time its going to skin is during looting and that doesnt happen while your killing mobs.
 
CodenameG said:
honorbuddy wont skin while in combat, the only time its going to skin is during looting and that doesnt happen while your killing mobs.
Click to expand...

Alright then what is the solution to this? An extremely large number of dead mobs remain unskinned until they despawn (actually more mobs despawn than the ones that are skinned) and there appears to be a large number of people encountering the same problem as me, so can someone look into this?
 
Last edited:
the only thing i can recommend is to rework your profile.
 
Just wanted to contribute to this as I have experienced this issue first hand also.

Current situation is as follows:

- I kill 3 wolves - I am no longer in combat, there are other mobs in the area but not within agro range of me
- The bot loots all 3 mobs and then starts skinning the mobs
- The bot skins only 2 of the 3 dead mobs and then moves to interact with another of the nearby mobs and engages in combat

What I would like to have happen:

- I kill 3 wolves - I am no longer in combat, there are other mobs in the area but not within agro range of me
- The bot loots all 3 mobs and then starts skinning the mobs
- The bot skins all 3 of the dead mobs and then moves to interact with another of the nearby mobs and engages in combat

There doesn't seem to be a way to rework the profile to account for this, maybe I'm wrong? but the Bot only ever skins a max of 2 corpses before it then runs off and gets its self in combat with another nearby mob. The end result is that there are an amount of dead corpses that get left un-skinned and then de-spawn

Thanks
 
simple, just turn off pull more this will result in killing the wolf then skinning it over and over again
 
Just turned off the "pull more" option so going to test, although I was under the impression that the pull more feature pulled more mobs while you are in combat, not while you are out of combat and looting.

Ill test a bit more with the option turned off in Singular and update with results.

Thanks for feedback though
 
Can confirm issue still exists.

Killed a pack of 4 Nagrand Prowlers - Bot loots all, skins 2 and then moves to engage in combat with another mob nearby

Thanks
 
i've had this same issue since day 1 as well. bot never skins more than 2 before continuing to farm
 
So I've been watching this closely for a long time, and I will reiterate exactly what extraview said, there is no doubt that this is what's happening.

I have tried in areas populated with more mobs and some with less and this REALLY needs a fix, It's basically skipping half the skinnable mobs as soon as it kills a pack it just skins 2 and goes to fight more. It doesn't matter how you change the profile it's just the embedded bot logic of skinning.

Current situation is as follows:

- I kills 3 wolves - I am no longer in combat, there are other mobs in the area but not within agro range of me
- The bot loots all 3 mobs and then starts skinning the mobs
- The bot skins only 2 of the 3 dead mobs and then moves to interact with another of the nearby mobs and engages in combat

What should be happening:

- I kill 3 wolves - I am no longer in combat, there are other mobs in the area but not within agro range of me
- The bot loots all 3 mobs and then starts skinning the mobs
- The bot skins all 3 of the dead mobs and then moves to interact with another of the nearby mobs and engages in combat. There is simply no reason to pull more mobs if there are more targets to skin, and enemy mobs haven't aggroed you.

For the devs: this is most obvious when it kills several mobs, you will see it go kill more stuff after skinning only 2 mobs. The ONLY time when it skins everything is if there's mobs nowhere in sight/in reasonable combat range and even so you can see the bug, it skins 2, mounts up to go fight more, then it dismounts and comes back to skin the mobs, but this rarely happens because it always has more targets around to pull after skinning only 2 mobs.
 
Last edited:
Still happening with build 796 of HB, no progress on this? It's 4 months old.
 
It seems related to the own-tagged skinning I suppose.

If you want to test it - run to the Iron Front near the flightmasters - usually there is tons of dead iron horde and plenty of died wolves, ready for ninjaskin.

Then you can witness how the bot can ninja skin all the corpses around, if not engaged in combat. Have seen it ninja more than 5-6 in row. On the opposite note - while solo farming, do not skin more than 2 own-tagged corpses.

P.S.: Replaced my post here, since obviously I have replied in the wrong thread ;)
 
This issue is still present, can we get an update on this please?
 
The development staff does not give ETAs for repairs on particular bugs.

We can say, however, that the reason this issue remains open is that users with the problem are remiss in posting full logs of the event. Internally, the problem cannot be replicated, so logs are absolutely required if the issue is to eventually be addressed.

cheers,
chinajade
 
So any news on this? i'm having this issue as well and seeing the thread being more than a year old, i hoped there would be a fix.
Anyone else has this?
 
Status
Not open for further replies.
Back
Top