Has anyone got simplefollow to work with Uberbot? It doesn't seem to be working at all. The leader waits for the followers to open a rift and they just sit in town. There used to be an edited version that worked last season real well, but I'm not sure what edits were made to make it work.
[Party Plugin] SimpleFollow 3.0
- Thread starter TarasBulba
- Start date
lawlumad88
New Member
- Joined
- Nov 1, 2015
- Messages
- 275
- Reaction score
- 0
No i usually run uber manually and use simple follower to fight with me. Note that you have to pause them, have the followers manually accept the rift invitation and unpause it to let them fight together.
my leader didnt invite my followers anymore
[SimpleFollow] Error 203: Could not get an update from the leader using http://localhost:10920/Follow. Is the leader running?
[SimpleFollow] System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 0000019C, Size: 12
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(Int Ptr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Internals.Actors.DiaObject.get_Position( )
at SimpleFollow.Network.FollowerService.ClientUpdate( ) in c:\Users\Stephen\Desktop\Demon Buddy\Botb\Plugins\SimpleFollow\Network\FollowerSe rvice.cs:line 122
how can i fix that?
[SimpleFollow] Error 203: Could not get an update from the leader using http://localhost:10920/Follow. Is the leader running?
[SimpleFollow] System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 0000019C, Size: 12
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(Int Ptr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Internals.Actors.DiaObject.get_Position( )
at SimpleFollow.Network.FollowerService.ClientUpdate( ) in c:\Users\Stephen\Desktop\Demon Buddy\Botb\Plugins\SimpleFollow\Network\FollowerSe rvice.cs:line 122
how can i fix that?
um what? I am getting this same error where it can't connect to host. i've pinged the host computer with cmd and it comes back with a reply so it can contact it but for some reason simple follow can't communicate.
i got it working simplefollow is sending to followers to use machines but its not implented in simplefollow.
edit this file Plugins\SimpleFollow\Behaviors\LeaderBehavior.cs and comment out this code. then it should work.
// Wait for followers to open greater rift
// while (ValidCheck() && ShouldFollowerOpenRift())
// {
// SimpleFollow.Pulse();
// Logr.Log("Waiting for follower to open rift...");
// await Coroutine.Yield();
// }
maybe you need to delete simplefollow en install again. posting logs would be usefull for others
here is my edited version of simplefollow its working with uberrun plugin and its doing townruns on act1
and if you want to do townruns properly on greater rifts change this line in adventure plugin Plugins\Adventurer\Coroutines\RiftCoroutines\RiftCoroutine.cs
private readonly InteractionCoroutine _interactWithRiftStoneInteractionCoroutine = new InteractionCoroutine(RiftData.RiftStoneSNO, TimeSpan.FromSeconds(2), TimeSpan.FromSeconds(1));
to
private readonly InteractionCoroutine _interactWithRiftStoneInteractionCoroutine = new InteractionCoroutine(RiftData.RiftStoneSNO, TimeSpan.FromSeconds(2), TimeSpan.FromSeconds(15));
then it will now wait 15 seconds before opening rift
View attachment SimpleFollow.zip
and if you want to do townruns properly on greater rifts change this line in adventure plugin Plugins\Adventurer\Coroutines\RiftCoroutines\RiftCoroutine.cs
private readonly InteractionCoroutine _interactWithRiftStoneInteractionCoroutine = new InteractionCoroutine(RiftData.RiftStoneSNO, TimeSpan.FromSeconds(2), TimeSpan.FromSeconds(1));
to
private readonly InteractionCoroutine _interactWithRiftStoneInteractionCoroutine = new InteractionCoroutine(RiftData.RiftStoneSNO, TimeSpan.FromSeconds(2), TimeSpan.FromSeconds(15));
then it will now wait 15 seconds before opening rift
View attachment SimpleFollow.zip
jhartman1991
Member
- Joined
- Aug 29, 2014
- Messages
- 134
- Reaction score
- 0
any reason why my guys all just sit there and keep TPing to some act 5 zone. Over and over and over and over.
Htotheenne
New Member
- Joined
- Oct 22, 2013
- Messages
- 15
- Reaction score
- 0
hey guys im using this plugin like 6months or something, every thing works fine, but i have one problem after the greater rift my followers do not have enough time to spend bloodshards, stash crash items and doing stuff before leader starting next greater rift, when im doing nephalem portals its not nessecary because they port into after they have done there full townrun, would be nice if somebody can help me out. im not good coding or something but i think just a delay i need before starting next greater rift, you guys dont have this problem ?
jhartman1991
Member
- Joined
- Aug 29, 2014
- Messages
- 134
- Reaction score
- 0
Anyone??
destroyer57
Member
- Joined
- Oct 2, 2015
- Messages
- 178
- Reaction score
- 9
I solved this problem by unchecking "use book of cain" on leader's demonbuddy settings. That way, leader will identify items one by one and this will give followers enough time.
having same issue, follower ports to act 5 wp and sits with error code
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at SimpleFollow.Network.IFollowService.GetUpdate()
at SimpleFollow.Network.FollowerService.ClientUpdate() in c:\Users\jimmah\Documents\Demonbuddy\Plugins\SimpleFollow\Network\FollowerService.cs:line 133
[SimpleFollow] Initializing Client Service connection to http://MYIPHERE:10920/Follow
Was initially trying to run 2 clients in seperate VMware and using local IP, localhost and external IP. nothing would work and assuming vmware port forwarding was required.
Instead I opened 2 bots and clients inside same vmware using localhost and it started right up.
This error is when your 2 bots are not talking to each other and the follower trying to port to town to afk.
Also used https://www.*************.com/ipb/i...-and-memory-usage-of-wow-and-d3-by-70/&page=1
to remove rendering so the 2 bots in vmware run really well. its free to use currently.
gauthierjoc
New Member
- Joined
- Jan 22, 2014
- Messages
- 75
- Reaction score
- 0
GIVING 20$ to set it up for me via teamviewer !@
TwoCigars
Active Member
- Joined
- May 4, 2014
- Messages
- 992
- Reaction score
- 41
To anyone having trouble using SimpleFollow, keep in mind that the Dev who originally made it is no longer working on it. Then TarasBulba fixed it up to work in the last patch, but was not actively supporting it.
After the 2.4 patch, xvjv was kind enough to fix the compiler errors, but it is again, not currently supported.
xvjv has been working on AutoFollow which is currently supported and as a former SimpleFollow user, I prefer AutoFollow. It's in my sig if you need a link to it.
After the 2.4 patch, xvjv was kind enough to fix the compiler errors, but it is again, not currently supported.
xvjv has been working on AutoFollow which is currently supported and as a former SimpleFollow user, I prefer AutoFollow. It's in my sig if you need a link to it.
AUTOFOLLOW
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 Different than SimpleFollow?
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 'QuickJoin' (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!
- Client/Server is disconnected from Leader/Follower
It doesn't matter which bot server or client or the other in which you start each bot. They'll figure it out. This will allow for future improvements where the bots might re-negociate who should be the leader, or even split into multiple groups to split farm.
This is a Beta Plugin
Its just been made and is likely to contain many bugs and problems. Please provide suggestions, bug reports and constructive criticism. So it can be improved.
Source Control
You can find the SVN here: https://subversion.assembla.com/svn/unifiedtrinity.AutoFollow/
Support My Work
If you like this plugin and it works well for you.
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
Known Issues
- If bots get themselves into rotating between client and server mode they are unable to recover. Restart All DBs.
- If bots are changed from a leader to a follower or vice-versa they will may load the behavior properly. Restart DB.
- Bots will go into a game only to leave again once they get invited (particularly when using YAR with kickstart).
Change History
Code:[FONT=Verdana]1.0.10[/FONT] [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] [FONT=Verdana]1.0.8[/FONT] [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] [FONT=Verdana]1.0.6[/FONT] [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: