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

[Exp/Legs/Keys/Rift/...] BotCompilation


This is the end, the end. I do not have time for a project like this. I upload a final version later and I will do different posts for different plugins and profiles of my compositions (and I will continue on this path)
 
Please fix rift profile in next version and keep it up to date the new revision is 430
 
how to solve?
Exception during bot tick.System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired
em GreyMagic.Executor.WaitForInjection(Int32 timeout)
em GreyMagic.Executor.Execute(Int32 timeout)
em GreyMagic.Executor.GrabFrame()
em GreyMagic.ExternalProcessMemory.AcquireFrame(Boolean isHardLock)
em Zeta.Bot.BotMain.()
 
What excactly is this, just a dev making profiles and charging for them instead of free? like everything else?
 
1 question, i install everything, everything works but it broke my monk, doesn't spam mantra anymore, i tried to reinstall the MonkCombat but still doesn't spam

What should i change ? the combat. file in trinity and put the old one ?
 
For anyone still trying to download and use this, refer to the earlier post in bold that says this project is dead.

tecknoe said:
What excactly is this, just a dev making profiles and charging for them instead of free? like everything else?
Click to expand...

Project was free... It was a compilation of all of the basic needs that people could download, toss in a folder and get botting with very little searching or knowledge... However, what started as a simple post to help the community became a massive amount of work to keep up with and reply to. Often times the community was more demanding/complaining than they were helpful/appreciative.

Replies like the one from tecknoe are a perfect example. You want to demand/require a dev to continue to make public releases for free...

This is happening more and more frequently on the forums. Thousands of downloads, dozens of complaints, the occasional "thank you" every few pages of the thread, with the original poster making 50% of all the posts... IE lots and lots of leechers.

I feel it's fair to say that most Devs have more than enough motivation when they are getting appreciation from the community and the occasional donation...
Anyways... BuddyMe decided to continue upgrading and improving KeyBot in a separate thread. It is easily the best key run plugin I had ever seen.

After having his thread disrupted numerous times with demands and complaints over basic quibbles, he decided to post about not continuing updating Keybot. When he made mention of appreciation for the thread or the idea of making it a pay-to-use plugin, there was a backlash from many members. This poor response sealed the deal.

It was unfortunate but you have to understand the large amount of time put in maintaining a thread and plugin both.

If the choice is having a dev quit completely, or starting to charge for work that is WORTH paying for, I would hope they choose to keep developing but while charging a small fee. If you disagree with this, it's not your choice.

Just continue to use all of the awesome, freely available plug-ins ad profiles that are available, they are numerous. Just remember that every time you hit that DOWNLOAD button, also hit the reply and include your appreciation, it will not go un-noticed... It might just keep the next developer free.

-TC
 
TwoCigars said:
For anyone still trying to download and use this, refer to the earlier post in bold that says this project is dead.



Project was free... It was a compilation of all of the basic needs that people could download, toss in a folder and get botting with very little searching or knowledge... However, what started as a simple post to help the community became a massive amount of work to keep up with and reply to. Often times the community was more demanding/complaining than they were helpful/appreciative.

Replies like the one from tecknoe are a perfect example. You want to demand/require a dev to continue to make public releases for free...

This is happening more and more frequently on the forums. Thousands of downloads, dozens of complaints, the occasional "thank you" every few pages of the thread, with the original poster making 50% of all the posts... IE lots and lots of leechers.

I feel it's fair to say that most Devs have more than enough motivation when they are getting appreciation from the community and the occasional donation...
Anyways... BuddyMe decided to continue upgrading and improving KeyBot in a separate thread. It is easily the best key run plugin I had ever seen.

After having his thread disrupted numerous times with demands and complaints over basic quibbles, he decided to post about not continuing updating Keybot. When he made mention of appreciation for the thread or the idea of making it a pay-to-use plugin, there was a backlash from many members. This poor response sealed the deal.

It was unfortunate but you have to understand the large amount of time put in maintaining a thread and plugin both.

If the choice is having a dev quit completely, or starting to charge for work that is WORTH paying for, I would hope they choose to keep developing but while charging a small fee. If you disagree with this, it's not your choice.

Just continue to use all of the awesome, freely available plug-ins ad profiles that are available, they are numerous. Just remember that every time you hit that DOWNLOAD button, also hit the reply and include your appreciation, it will not go un-noticed... It might just keep the next developer free.

-TC
Click to expand...
do not report this thread, this thread cannot be locked till ether the code no longer works. or till the OP requests the project be archived. please do not report this thread again to Lock or do any other moderation actions unless you are the OP.
 
Bug

Im getting this bug on every profile idk what to do
[HIDE][QuestTools][TrinityApi] Unable to get Trinity Type!
Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.NullReferenceException: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
w QuestTools.Helpers.TrinityApi.GetStaticPropertyFromType(Type type, String propertyName) w c:\Users\TymekB\Desktop\Demonbudddy\Plugins\QuestTools\Helpers\TrinityApi.cs:wiersz 53
w QuestTools.ProfileTags.CombatSettingTag.<CombatSettingTask>d__2.MoveNext() w c:\Users\TymekB\Desktop\Demonbudddy\Plugins\QuestTools\ProfileTags\CombatSettingTag.cs:wiersz 91
--- Koniec śladu stosu z poprzedniej lokalizacji, w której wystąpił wyjątek ---
w System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
w System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
w Zeta.Bot.ActionRunCoroutine....()
--- Koniec śladu stosu wyjątków wewnętrznych ---
w Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
w Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
w Buddy.Coroutines.Coroutine.Resume()
w Zeta.Bot.ActionRunCoroutine.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Common.HookExecutor.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Common.HookExecutor.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Bot.BotMain.()

Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.NullReferenceException: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
w QuestTools.Helpers.TrinityApi.GetStaticPropertyFromType(Type type, String propertyName) w c:\Users\TymekB\Desktop\Demonbudddy\Plugins\QuestTools\Helpers\TrinityApi.cs:wiersz 53
w QuestTools.ProfileTags.CombatSettingTag.<CombatSettingTask>d__2.MoveNext() w c:\Users\TymekB\Desktop\Demonbudddy\Plugins\QuestTools\ProfileTags\CombatSettingTag.cs:wiersz 91
--- Koniec śladu stosu z poprzedniej lokalizacji, w której wystąpił wyjątek ---
w System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
w System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
w Zeta.Bot.ActionRunCoroutine....()
--- Koniec śladu stosu wyjątków wewnętrznych ---
w Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
w Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
w Buddy.Coroutines.Coroutine.Resume()
w Zeta.Bot.ActionRunCoroutine.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Common.HookExecutor.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Common.HookExecutor.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Bot.BotMain.()

Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.NullReferenceException: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
w QuestTools.Helpers.TrinityApi.GetStaticPropertyFromType(Type type, String propertyName) w c:\Users\TymekB\Desktop\Demonbudddy\Plugins\QuestTools\Helpers\TrinityApi.cs:wiersz 53
w QuestTools.ProfileTags.CombatSettingTag.<CombatSettingTask>d__2.MoveNext() w c:\Users\TymekB\Desktop\Demonbudddy\Plugins\QuestTools\ProfileTags\CombatSettingTag.cs:wiersz 91
--- Koniec śladu stosu z poprzedniej lokalizacji, w której wystąpił wyjątek ---
w System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
w System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
w Zeta.Bot.ActionRunCoroutine....()
--- Koniec śladu stosu wyjątków wewnętrznych ---
w Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
w Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
w Buddy.Coroutines.Coroutine.Resume()
w Zeta.Bot.ActionRunCoroutine.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Common.HookExecutor.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Common.HookExecutor.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Bot.BotMain.()

Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.NullReferenceException: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
w QuestTools.Helpers.TrinityApi.GetStaticPropertyFromType(Type type, String propertyName) w c:\Users\TymekB\Desktop\Demonbudddy\Plugins\QuestTools\Helpers\TrinityApi.cs:wiersz 53
w QuestTools.ProfileTags.CombatSettingTag.<CombatSettingTask>d__2.MoveNext() w c:\Users\TymekB\Desktop\Demonbudddy\Plugins\QuestTools\ProfileTags\CombatSettingTag.cs:wiersz 91
--- Koniec śladu stosu z poprzedniej lokalizacji, w której wystąpił wyjątek ---
w System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
w System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
w Zeta.Bot.ActionRunCoroutine....()
--- Koniec śladu stosu wyjątków wewnętrznych ---
w Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
w Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
w Buddy.Coroutines.Coroutine.Resume()
w Zeta.Bot.ActionRunCoroutine.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Common.HookExecutor.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Common.HookExecutor.Run(Object context)
w Zeta.TreeSharp.Action.RunAction(Object context)
w Zeta.TreeSharp.Action..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.TreeSharp.PrioritySelector..()
w Zeta.TreeSharp.Composite.Tick(Object context)
w Zeta.Bot.BotMain.()[/HIDE]
 
Yeah now would be a good time to lock the thread since it no longer works? :)
 
I get the bot running but it will not put a rift key frag in and open a portal also once inside it lags really bad only seems to do this with rift bots has no problem running regular bounties
 
Witch profile do you use for regular rift then ? :s
i search one
 
Hi, before all : I'm French.

So, I've the keyfarm profil : [KeyBot] KeyRuns by Toky and the others.
Some others profiles gratify me with : Bot Thread Ended. Was this requested?


And I'm ALWAYS stuck in Oasis at the corner stairs of the mine door.
He's stuck here and die... and die again, after some time and restart, I'm disconnected from the game due to innactivity if no monsters are here.
Same things happen reguraly in Silver Spire but at random places (Often at circles things with pillars or after killing the keywarden), but not so often than the oasis.

How I can fix this ? I can't leave my computer because of that (I've to do a tiny click to go down and all is ok) ^^

I'm putting the log here.

The log contain Oasis stuck and after boss kill in Silver Spire.
Thank in advance
 

Attachments

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