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

[Party Plugin] SimpleFollow - Multi-Bot Party Plugin

Hey all,
can someone tell me how I have to modify the code to...

1.) move my toons exactly top the same coordinates as my leader

2.) to let them follow faster (wait less ms) when the Leader starts to move

Thanks
itraxx


modify your trinity settings for trash mobs for followers i.e. Main: 2mobs followers: 4mobs.... or change the range.
 
This plugin couple with let me drive has been fantastic for farming bounties and rifts, manually playing the leader while my bot follows. Tradable legs for 2hours coupled with enchanting means easy to swap legs between the two accs and re-roll main stat is need be :) +1
 
Followers not working

Rrrix - Please help.. :(

Not sure what happened here, if it is new trinity, new db, or something else.. I updated a few things today now my followers are completely useless. My followers dont even care what the leader is doing. The 3 followers stand around alot, leader takes off fighting and the 3 followers chill with each other, walk around a little, stand a little more... The ONLY time they are of any use is when they enter a boss battle and trigger the boss confirmation screen and they enter and fight.. Sometimes they will teleport to leader and join in a quick fight until the fight is over then they go back to chilling while the leader moves off fighting other mobs.
 

Attachments

I really have a big problem with this plugin. Everytime i run it after a few minutes my D3 follower game crashes View attachment 122896 . When not running Simple follow there is no problem... I tried reinstalling the follower game directory it didnt help... Please help anyone?

Also Logs of follower if needed?
 

Attachments

Last edited:
DB Navigation is weird.

Followers can sometimes fail to follow and just patrol back and forth to leader, seemingly unable to create a path to leader, although grid segementation resets quite a bit.

This is especially problematic in the Towers and/or Core.

The worst of all, is that the bots wouldn't loot any legendaries or other items even if they were in front of them during this limbo phase.

--------------------------------------------

More of a plugin related issue:

Sometimes, when the leader TP back to town, the followers do the same. But it seems that the followers take the portal back again to the original area.
They eventually teleports to leader when the leader moves on to another waypoint.

Thanks,
 
When running a profile on leader the followers game client crashes when rejoining the game most of the time.

When there's no crash the follower joins the game, leaves, then rejoins the game.

Leader is opening the social menu constantly.

When running a blank profile to manually control the leader the follow stands around doing nothing. Wondering in random directions intermittently.
 
Hey rrrix

I am not sure if simplefollow cause the crash but Ill attach the log file.

I was doing adventure mod act 1 skeleton cursed once the leader teleport to town to end game the follower did the same as expect but it crash. I hope this log can help.

The profile runs without simplefollow enable doing solo runs.

DemonbuddyBETA 1.1.1740.365
Trinity 1.8.13
Simplefollow 1.3.13

View attachment 123026View attachment 123027View attachment 123028
 
So anyone can help about the constant follower D3 windows crashing? Sounds like im not the only one that would be greatly apppreciated. I tried both version of SimpleFollow 13 and 8. It makes Demonbuddy crash and D3 also...
 
So anyone can help about the constant follower D3 windows crashing? Sounds like im not the only one that would be greatly apppreciated. I tried both version of SimpleFollow 13 and 8. It makes Demonbuddy crash and D3 also...


how about trying the same profile solo? and what DB version.
 
I can perfectly run 2 Diablo 3 instances playing the same profile independently. SimpleFollow seems to create an error and even freeze the follower DB ( + crash D3 follower game eventually ) . I didnt try any different Trinity version as it seems pretty important with ROS patch to have Trinity updated but i may be wrong i'm not sure? What DB/trinity/SimpleFollow version are you guys using?
 
Is it possible to make the plugin follow two diffrent bots across the internet? If it is can you please tell me how?
 
Is it possible to make the plugin follow two diffrent bots across the internet? If it is can you please tell me how?

I am not sure the limitations of the program, but it MIGHT be possible to follow another leader(ONE) over the internet if he was also running simplefollow and you had your follower's IP pointed to the leader. (granted he had a static ip & the port forwarded through his firewall).. But you said follow two different bots.. That is impossible to do -- follow 2 different bots as your character would have to be in 2 places at once.
 
For those of you with followers that leave the game and rejoin every single time I have a solution.

Normally when a party leader leaves a game all other members are left behind in that game to leave by themselves, but in particularly short games (roughly under 1:30 per game) all members are forced out automatically when the leader leaves.

This seems to be causing problems when using SimpleFollow with very short profiles like Manglemaw and Razerclaw farming. It appears SimpleFollow can't quite handle followers being automatically kicked, and it gets rather confused. The problem is the LeaderIsInGame check that is performed by the follower.

When running very short profiles since Diablo III forces all players out of a game if the leader leaves, and forces all players in to the game when the leader starts it then there is really no need for the plugin to check if the leader is in game. Basically, if the follower is in a game then its guaranteed that the leader will also be in game. So there's no need to perform a check.

In Plugins/SimpleFollow/FollowTag.cs find the following line:

Code:
new Decorator(ret => DateTime.UtcNow.Subtract(lastInteractTime).TotalMilliseconds > 1000 && (Leader.IsLeavingGame || !Leader.IsInGame || !Leader.IsInSameGame),

Replace it with this line.

Code:
new Decorator(ret => DateTime.UtcNow.Subtract(lastInteractTime).TotalMilliseconds > 1000 && (Leader.IsLeavingGame && !Leader.IsInGame && !Leader.IsInSameGame),

This is the quickest and easiest way I could think of that effectively makes it so that this checks conditions are never met and followers wont join-leave-rejoin constantly.

You MUST change this code back to it's original state if you want to switch to a longer profile where followers aren't automatically forced out when the leader leaves.
 
Last edited:
Since Diablo III forces all players out of a game if the leader joins, and forces all players in to the game when the leader starts it then there is really no need for the plugin to check if the leader is in game. Basically, if the follower is in a game then its guaranteed that the leader will also be in game. So there's no need to perform a check.

Except when a follower is not yet in the same party and is in a game, and the leader is out of game. Your code breaks this scenario I believe?
 
Except when a follower is not yet in the same party and is in a game, and the leader is out of game. Your code breaks this scenario I believe?

I think you are trying to say..
Follower is in a game (in town for example)
Leader is in a separate game (in town for example)
Not currently in a party

This kind of situation wouldn't happen unless you specifically set it up, no? Even so, your code ensures this fixes itself without the leader in game check.
Leader and follower aren't in the same party
Leader sends out invite
Follower accepts the invite
All is good. (I think?)

Where it breaks is if
Follower is in game.
Leader is in menus.
Currently in the same party.

BUT I just found it a few moments ago running a different profile that it seems D3 forces joined players out of a leaders game only in cases where the game has only been live for a short period of time. Using my code changes on longer runs means the follower cant tell when the leader has left and just sits around doing nothing while the leader is waiting for the follower to leave.

I now realize this is probably the underlying issue that I was trying to fix. I imagine you wrote SimpleFollow assuming followers had to leave the games themselves in all cases? Getting forced out by the leader seems to confuse them! Something to look at for future releases maybe? Removing the leader check in this case prevents freuquent crashing and the join-leave-rejoin problem I was experiencing. In this case there's no need for a leader check except maybe if I was using YAR and the leaders client crashes?

I hope I explained this OK.
 
The client crashing is a bug of it's own. We shouldn't be trying to hack in workarounds for that - we need to get that, specifically, fixed :)
 
Hey Rrrix,

This plugin doesn't seem to click the boss encounter acceptance prompt for the leader. The followers click them fine however.

Is this something that should be handled by profile instead?

Thanks,
 
Hey Rrrix,

This plugin doesn't seem to click the boss encounter acceptance prompt for the leader. The followers click them fine however.

Is this something that should be handled by profile instead?

Thanks,

Nope - it's supposed to be handled by the leader! Can you attach your DB log?
 
Back
Top