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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[A - Quest] Human 1-60 [KaZ]

Status
Not open for further replies.
You have forgotten to turn in the quest: <PickUp QuestName="Report to Goldshire" QuestId="54" GiverName="Marshal McBride" GiverId="197" />

Yea i noticed that too =( that is fixed in the new ones i am posting later today, thanks for the heads up =)
 
Hey Killa, i don't post much but want to thank you for sharing your hard work. I am writing my own questing script and was using some of your work to save me some time.
 
Changing current profile to [Questing|Alliance]KillaKaZ 15-20 Questing | Redridge
Pull Max Distance set to 5
Pull Min Distance set to 3
Could not find quest giver NPC with ID 342 in database.
Could not create current in quest bot!
Stop called!
ThreadAbortException caught... did the user press the 'Stop' button?

need to get closer to questgiver, this is an issue with HB's database sorry.

i been trying to add location tags to most npc that give issues so ill note that one thank you =)
 
need to get closer to questgiver, this is an issue with HB's database sorry

Yeah, noticed that and deleted my post.

My HB stopped randomly and couldnt pick up any quests after that. Restarted it and working fine now :)
 
As an update i am currently working on the 30+ profile and as you know there are a lot more quests to do to level at higher levels, so i am working on it, just so everyone knows =P
 
working good other than just a lil babysitting on a human paladin. looks as though this would be better suited for a BOA geared toon and not a fresh one as it likes to die Very often in this. But it does get the job done eventually. I would imagine that a priest or mage might have some severe difficulty in running this with no BOA help.


Thanks for the Profile !!!!
 
Last edited:
working good other than just a lil babysitting on a human paladin. looks as though this would be better suited for a BOA geared toon and not a fresh one as it likes to die Very often in this. But it does get the job done eventually. I would imagine that a priest or mage might have some severe difficulty in running this with no BOA help.


Thanks for the Profile !!!!

it's funny you say that i am currently re-running it with a priest and a mage following my toon im making the quest with, adjusting blackspots and such as i encounter them, so some changes will be made for that, thank you for your feedback =)
 
Nice!

Looking forward to lv30~xx quest order. Any ETA or help you need with?
 
Nice!

Looking forward to lv30~xx quest order. Any ETA or help you need with?

Juat alot more quests to do as you get higher lvl, at 40 now progressing way up, on a side note i did get it to use a teleport so no having to split up the file =P
Most likely i may release a 15-40 so i can get some extra help testing as i take it to 60 so i can fix and update as i go and people don't have to wait as long lol =P
 
No pickup or turnin for this quest which stops questing progress on 15-30: <Objective QuestName="Deep Roots" QuestId="26744" Type="CollectItem" ItemId="60295" CollectCount="1" />

Also:

Could not find quest giver NPC with ID 43886 in database.
Could not create current in quest bot!
Stop called!
[Quest Protector] Bot shutdown detected, clearing item protection.

>>> STOPPING ShamWOW v4.2.09b by Bobby53
ThreadAbortException caught... did the user press the 'Stop' button?
 
No pickup or turnin for this quest which stops questing progress on 15-30: <Objective QuestName="Deep Roots" QuestId="26744" Type="CollectItem" ItemId="60295" CollectCount="1" />

Also:

Could not find quest giver NPC with ID 43886 in database.
Could not create current in quest bot!
Stop called!
[Quest Protector] Bot shutdown detected, clearing item protection.

>>> STOPPING ShamWOW v4.2.09b by Bobby53
ThreadAbortException caught... did the user press the 'Stop' button?

Yes i came accross that there are 2 or 3 quests that being removed or replaced to keep it fluid, thank you for the report, all of these have been updated.. i am running the 3rd toon through the 15-40 now so far so good

Edit: basicly i run 1 toon through while im doing and making the quest profile then i have it followed by 2 clothie toon priest and mage to make sure it is not overbarring to complete by any class. then i release it for testing by public. i thank you all for your help and feedback during the process =)
 
I'm getting this. I did the class quest by hand and I'm trying to start it again.

This is from the Debug Log.
Code:
[11:29:01 PM:451] System.Threading.ThreadAbortException: Thread was being aborted.
   at Microsoft.Win32.NativeMethods.WaitForSingleObject(SafeProcessHandle handle, Int32 timeout)
   at System.CodeDom.Compiler.Executor.ExecWaitWithCaptureUnimpersonated(SafeUserTokenHandle userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine)
   at System.CodeDom.Compiler.Executor.ExecWaitWithCapture(SafeUserTokenHandle userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine)
   at Microsoft.CSharp.CSharpCodeGenerator.Compile(CompilerParameters options, String compilerDirectory, String compilerExe, String arguments, String& outputFile, Int32& nativeReturnValue, String trueArgs)
   at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)
   at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)
   at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)
   at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, String[] sources)
   at Styx.Logic.Profiles.Quest.Order.FlowChanging.ConditionHelper.CompileAndEvaluateExpression(String[]& buildErrors, Boolean& evaluatedExpression)
   at Styx.Logic.Profiles.Quest.Order.FlowChanging.ConditionHelper.a.b()
   at QuestBot.Actions.PerformQuestObjectiveOrdered.a(IfNode A_0)
   at QuestBot.Actions.PerformQuestObjectiveOrdered.a.a()
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.a.b()
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.Decorator.a.a()
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.a.b()
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.a.b()
   at TreeSharp.Composite.Tick(Object context)
   at Styx.Logic.BehaviorTree.TreeRoot.b()
[11:29:01 PM:451] Cleared POI

This is from the "Log"
Code:
Changing current profile to [KaZ] Alliance 1-15 Human [QuestOrder]
Could not find quest with ID 28764! (Or could I: False)
Could not create a performable quest objective for objective with ID 49871!
Can not turn in quest Beating them Back! (ID: 28764) because I don't have it in my quest log! (Or do I: False)
Could not find quest with ID 28772! (Or could I: False)
Could not create a performable quest objective for objective with ID 49874!
Can not turn in quest Lions for Lambs (ID: 28772) because I don't have it in my quest log! (Or do I: False)
Stop called!
ThreadAbortException caught... did the user press the 'Stop' button?
 
Ready for the 15-40. I've got everything but a priest and druid to 30 with your current profile and I hate priests and druids so I'll wait patiently for your release. As far as feedback goes, everything went pretty smooth, the only thing I noticed is that depending on whether kill between hotspots and gathering professions, toons would pick up extra XP which sometimes caused it to level to quickly and quests get skipped (or not turned in even though they were complete). Not sure if there's a way to write these profiles where the level cap in each section isn't so hard and fast. Other than that, these profiles were a riot, very fun and not a lot of babysitting needed.
 
Status
Not open for further replies.
Back
Top