xzjv
Community Developer
- Joined
- Mar 17, 2014
- Messages
- 1,243
- Reaction score
- 46
What does it do?
It allows multiple bots to communicate with each other, and play together in a party.
Why would you do that?
You get more loot and XP from playing with multiple people in your party. Difficulty (monster health) only increases by +50% per player yet you receive 100% more damage. Which translates to higher level greater rifts, and more experience per rift. There is also a loot bonus for every additional player.
What's Good about AutoFollow?
I chose to fork development and redesign many of the internals because these changes will allow a much more intelligence coordination of bots in the longer term.
Please provide suggestions, bug reports and constructive criticism. So it can be improved.
Source Control
You can find the SVN here: unifiedtrinity.AutoFollow - Revision 25: /
Requirements
Instructions
Using over the internet and over multiple computers
AutoFollow is designed primarily to be used by multiple bots on the same computer. It is possible to connect over the internet or multiple computers on a local network, BUT it can be very difficult. Everybody will have a different set of problems to face depending on their network situation and how they're accessing the internet, and so this is outside of the scope here.
Change History
It allows multiple bots to communicate with each other, and play together in a party.
Why would you do that?
You get more loot and XP from playing with multiple people in your party. Difficulty (monster health) only increases by +50% per player yet you receive 100% more damage. Which translates to higher level greater rifts, and more experience per rift. There is also a loot bonus for every additional player.
What's Good about AutoFollow?
I chose to fork development and redesign many of the internals because these changes will allow a much more intelligence coordination of bots in the longer term.
- Every bot knows about every other bot.
Previously, clients only communicated with the server and had no idea what the other followers were up to.
- Async Event based communication.
Bots fire events when things happen. All other bots receive these events and can choose to react to them or not depending on their behavior profile. For example, one bot can broadcast that they are in trouble, and another bot receives that message and might decide to run over and help depending on their circumstances.
- Added Security and More Friends
The way the bots invite each other to games has been rewritten. Bots are able to join a leader's game using 'Quick Join' (including joining the games of local players who are not on the friends list). If those features are disabled they can use a normal invite from the friends list. Bots will search for the name of the player and only join the correct game. Which means you can have more than 4 people on your friends list!
Please provide suggestions, bug reports and constructive criticism. So it can be improved.
Source Control
You can find the SVN here: unifiedtrinity.AutoFollow - Revision 25: /
Requirements
- Multiple DB Licenses
- Multiple Diablo3 Accounts
- Latest Trinity
- Latest Adventurer is recommended.
Instructions
Basic Setup
- Start Multiple D3 clients in windowed mode (add -launch to target of a Diablo3.exe shortcut).
- Start as many DB instances and login (protip: click the refresh button to update dropdown to valid D3 clients)
- So now you should be in the hero select screen out of game on all bots with DB connected to each.
- For all followers load the profile \db\plugins\FollowerCombat.xml
- For the leader load any normal profile.
- Click start on DB for the leader and then start all the followers.
Manual Leader Setup
- Do the same as basic setup, except for leader bot load the profile \db\plugins\LeaderManual.xml
Using over the internet and over multiple computers
AutoFollow is designed primarily to be used by multiple bots on the same computer. It is possible to connect over the internet or multiple computers on a local network, BUT it can be very difficult. Everybody will have a different set of problems to face depending on their network situation and how they're accessing the internet, and so this is outside of the scope here.
Change History
Code:
1.260.1
[*] Fixed issue with teleport to players.
[*] Fixed issue detecting if bots are in the same game.
1.0.33
[*] Added setting to force plugin enabled on load.
[*] Updates for D3 2.5 and to prevent crashes.
1.0.27
[LIST]
[*]Updated for Trinity 2.50.185+
[*]Removed 'Auto' connection mode as it wasnt working properly - manually choose Server or Client for each bot in settings.
[*]Removed Real-Id options as they were not working properly.
[*]Bot will attempt to use quick join first if available.
[/LIST]
1.0.23
[LIST]
[*]Added support for real-id friends.
[*]Added support for inviting friends based on class/level/paragon.
[*]Added option to always accept invites from anyone.
[*]Fixed a bug with checking names that have spaces in them.
[*]Bounty split-farming (multiple bots running bounty profile)
[*]Fix for autofollow still running while diablo3 is at the login screen.less
[*]Added delay for leaving game due to leader being in a different game to smooth connection lag/drops.
[/LIST]
1.0.19
[LIST]
[*]Combat is now turned off properly rather than pulsing while trying to catch up to leader.
[*]Tightened the exceptions to following the leader, bot should fight less while catching up.
[*]Followers now can tell when the leader is casting a town portal rather than waiting till he arrives in town.
[*]Followers can now teleport to the leader immediatelyafter urshi spawns to upgrade gems.
[*]Followers should react a more responsively to needing to catch up with leader.
[*]Added some logging for movement issues
[/LIST]
1.0.17
[LIST]
[*]Leader can now invite players from the recent list or local players list.less
[*]Leader should now wait for followers to finish vendoring when using any profile
[*]Bot should no longer wait for ages after followers have finished their town runs.less
[*]Followers should no longer try to teleport to leader while on a town run.
[*]Followers should no longer try to follow leader through a hearth portal
[*]Fix for getting stuck moving after a world change.
[*]Followers shouldn't leave after rift until leader is ready; except if their bags are full.
[*]Bots should once again be able to handle events that they have fired.
[*]Added IsCastingTownPortal to information sent between bots.
[*]Experiments with accepting a rift as empowered (not currently possible)
[*]Reduced minimum catch up distance on slider to 10 and set default to 40 (was 80)less
[*]Fixed rift guardian spawn message occurring in town when rift is closed.
[*]Added cooldown on starting town runs because leader is doing it to avoid spam.
[*]Added checks for YAR login on Initialize/Enable
[*]Added setting to not display any character names in logging.
[*]PowerLevel profile will now accept invites properly.
[*]Bots will fight instead of walking to leader when within Catchup Radius if routine wants to fight.
[*]Temporarily disabled scanning the names of players in party lobby to see if leader is present.
[*]Fix for accepting any party invite.less
[*]Fix for exception entering numbers into settings slider text box.
[*]Settings: Added ability to force a bot as Server or Client
[*]Settings: Added Slider for 'CatchUp Range' - the distance required for combat on/off cycling.
[*]Events: Added events for rift guardian being spawned and when killed.
[*]Follower Powerlevel/Combat: Bots will not teleport to leader when rift guardian has been killed.
[*]Follower Combat: Bots will no longer take random portals nearby when bored.
[*]Leader: Will wait for bots to catch up and upgrade gems after killing a rift guardian.
[*]Movement: Bots will continue moving to leader when outside teleport range and in a greater rift.
[*]Gem Upgrading: now calling Adventurer's upgrade SubRoutine directly to increase reliability.
[/LIST]
1.0.10
[LIST]
[*]Tested running on Bounties, Ubers, Key wardens, Greater/Neph rifts and Manual follow.
[*]Now Supports YAR (should work best with "kickstart" disabled in YAR settings)
[*]Added LeaderManual.xml profile for having the bots follow you while you play by hand.
[*]Bots should no longer get separated as much. It effectively goes into a zerg mode when out of range.
[*]Bots should now follow leader through portal and try their luck with nearby portals if lost.
[*]Movement has been heavily refactored, now uses a local actor where possible and has faster reactions.
[*]Added setting for max leader waits for others before starting a profile (will start sooner if everyone is near)
[*]Improved how the bot waits before starting games and after changing levels to ensure everyone is present.
[*]Bot should have less memory related exceptions now.
[*]Improved out of game handling of parties and invites.
[*]Technical: Removed speed limits on communication, now runs smoothly down to 25ms.
[*]Technical: Bot now only accesses DB memory in framelock and communication thread reads cached values.
[*]Technical: Bot now reads names in party lobby out of game to tell if the leader is present.
[*]Technical: Improved event system, including limits on how fast they can queue up.
[*]Technical: Changed the way settings are saved to use a new JSON based system.
[*]Technical: Refactored pretty much everything else + Many other small bug fixes.
[*][U][B]Note: For best results make sure your profiles have stayInParty="true" on LeaveGame tags.[/B][/U]
[*][U][B]Note: Completely remove old plugin version before installing.[/B][/U]
[*][U][B]Note: folder name has changed in plugins directory to 'zAutoFollow'[/B][/U]
[/LIST]
1.0.8
[LIST]
[*]Bots now disengage combat periodically in order to follow much more closely.
[*]Improved movement to properly get updated position of the leader.
[*]Added some checking movement so it will stop trying to move when blocked.
[*]Fixed settings input boxes not working and changed them to sliders.
[*]Fixed bug where updating port/address wouldn't take effect until restart.
[*]Fixed problem that was preventing followers from communicating with Leader
[*]Fixed name scanning regex so that players with a clan can now be invited properly.
[*]Followers will now start a town run if they notice the leader is doign one.
[*]Bots will no longer leave the game to avoid unknown players when the setting is off.
[*]Bots should now teleport instead of using portal markers in normal rifts
[/LIST]
1.0.6
[LIST]
[*]Leader now requests other bots leave the game when he needs them to.
[*]Followers now move to exit marker in greater rifts when leader isn't found.
[*]Added settings for Follow Distance and Teleport Distance
[*]Fixed leader saying he was teleporting to followers when he wasn't going to.
[*]Leader should now wait for followers to stop vendoring before opening new rift portal.
[*]Interacting with portals should now fire WorldTransferStart properly
[*]Fixed bots entering and exiting portals repeatedly
[*]Added task for talking to orek.
[*]Added Markers to Data cache
[*]Added IsWorldEntryPoint, IsWorldExitPoint and Marker to Interactable object
[*]Added RiftQuest object from Adventurer to more easily work with rift quest step ids.
[*]Now waits for bots to finish vendoring before starting a rift
[*]Bots in town will now try to use hearth portals
[*]Bots will not longer try to teleport to players while in greater rift.
[*]Bots will no longer try to send invites when party is locked
[*]Improved handling of followers' gem upgrade request in greater rift.
[*]Fixed an issue preventing events when a follower is the server.
[*]Removed some excessive logging.
[*]Improved MoveTo to constantly update its going to when its target moves.
[*]Added a setting for leaving games that have unknown players in them.
[*]Added a setting for distance from leader before attempting to teleport.
[/LIST]
Last edited:
