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

[Party Plugin] SimpleFollow - Multi-Bot Party Plugin

I am currently seeing the same issue as Xerais with Greater rifts... lately I have my 3 bot team run only normal rifts via R-Rifttest.xml and it works great... when the leader enters the next rift level, all followers just immediately portal to the leader. I just wish there was a way for them to actually use the portals themselves so Greater rifts would be possible.

I am using
QT 3.1.1
Trinity 2.2.0
 
Yea JoJo, same exact thing. They used to take the portals themselves but now they only teleport to the leader. It makes GRIFTs impossible to do afk.
 
Same issue, really frustrating. Sometimes they port to town, sometimes they just start running away from the portal.
 
Anyone know what the "trinity hotspots" option is? Also what is the difference between SimpleFollow and SimpleFollow_PowerLevel?
 
I believe hot spots relays where the leader is headed instead of where they are currently located. Powerlevel just follows without combat.
 
how do you set up with two different computer? i am not getting well along with program. I use two computer to run it instead of one computer. any solution?????
 
nvm this plugin isn't realy smooth working for me.

anyway thx for all you're time! :rolleyes:
 
Last edited:
Any plans to update this? This used to be so good and so much fun. I am not sure if the problems are with simplefollow or just inherent in the latest instability of db.
 
Any plans to update this? This used to be so good and so much fun. I am not sure if the problems are with simplefollow or just inherent in the latest instability of db.

What SPECIFIC problems do you have?
I am using this all the time and it works well. Maybe you can be more specific and point out the exact issues you are having that is related to this plugin and not related to other things such as other plugins, profiles, user retardedness, etc etc.
:)
 
Last edited:
Hey guys,

Let me explain you the problem, I am with a friend, we try to connect our two different pc to use SimpleFollow, we had all configure as you said in your tutorials. But it couldnt work so far.
I am the follower and we have this mistake:

[SimpleFollow] Resetting Grid and clearing Navigator
[SimpleFollow] Initializing Client Service connection to http://localhost:10920/Follow
[SimpleFollow] Could not get an update from the leader using http://localhost:10920/Follow. Is the leader running? (Il n'existait pas de point de terminaison à l'écoute sur http://localhost:10920/Follow pouvant accepter le message. Ceci est souvent dû à une adresse ou une action SOAP incorrecte. S'il est présent, voir l'élément InnerException pour plus d'informations.)
[SimpleFollow] Initializing Client Service connection to http://localhost:10920/Follow
[SimpleFollow] Could not get an update from the leader using http://localhost:10920/Follow. Is the leader running? (Il n'existait pas de point de terminaison à l'écoute sur http://localhost:10920/Follow pouvant accepter le message. Ceci est souvent dû à une adresse ou une action SOAP incorrecte. S'il est présent, voir l'élément InnerException pour plus d'informations.)

Someone may help us to do a new tutorial please?

Thank you very much
 
Hey guys,

Let me explain you the problem, I am with a friend, we try to connect our two different pc to use SimpleFollow, we had all configure as you said in your tutorials. But it couldnt work so far.
I am the follower and we have this mistake:

[SimpleFollow] Resetting Grid and clearing Navigator
[SimpleFollow] Initializing Client Service connection to http://localhost:10920/Follow
[SimpleFollow] Could not get an update from the leader using http://localhost:10920/Follow. Is the leader running? (Il n'existait pas de point de terminaison à l'écoute sur http://localhost:10920/Follow pouvant accepter le message. Ceci est souvent dû à une adresse ou une action SOAP incorrecte. S'il est présent, voir l'élément InnerException pour plus d'informations.)
[SimpleFollow] Initializing Client Service connection to http://localhost:10920/Follow
[SimpleFollow] Could not get an update from the leader using http://localhost:10920/Follow. Is the leader running? (Il n'existait pas de point de terminaison à l'écoute sur http://localhost:10920/Follow pouvant accepter le message. Ceci est souvent dû à une adresse ou une action SOAP incorrecte. S'il est présent, voir l'élément InnerException pour plus d'informations.)

Someone may help us to do a new tutorial please?

Thank you very much


PC1 :

1. Launch DOS Prompt. (Press window key + "R", & type "CMD")
2. Type "IPCONFIG" then you can see your PC1's IP ADDRESS just like "192.168.0.5 ..."


PC2 : (follower bot)

1. In simple follow config
2. Type PC1's IP ADDRESS @ bind address.
 
is there an option to invite other than the first 3? for example do my main as #1 and the otehrs as follower?
 
When running Trail Rifts , the follower running A5 to the Orange Exit Portal in the upper right corner and don't open new Trail Rift. Only happen with this Method. In Grift all is fine. But just noticed this after switching from 2.0.16 > 2.0.23 Simplefollow ;/
 
SimpleFollow 2.1.1 posted

Basically it's full of additional stability, reliability and performance fixes.



I haven't posted a changelog in like, i dunno, forever... so here's the last few versions:

2.1.0
FollowTag will no longer use Waypoints when going to town (causes a disconnect).
FollowTag will no longer attempt to follow leader through portals when in town.
Ran CodeCleanup
2.0.14
More refactoring, bug fixing, and feature additions for Greater Rift support
Leader "RequestOpenRift" now waits for all party members to be connected
Leader message is now correctly set when server service is started
Standardized game events for hook checks and message updates
Added timeouts for async MoveToActor tags
Greater Rift FindDungeonExit is now used before basic Follower portal navigation
Interacting with rift portal in town now handles both regular rift portals and greater rift portals
WaitTimer tag added after MoveToActor and QTOpenRiftWrapper
Fixed LeaderBehavior incorrectly waiting for followers to connect
Built-in CompleteGreaterRift logic to Follow tag
Now using new Coroutine style FollowPlayerThroughPortal
Followers will now interact with greater rift portal if in town
Followers will now use a MoveToMapMarker to find rift dungeon exit
Refactored Follower Rift Opening a little
Added Option for Leaders to wait for Followers to connect while in town or out of game
OutOfGame hook should no longer be replaced if no profile is loaded
Old Follower messages will be removed after 30 seconds to prevent "stale" followers appearing for the leader's cache
Remove & sort usings
QuestTools is now directly integrated for Rift preferences, and ProfileBehavior queing features
More updates for leader -> follower rift opening communication
Fixes for opening server service while port is already taken
Initial implementation of FollowerOpenRift, QuestTools API
Added IntDataMessageExtensions to allow for .Send()
Fixed Social invites not checking for alternate Friend 4 button
Fixed Leader behavior
More refactoring and bug fixing
2.0.0
SimpleFollow class has been refactored into several other classes
Network logic has been seperated
Behavior logic has been seperated
Heavy refactoring of many other classes
Reorganized namespaces
Fixed NRE with LeaderPortal
Fixed ReadMemory exception with Rift Keys
Movement debug logs will be less spammy
SimpleFollow will now always teleport to the correct leader index
 
Follower keeps getting stucked (sometimes) @ Portals to run next level. I have to manually move them..... Don't happen every time but saw it
 
First of, thank you for the updates, rrrix. I had actually been working on refactoring your code out of interest. I wasnt sure why you were using all these static classes but got some appreciation for it when I saw the limitations of the underlying framework you have to work around.

Question I have is if you could update the SVN link as well. I had thought that Assembla would somehow sync the git and svn view of the repository. Of course that request is made hoping that Assembla makes that easy.
 
rrix,

Thank you so much for putting in the time on updating this plugin. I took your advice and grabbed ISboxer a few months ago, WOW! I know its not required but it certainly makes things run better.
 
Back
Top