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

[Plugin] AutoFollow 1.260.1

running 2 bot, both bot are waiting for another one to connect runing with .470 DB anyone else got same problem?
 
In the settings of the plugin AutoFollow verify one machine is set to server and the other is set to client. On the client machine modify the settings IP address. Try adding the IP-address of the machine set as server.


Hope this helps....
 
hey guy
i try the fix you guy made for playing in group
Code:
_riftStartTime = DateTime.UtcNow;
const int waittime = 20;
const int partysize = 4; // ToDo: Add slider for party size under beta playground checkbox


if (true)
{
and its still start a new game right away
using trinity .35

does iam the only one with that prob
thanks for the help
 
Did you upgrade trinity after you made the changes? If so, it will over-write the RiftCoroutine.cs when you do a new Trinity install.

When this happens, is it the first time all of the bots are joining the autofollow server and the game or is it after they have been playing together in GRifts?

How many bots are you using?

How long were the bots waiting at the GRift portal.

How many of the bots joined the GRift when the leader started it.

Were any of the bots still in process of joining the group/game?
 
Revive is still broken using AF.
Sometimes bots will go to player cross and get confused, running back and forth near it.
When it miraculously gets to the cross it will start to try to revive for a fraction of a second then stop. move away and come back.
This will continue until the bot revives itself.
Huge waste of time.


Death/Repair handling is also broken.
When dying enough (happens quite often unfortunately with AF logic) to need repair, bot will revive and try to teleport to town.
If there is an enemy, bot will die repeatedly trying to teleport out.
This creates a stuck issue until inactivity time hits.

If it's a DPS character, which it often is, it completely screws up the entire rift as the rest of the group slowly slogs through.
If it's a ZDPS character it's even better! YAY! Because no one else can stay alive, so they all die. over. and over. and over.

and over

and

over

a
n
d

o
v
e
r
 
cybernite said:
In the settings of the plugin AutoFollow verify one machine is set to server and the other is set to client. On the client machine modify the settings IP address. Try adding the IP-address of the machine set as server.


Hope this helps....
Click to expand...

Still not working. Tried now different way's to get it done.. but ummpph nope <.<

Changed with Ipv4 on booth clients+ localhost. Restarted DB, new Installation etc

View attachment 12316 2016-09-01 16.55.txt
View attachment 1732 2016-09-01 16.49.txt
 
Dude this program is definitely a huge help but im having trouble finding the right combination of classes to maximize the 3 man group efficiency. I settled on running 3 Helltooth WD's just to make things simple but i've noticed a problem. They don't follow closely enough and the y ar always getting drawn into battles an leaving the lead WD. I have min trash pack set to 8 on all toons. Any thoughts on this? Also they are following at anywhere from 50m-100 yards based on diablo 3 math but settings indicate 10 yards...
 
Dantronix said:
Dude this program is definitely a huge help but im having trouble finding the right combination of classes to maximize the 3 man group efficiency. I settled on running 3 Helltooth WD's just to make things simple but i've noticed a problem. They don't follow closely enough and the y ar always getting drawn into battles an leaving the lead WD. I have min trash pack set to 8 on all toons. Any thoughts on this? Also they are following at anywhere from 50m-100 yards based on diablo 3 math but settings indicate 10 yards...
Click to expand...

You really need to look at running a ZDPS character. It allows me to run glass cannon WDs at MASSIVE DPS. Her eis an example pic of massive Crits:
23t1pwn.png

...I actually see crits over 200 billion quite frequently...



I am not trying to tell you to spend more money, but if you're already running 3 WDs, my suggestion is to by another game copy and DB License...

Then run a Support Monk. It's pretty quick to gear for GR 65 or so. After ancient gear and Caldesann's, its GR 80+ with the bot.

Side note:
There have been some updates for WD posted in the Discord channel or on the SVN if you want to check those out. Might make a difference for you. (Discord link in my sig, feel free to add me on there).

Your feedback on the changes would be appreciated.

ATTACHMENTS:
I am attaching my current WD Trinity settings as well as my ZDPS monk settings
  • I run 2 DPS WDs, 1 LTK Monk and 1 ZDPS Monk.
  • Pick a bot to wear Nemesis Bracers, have everyone IGNORE SHRINES except the one with Nemesis on.
  • I am running WD as leader. I picked my highest DPS because I always want him in the fray.
  • I have avoidance turned down quite a bit, this is a result of my testing to be the best scenario for my group composition.
  • Here is my current monk ZDPS Build:
    • Diablo III Character Planner
      • The Frostburn Gauntlets are a test that has been good so far.
      • If you dont want to run frostburns, it's jsut as good to run Inna's Hold gloves and tchange the RRoG in the cube to Band of Rue Chambers
    • You can also run Rogue-Slanderer ZDPS monk, it works well.
    • I am using Caldesann's to put vitality on all my ancient items.

You will want to look through the ItemLists as it can be pretty restricting if you aren't geared as well as I am:
  • Diablo III Character Planner
  • I have changed over to Int gems in all gear sockets since making that planner (yes it's more likely to die, but the scenarios that kill me, it doesnt make a difference)

Note that my ItemLists cover multiple builds in case you want to test something else out.


Important Group Build Notes:
Pestilence rune causes you to cast Locust Swarm less. It's pretty GG since time wated casting = lost DPS. You can still run the de-buff rune if you like on some of the WDs. Currently my DPS monk (listed in D3Planner) runs pestilence, the other runs the debuff rune.

Run the Amethyst helm since Rush of Essence passive means we are never starved for Mana.

WDs might die 1-2 times a GRift at 75-80, this is somewhat expected. I have contemplated running 3 WDs, 1 ZDPS monk or 4 monks.
  • Barbs run off too much
  • DH is too glass cannon for group bot IMO
  • I have run a super GG Firebird archon and it's not even close the the DPS of the WD or LTK monk in it's current implementation in the bot.


Like I said, add me on Discord and we can chat if you need further help.

TC
 

Attachments

TwoCigars said:
You really need to look at running a ZDPS character. It allows me to run glass cannon WDs at MASSIVE DPS. Her eis an example pic of massive Crits:
23t1pwn.png

...I actually see crits over 200 billion quite frequently...



I am not trying to tell you to spend more money, but if you're already running 3 WDs, my suggestion is to by another game copy and DB License...

Then run a Support Monk. It's pretty quick to gear for GR 65 or so. After ancient gear and Caldesann's, its GR 80+ with the bot.

Side note:
There have been some updates for WD posted in the Discord channel or on the SVN if you want to check those out. Might make a difference for you. (Discord link in my sig, feel free to add me on there).

Your feedback on the changes would be appreciated.

ATTACHMENTS:
I am attaching my current WD Trinity settings as well as my ZDPS monk settings
  • I run 2 DPS WDs, 1 LTK Monk and 1 ZDPS Monk.
  • Pick a bot to wear Nemesis Bracers, have everyone IGNORE SHRINES except the one with Nemesis on.
  • I am running WD as leader. I picked my highest DPS because I always want him in the fray.
  • I have avoidance turned down quite a bit, this is a result of my testing to be the best scenario for my group composition.
  • Here is my current monk ZDPS Build:
    • Diablo III Character Planner
      • The Frostburn Gauntlets are a test that has been good so far.
      • If you dont want to run frostburns, it's jsut as good to run Inna's Hold gloves and tchange the RRoG in the cube to Band of Rue Chambers
    • You can also run Rogue-Slanderer ZDPS monk, it works well.
    • I am using Caldesann's to put vitality on all my ancient items.

You will want to look through the ItemLists as it can be pretty restricting if you aren't geared as well as I am:
  • Diablo III Character Planner
  • I have changed over to Int gems in all gear sockets since making that planner (yes it's more likely to die, but the scenarios that kill me, it doesnt make a difference)

Note that my ItemLists cover multiple builds in case you want to test something else out.


Important Group Build Notes:
Pestilence rune causes you to cast Locust Swarm less. It's pretty GG since time wated casting = lost DPS. You can still run the de-buff rune if you like on some of the WDs. Currently my DPS monk (listed in D3Planner) runs pestilence, the other runs the debuff rune.

Run the Amethyst helm since Rush of Essence passive means we are never starved for Mana.

WDs might die 1-2 times a GRift at 75-80, this is somewhat expected. I have contemplated running 3 WDs, 1 ZDPS monk or 4 monks.
  • Barbs run off too much
  • DH is too glass cannon for group bot IMO
  • I have run a super GG Firebird archon and it's not even close the the DPS of the WD or LTK monk in it's current implementation in the bot.


Like I said, add me on Discord and we can chat if you need further help.

TC
Click to expand...



Well that was super helpful and i appreciate how thorough you were. I actually ran a 3 person setup with one zpds similar to the build you had for the monk and he kept dying like a punk and my damage just wasn't there. I actually took a break because i was frustrated by my lack of progress making a 3 man group. On the other and I would be willing to try again if your template is a succesful as you say. I dont mind buying a 4th Diablo license but im ot a fan of these temporary DB licenses. I have 3 lifetime licenses...
 
Dantronix said:
Well that was super helpful and i appreciate how thorough you were. I actually ran a 3 person setup with one zpds similar to the build you had for the monk and he kept dying like a punk and my damage just wasn't there. I actually took a break because i was frustrated by my lack of progress making a 3 man group. On the other and I would be willing to try again if your template is a succesful as you say. I dont mind buying a 4th Diablo license but im ot a fan of these temporary DB licenses. I have 3 lifetime licenses...
Click to expand...

It is effective. Non-Crits. Look at the madness.

Run 1 Monk 2 WDs. Look for me on Discord for any help you might need.

ac0f7800ffa2070f0bc379cc7b475d94.png
 
Lindi91 said:
Always got this message : [AutoFollow.Behaviors][<OutOfGameTask>d__21] Waiting for bots to connect...
[AutoFollow.Networking][Client] Lost Connection to server... any idea how to fix that?

Edit: Iam using 2 Bots on 1 Computer. In settings its localhost but its not working still get the same error
Click to expand...

For all who get this or similar errors...
most of the times it is your Firewall. please make sure u set a firewall rule for port 10920 (or whatever u use)
mine (eset nod 32 ISS) have done the same error for me, until i set a rule for Bot & Port
 
at the end oF griFt leader upgrade inFinity times the same gems in loop and others Follower dont upgrade gems

nothing to do follower dont upgrade gem

anyone hav a solution for this issue?
 
Last edited:
Got an error as Follower

Code: 
[AutoFollow.Events][ChangeMonitor] Lost leader, he was right here
[AutoFollow.Coroutines][<LeaveWhenInWrongGame>d__12] Leader gameId is different/invalid!
[AutoFollow.Behaviors][<OnLeavingGame>d__12] Leader (82311679) is leaving game, lets leave too!
[AutoFollow.Coroutines.Resources][GameUI] Error clicking UI Button: System.Exception: Nur ein Teil der ReadProcessMemory- oder WriteProcessMemory-Anforderung wurde abgeschlossen, at addr: 00000188, Size: 4
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.Read[T](IntPtr addr)
   at Zeta.Game.Internals.Actors.ACD.get_HitpointsCurrent()
   at Zeta.Game.Internals.Actors.DiaUnit.get_IsDead()
   at AutoFollow.Coroutines.Resources.GameUI.SafeCheckClickButtons() in C:\Users\CPTCL\Downloads\Demon Buddy\Demonbuddy 1\Plugins\zAutoFollow\Resources\GameUI.cs:line 416
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Nur ein Teil der ReadProcessMemory- oder WriteProcessMemory-Anforderung wurde abgeschlossen, at addr: 00000088, Size: 4
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.Read[T](IntPtr addr)
   at Zeta.Game.Internals.Actors.DiaObject.get_ACDId()
   at Zeta.Game.Internals.Actors.DiaActivePlayer.‫‫‫**​*‪**​​‏‬‎‬**‎*‬**(Boolean )
   at Zeta.Bot.GameStats.*‪*‬****​‫‎****‫​‏‬*‏​‬​‏******(Object , EventArgs )
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Zeta.Bot.Pulsator.*‫‫*‬*​​***​‪‎‎‬‪‬*‬‫​*‎‏‪*‪*(Delegate , Object[] )
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Zeta.Game.ZetaDia.‎‫**‪*‏***‬‪‬‎*‎‫‏‏‬​‪‎*​‬****.‫**‏​​‪‎​**‬‏**‎*‏‏‬‫*‫***()
   at Zeta.Game.Internals.DynamicPointer`1.get_Value()
   at Zeta.Game.ZetaDia.get_PlayerData()
   at Trinity.Framework.Modules.HotbarCache.Update()
   at Trinity.Framework.Modules.HotbarCache.OnPulse()
   at Trinity.Framework.Module.FirePulse(Boolean force)
   at Trinity.Framework.Module.FireEvent(ModuleEventType moduleEventType)
   at Trinity.Framework.ModuleManager.<>c__DisplayClass3_0.<FireEventAll>b__0(Module util)
   at Trinity.Framework.ModuleManager.ExecuteOnInstances(Action`1 action)
   at Trinity.Framework.ModuleManager.FireEventAll(ModuleEventType moduleEventType)
   at Trinity.Framework.Core.Update(Boolean force)
   at Trinity.Framework.Core.Pulse(Object sender, EventArgs eventArgs)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Zeta.Bot.Pulsator.*‫‫*‬*​​***​‪‎‎‬‪‬*‬‫​*‎‏‪*‪*(Delegate , Object[] )
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Nur ein Teil der ReadProcessMemory- oder WriteProcessMemory-Anforderung wurde abgeschlossen, at addr: 0000019C, Size: 12
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.Read[T](IntPtr addr)
   at Zeta.Game.Internals.Actors.DiaObject.get_Position()
   at AutoFollow.Resources.BotHistory.PositionCache.<>c__DisplayClass26_0.<AddPosition>b__1(PositionCache p) in C:\Users\CPTCL\Downloads\Demon Buddy\Demonbuddy 1\Plugins\zAutoFollow\Resources\BotHistory.cs:line 108
   at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
   at AutoFollow.Resources.BotHistory.PositionCache.AddPosition(Single distance) in C:\Users\CPTCL\Downloads\Demon Buddy\Demonbuddy 1\Plugins\zAutoFollow\Resources\BotHistory.cs:line 108
   at AutoFollow.Resources.BotHistory.Update() in C:\Users\CPTCL\Downloads\Demon Buddy\Demonbuddy 1\Plugins\zAutoFollow\Resources\BotHistory.cs:line 34
   at AutoFollow.Resources.BotHistory.Pulsator_OnPulse(Object sender, EventArgs e) in C:\Users\CPTCL\Downloads\Demon Buddy\Demonbuddy 1\Plugins\zAutoFollow\Resources\BotHistory.cs:line 29
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Zeta.Bot.Pulsator.*‫‫*‬*​​***​‪‎‎‬‪‬*‬‫​*‎‏‪*‪*(Delegate , Object[] )
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Nur ein Teil der ReadProcessMemory- oder WriteProcessMemory-Anforderung wurde abgeschlossen, at addr: 0000019C, Size: 12
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.Read[T](IntPtr addr)
   at Zeta.Game.Internals.Actors.DiaObject.get_Position()
   at AutoFollow.Resources.BotHistory.PositionCache.<>c__DisplayClass26_0.<AddPosition>b__1(PositionCache p) in C:\Users\CPTCL\Downloads\Demon Buddy\Demonbuddy 1\Plugins\zAutoFollow\Resources\BotHistory.cs:line 108
   at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
   at AutoFollow.Resources.BotHistory.PositionCache.AddPosition(Single distance) in C:\Users\CPTCL\Downloads\Demon Buddy\Demonbuddy 1\Plugins\zAutoFollow\Resources\BotHistory.cs:line 108
   at AutoFollow.Resources.BotHistory.PositionCache.<>c.<.cctor>b__24_0(Object sender, EventArgs args) in C:\Users\CPTCL\Downloads\Demon Buddy\Demonbuddy 1\Plugins\zAutoFollow\Resources\BotHistory.cs:line 87
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Zeta.Bot.Pulsator.*‫‫*‬*​​***​‪‎‎‬‪‬*‬‫​*‎‏‪*‪*(Delegate , Object[] )
System.NullReferenceException: Object reference not set to an instance of an object.
   at Zeta.Game.ZetaDia.‎‫**‪*‏***‬‪‬‎*‎‫‏‏‬​‪‎*​‬****.‫**‏​​‪‎​**‬‏**‎*‏‏‬‫*‫***()
   at Zeta.Game.Internals.DynamicPointer`1.get_Value()
   at Zeta.Game.ZetaDia.get_PlayerData()
   at Trinity.Framework.Modules.InventoryCache.Update()
   at Trinity.Framework.Modules.InventoryCache.<.ctor>b__0_5(Object sender, EventArgs args)
   at Zeta.Bot.GameEvents.*‫‫*‬*​​***​‪‎‎‬‪‬*‬‫​*‎‏‪*‪*[](EventHandler`1 , Object ,  )
System.NullReferenceException: Object reference not set to an instance of an object.
   at Trinity.Components.Adventurer.Game.Actors.EntryPortals.AddEntryPortal()
   at Trinity.Components.Adventurer.Game.Events.PluginEvents.GameEvents_OnWorldChanged(Object sender, EventArgs e)
   at Zeta.Bot.GameEvents.*‫‫*‬*​​***​‪‎‎‬‪‬*‬‫​*‎‏‪*‪*[](EventHandler`1 , Object ,  )

Bot works for a while... than this error..
Bit stops to move or fight. Only port to leader.
Have to restart the bot. Any suggestions?
 
Dantronix said:
Dude this program is definitely a huge help but im having trouble finding the right combination of classes to maximize the 3 man group efficiency. I settled on running 3 Helltooth WD's just to make things simple but i've noticed a problem. They don't follow closely enough and the y ar always getting drawn into battles an leaving the lead WD. I have min trash pack set to 8 on all toons. Any thoughts on this? Also they are following at anywhere from 50m-100 yards based on diablo 3 math but settings indicate 10 yards...
Click to expand...

Followers need to have follow at 5-10, trash size to 1, elite range to 20 and trash range to 20.
 
Hoschy said:
For all who get this or similar errors...
most of the times it is your Firewall. please make sure u set a firewall rule for port 10920 (or whatever u use)
mine (eset nod 32 ISS) have done the same error for me, until i set a rule for Bot & Port
Click to expand...

Run them from the same db folder.
 
donovan said:
at the end oF griFt leader upgrade inFinity times the same gems in loop and others Follower dont upgrade gems

nothing to do follower dont upgrade gem

anyone hav a solution for this issue?
Click to expand...
Fresh install, run them off the same db folder and see how that goes. Try a new folder and test that out.
 
zautofollow plugin compile error

I have been trying to get autofollow working for quite some time, i get the following error message (running latest demon buddy with zautofollow 1.0.27):
Demonbuddy v1.1.3069.470 started
Logging in...
T: 5247791972637172727 H: 2266498736
Attached to Diablo III with pid: 23396
Flashing window
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\LeaderManual.cs(36,42) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\Leader.cs(157,42) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(218,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(220,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\Leader.cs(166,42) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(222,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(224,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\UDemonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(226,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(228,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(230,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(232,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(234,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(236,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\Leader.cs(189,42) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\BaseBehavior.cs(238,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\ProfileTags\AutoFollowTag.cs(43,34) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Networking\Service.cs(156,45) : warning CS0168: The variable 'e' is declared but never used
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\FollowerCombat.cs(202,42) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Behaviors\FollowerCombat.cs(226,42) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Networking\Server.cs(47,56) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Networking\Client.cs(225,37) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Resources\CoroutineHelper.cs(143,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Resources\IPluginCommunicator.cs(78,30) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Resources\IPluginCommunicator.cs(115,34) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Resources\PluginCommunicator.cs(21,18) : error CS0266: Cannot implicitly convert type 'AutoFollow.AutoFollow' to 'AutoFollow.Resources.ICommunicationEnabledPlugin'. An explicit conversion exists (are you missing a cast?)
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Coroutines\Party.cs(42,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Coroutines\Party.cs(68,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Coroutines\Party.cs(85,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Coroutines\Party.cs(101,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Coroutines\Coordination.cs(190,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Resources\MemoryHelper.cs(72,34) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Resources\MemoryHelper.cs(81,34) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Coroutines\Party.cs(214,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Coroutines\Party.cs(339,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Coroutines\Party.cs(406,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Events\ChangeMonitor.cs(27,31) : warning CS0169: The field 'ChangeMonitor._currentTarget' is never used
Compiler Error: C:\Demonbuddy\Plugins\zAutoFollow\Resources\Player.cs(74,29) : warning CS0414: The field 'Player._lastIsPartyLeader' is assigned but its value is never used
Setting up TrinityPlugin Logging
[Trinity 2.50.231] Initialized v2.50.231
[Trinity 2.50.231] Trinity OnEnabled() was called from thread: (1)
[Trinity 2.50.231] OnEnable start
[Trinity 2.50.231] Loading Hero Specific Settings
[Trinity 2.50.231] Configuration file loaded
[Trinity 2.50.231] Configuration loaded successfully.
[Trinity 2.50.231] Loading Avoidance Data
[Trinity 2.50.231] ItemSetting OnLoaded called
[Trinity 2.50.231] Loading ItemList Data
[Trinity 2.50.231] ENABLED: v2.50.231 BETA. Provides Combat, Exploration and much more now in action!
[QuestTools][Plugin] v3.5.14 Enabled
Current bot set to Order Bot
Loaded profile R-RIFT
 

Attachments

Last edited:
You must log in or register to reply here.
Back
Top