[Questing Profiles] Do we bot on runners

[Imortel]

Blacklisting or whitelisting quests is a pain either way.

People still don't realize that either way it will require a community effort to make profiles viable to level.
The grind profiles have been made by some people that took the time and worked(hard or not) to chose areas where the bot will get more XP and have lots of mobs to grind on.
Its the same with quests.
Sooner or later there will be this questing profiles. Most people just expect them to pop up on the forums, load them and get to 80 in no time.

Anywayz.
I'd like to see the "Do this quests" implementation since it would be rather easy just to go on wowhead or any WoW database and go zone by zone and chose the quests you think the bot will be able to do easy. Also as stated around here, there are alot of leveling guides that will make creating a profile even easier due to the fact that we already have a sort of list already made.

We just have to adapt it to our needs.

 

[tehehe83]

In the next beta, when making 1-60 profiles, we do have the option to use a forcedquestlist like this:

    <ForcedQuestList>
      <Quest Id="287" Name="Frostmane Hold" />
      <Quest Id="291" Name="The Reports" />
      <Quest Id="319" Name="A Favor for Evershine" />
      <Quest Id="315" Name="The Perfect Stout" />
    </ForcedQuestList>

However once you get over level 5 you get a lot of quests with npcs that run away on low health and thus aggro friends and get your toon killed.

Even if we only do them when they are green, its still a pain and slows down your leveling compared to grinding spiders. But you do appear far less botlike.

What do you guys think? Bot quests that include runners or no?

Make it an option? Make everything potentially unstable or not working perfectly as an option if possible so we can choose ourselfs if we want to risk it.

 

[robbdeman]

Will this prevent the bot from doing one quest turning it in, going back to the same mob area do another quest, turn it in, and go back a 3rd time for another quest, or will it improve how it handles quests, i.e. no turn in till all quests are done in list from current sub profile.

 

[Hawker]

Will this prevent the bot from doing one quest turning it in, going back to the same mob area do another quest, turn it in, and go back a 3rd time for another quest, or will it improve how it handles quests, i.e. no turn in till all quests are done in list from current sub profile.

No connection.

 

[style1one]

Will this prevent the bot from doing one quest turning it in, going back to the same mob area do another quest, turn it in, and go back a 3rd time for another quest, or will it improve how it handles quests, i.e. no turn in till all quests are done in list from current sub profile.

It would be nice to have a forced turn in.

 

[Morga]

I think you should add a check box to complete quest in the same zone. When I was testing on the new druid she ran all the way to westfall to grab quest that were 4-5 levels to high for her. She then ran all the way back to logging camp in elwynn forest. But that's just me I like check boxes!

Morga

 

[Nuok]

Can you elaborate on exactly what a forced quest list will achieve?

Will we be able to control the order that quests are picked up, done in and turned in? Or is it mearly a white list?
If it is just a white list could you call for it to re-asses which quest to do more often like after each mob is killed or every 30 seconds; or maybe have a more distance weighted system. Maybe these are already in place but currently the bot runs all over the place and the result is less xp than just grinding because it so unoptimized.

 

[Xume]

If the general vote will be Yes, I would like to suggest to implement some smarter ressurection logic regarding not to ress in the middle of the crowd but try and look for a "safer" spot.
With the new navigation using the whole terrain shouldn't be an issue.

I vote yes and agree with LiquidAtoR

 

[style1one]

Can you elaborate on exactly what a forced quest list will achieve?

Will we be able to control the order that quests are picked up, done in and turned in? Or is it mearly a white list?
If it is just a white list could you call for it to re-asses which quest to do more often like after each mob is killed or every 30 seconds; or maybe have a more distance weighted system. Maybe these are already in place but currently the bot runs all over the place and the result is less xp than just grinding because it so unoptimized.

From what I have gathered, you create a subprofile, in that subprofile you say what quests to do. So say you want to do a spacific order, then its just a manor of setting up a subprofile for each quest in order.

 

[Zher0]

I think we should, also when do you think this will be out ?

 

[tMsje]

Voted yes. Even if it slows down leveling it will appear much less bot like and so its safer, and i prefer the safe way. Plus most CC's can handle runners pretty well.

 

[npittas]

I also voted Yes. It whould be nice to now if the ForceQuest will also have Questqueue-like option.
If you can force a quest in a specific order that whould be even more helpfull for the profile-makers.

Making it like this
<ForcedQuestList>
<Quest OrderNum=1 Id="287" Name="Frostmane Hold" />
<Quest OrderNum=2 Id="291" Name="The Reports" />
<Quest OrderNum=3 Id="319" Name="A Favor for Evershine" />
<Quest OrderNum=4 Id="315" Name="The Perfect Stout" />
</ForcedQuestList>

So you can either re-arrange the QuestList or Use a OrderNume-like Variable to determine the order your bot will complete them

 

[style1one]

I also voted Yes. It whould be nice to now if the ForceQuest will also have Questqueue-like option.
If you can force a quest in a specific order that whould be even more helpfull for the profile-makers.

Making it like this
<ForcedQuestList>
<Quest OrderNum=1 Id="287" Name="Frostmane Hold" />
<Quest OrderNum=2 Id="291" Name="The Reports" />
<Quest OrderNum=3 Id="319" Name="A Favor for Evershine" />
<Quest OrderNum=4 Id="315" Name="The Perfect Stout" />
</ForcedQuestList>

So you can either re-arrange the QuestList or Use a OrderNume-like Variable to determine the order your bot will complete them

Very nice idea, and if able to do so that way we could cut allot of un needed travel time down which is that much quicker to level cap.


<ForcedQuestList>
<Quest TurnInNum=1 Id="287" Name="Frostmane Hold" />
<Quest TurnInNum=2 Id="291" Name="The Reports" />
<QuestTurnInNum=3 Id="319" Name="A Favor for Evershine" />
<Quest TurnInNum=4 Id="315" Name="The Perfect Stout" />
</ForcedQuestList>

 

[Lt.Leon]

Looks like the favor is in with runners. Give the people what they want! lol

 

[Nuok]

I also voted Yes. It whould be nice to now if the ForceQuest will also have Questqueue-like option.
If you can force a quest in a specific order that whould be even more helpfull for the profile-makers.

Making it like this
<ForcedQuestList>
<Quest OrderNum=1 Id="287" Name="Frostmane Hold" />
<Quest OrderNum=2 Id="291" Name="The Reports" />
<Quest OrderNum=3 Id="319" Name="A Favor for Evershine" />
<Quest OrderNum=4 Id="315" Name="The Perfect Stout" />
</ForcedQuestList>

So you can either re-arrange the QuestList or Use a OrderNume-like Variable to determine the order your bot will complete them

This, as long as we can set quests completed to be done at the same time, (using the same order number's)

 

[deltasniper3]

1-60 only tho?

 

[LiquidAtoR]

1-60 only tho?

Rome was not build in a day either.

 

[Lt.Leon]

Rome was not build in a day either.

But the world was built in a week :/

 

[mopysworld]

I like but....

My impression of how questing was going to be done was you created a profile with the quest you wanted to do... aka such as profiles created along the lines of the more common leveling guides out there. The only issues/question i have with the tag line. Is there a way to tell it when to turn in the quest. Its much easier to do all the quest you picked up then turn them in all at once... or if a quest requires lets say a time limit to have it able to do that quest first then continue on.

Majority of the issues ive been reading about are mainly 2 areas....
1. rezzing in the middle of mobs. Should be a simple fix to add a range checker of nearest mob(hostile) if they are within x distance dont rez and move to another location where they are not. that should prevent the rez death cycle.
2. Moving to the quest location and ignoring mobs on the path there even if they are hitting you. Im still unclear if the CC handles the code for the move to aka navigation phase were does it fit(pull/combat/rest/etc...). If so putting a check for hostile aggression on any mob on the distance list within say 20m. If so target them first that way the toon works to the quest location like a normal person and not run head long pulling a jenkins. If the pathing/navigation part is handled internally is there and option to add that part of the code be be overrided using the sequence manager?

 

[Mario27]

I vote yes to I hope the bug get fixed to evryfew lvls it says no activity refrsh quest even if you edit the quest settings setminquest setmaxquest

and i dont know if this is a bug evrytime it gets killed by a mob it just go there again and res and gets killed sometimes again it would be nice if it blackspoted that and come back later