search

kolton / d2bot-with-kolbot

d2bot game manager by D3STROY3R with kolbot libs by kolton for d2bs
346 stars 332 forks source link

passive rushee doesnt talk to cain at a2 #720

Open Sherloock opened 6 years ago

Sherloock commented 6 years ago

So i have 1rusher and 4rushee (one of them doing the quests Config.Rushee.Quester = true) the other 3 is passive (Config.Rushee.Quester = false), they cant bypass a2, beacuse they cant go to the palace portal. If i speak with Cain manually everything works fine.

DarkHorseDre commented 6 years ago

It's been a long time since I rushed but I had same issue. Not sure of the cause but I had to set them all to quest. I have seen fixes to this area recently so ensure you are at latest trunk release.

krazy03 commented 6 years ago

https://github.com/kolton/d2bot-with-kolbot/issues/668#issuecomment-419012572

I had same problem, this is my fix.

Basically, when rusher bot says a3, they will talk to atma > enter portal for jeryhn > go back out portal > talk to meshif go to act 3

DarkHorseDre commented 6 years ago

Guys, is this only an issue with non questing rushees? (therefore, setting all to questing avoids the issue?)

krazy03 commented 6 years ago

yes only with non questing rushees, the problem is if you have more than 3 rushee with quest set to true they get in each other ways, and what was happening was that some wouldn't get the items and the others would only get 1 out of items needed to make staff... so if you had 5 rushees no one could get full staff because they all had only 1 part or none not sure why it happens. I'm guessing script doesn't check to make sure quest item is gotten or it fails to get it but no error appears.

DarkHorseDre commented 6 years ago

Ah ok - thats why I didnt fail as I only had 1/2 questing for socket :)

Yeah there isn't any bi-directional communication between rusher and rushee and the rusher doesn't know which rushee has which component for quest. The staff quest is the tricky one (so would act 3 organs but rusher can bypass).

Its good you guys found a workaround as coding to handle this properly would be a bit of work I'd imagine!