ski
Well-Known Member
- Joined
- Feb 12, 2010
- Messages
- 3,720
- Reaction score
- 48
Even if I were asking for a redesign surely now would be the best opportunity seeing as they are working out how to properly implement questing, hence the changes with forced quest list tags and such.
I think people need to sit back and understand what I am saying here.
I clearly stated that these were my opinions and perhaps even suggestions for the future implementation of the questing aspect as a whole.
Now yes I did criticise certain aspects of the current BETA release of questing but that was to further illustrate the points I was trying to make.
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).