Don't get me wrong, I'm not attacking you, I'm similarly stating my own opinion. The reason now isn't the best time is because the back-end functionality of HB (essentially, the meat and potatoes of the core) is the most important factor. Having xml tags and quest profiles are well and good but they are pointless if the core doesn't perform as it should, know what I mean? If the bot is running around, spinning in circles, and jumping off cliffs - it doesn't really matter how the quest profile is formatted. On the other hand, if the bot can run 90% of the quests types out of the box, and can navigate its way around well, and altogether runs like a well-oiled machine, then the front end can be changed in any number of ways pretty easily and you know the bot will reply in kind. I'd be more comfortable changing the front end when I know the back end is solid, then changing the front end and having issues but not knowing if they are because of the front end changes or because of an existing bug in the back end. (As an aside, when I say front end I'm referring to user accessible functionality such as the CC api, plugin API, or quest/profile API, whereas when I refer to back end I mean the HB program and its logic itself).
Yes I agree completely in regards to the back end needing to be running accordingly before the front end stuff. What I intended to do was suggest other methods based on my opinions that some of the users, including myself, are interested in. Doing so would allow the devs to mull things over before making a final release in the future The only downside to voicing my opinions was having to use the current builds as a basis to stress my points against.
The current questing can be sorted to do quests in the certin order you want them to do. The key thing is in making the profile. As you stated there are some that want to make exstensive profiles to do things in a certin order. This yes, I do understand we do not have controll on the turn in of a quest. But we do have the ability to say do a, b, d, and z quest. Then once done with those do c, x and y quest. Then when done, walk/ride to this area and do e, f, and w, then ride back to first area and do g, h, i, j, k, l and m. The current settings with the force quest, is you need to set up a sub profile and say you want it to do, a, b, d, and z quest. Then make a new sub profile and tell it to do, c, x and y. Then a new sub profile to go to new area and do, e, f, and w. Then a new sub profile to go back to the first area and do, g, h, i, j, k, l and m. It is there, it just has to be writen out of which you want to do in each sub profile instead of doing massive ones in one big force list.
By all means, ideas can never hurt. Just keep in mind the line between "ideas" and "demands" is a thin one - and one of those will likely piss people off
Putting a list of quests in a subprofile does not determine in what order those are done, those quests will still be completed in a random manner.
Ok, so your saying if you give it two quests that should be done, it does not matter that they are done in order but need to be done before the next two. You then put the first two in one sub profile, then you make a new sub profile for the next two. This now will have it do sub profile 1, which has only 2 quests in it. Then it will do sub profile 2 with only 2 quests in it. Thats the point, you can get it very detailed, you just need allot of sub profiles to tell it what order and so forth. Down to having a sub profile per quest.
Thing is, so far my bot have been ignoring it when I had minlevel & maxlevel on the same lvl (lvl 11) so I haven't been any successful in creating subprofiles for quest priorites. Care to wager, mate?
Surely that concept would not work due to the usage of min/max levels before moving onto the next sub profile? EDIT: Looks like wajke beat me to a response
i'm of two minds on this subject, on one hand if enough thought went into the exact points required and every click was planned out in one massive file, it could streamline questing through an area to probably the maximum rate available without powerlevelling. on the other hand the ability to program the bot's AI to adapt to most of the situations seen in WoW would just be plain cool, and have the benefit of adaptability.
Once I heard about a beta-release of questing I knew that sooner or later ppl will getting impatient and threads like this will occure. I guess the way you think is ok, dear threadopener, but please remember that this is in construction. I agree that it sometimes fucks you up if HB won't work like you will but we have to be more patient. Furthermore I'm verry verry happy that we have a pre/beta-release of questing to see how it works and to help the devs to fix bugs. So just relax and wait for some more time, drink some tee or red-bull and enjoy the great bot we have^^
