Synik
Active Member
- Joined
- Jan 30, 2010
- Messages
- 995
- Reaction score
- 42
With the introduction of the new Quest Behaviors most of us filled with excitement but there are just still far too many issues with them and the documentation.
Some simply do not work, others bug out under certain conditions and we still miss some very important ones in order for us to progress them further. Fortunately most of the other writers and profile users have already documented the issues in both the forums and the bug tracker so I will not go into specifics here.
Instead I will move on to what we still need in terms of behaviors;
1. Set and Use Hearth. This has been a request for far too long, I know some users don't want profiles to use hearthstones but perhaps a toggle in HB to ignore the behavior line if its a use or set hearthstone.
2. The ability to use a spell/item on an item which is either equipped or is in a bag, this would greatly assist in quests such as the Death Knight needing to forge their weapon.
3. The ability to loot from a container in your inventory, some quests require you just to open the container, extract the items and then hand in.
4. Occasionally we are required to equip items for the duration of a quest, for example the Death Knight Quest where we are required to equip two daggers and attack an NPC. This would also need to temporarily block Autoequip or Equipshit, some will say run without them but it is simply not an option, especially as a Death Knight in the starter zone.
5. This one uses both points 3 and 4. So far I have come across one quest that will require this but no doubt there are or will be many more. The quest requires a Death Knight to loot a container in the inventory, equip the two daggers and then proceed to beat down NPCs until the NPC gives us the information we require to complete the quest. Perhaps a behavior or even an optional attribute to the behavior request of 4. which allows you to check for specific yellow text and quit fighting once it is displayed then move onto the next step.
6. The ability to take quests from items in the inventory, this doesn't even need to be a behavior, it could simply be a new thing in the PickUp lines which tells it to check for an item in the inventory.
7. The ability to talk to an NPC without requiring a you to be on a quest or even supply a quest ID. Some quests, specifically one in Durotar, requires you to talk to an NPC which then flashes up the new quest frame prompting you to accept that quest.
8. The ability to pick up and complete above mentioned quest types.
9. The fixing and the advancement of regecksqt's work on transport behaviors which saw us able to use elevators for the very first time.
10. The ability to walk away and grind in a surrounding area if an NPC is not there to interact with for whatever reason. Set it to something like 10mins before retrying and if after X amount of tries it still can not proceed it should log out or something. - this idea was posted by Khurune.
11. We need some sort of hard coded check to see if an NPC that we wish to interact with is in combat, if they are, assist and then proceed with the step once the NPC is available to interact with. This speeds up the process and makes you look far less bot like. - this idea was posted by Khurune
12. We all know what happens when we use the Useitem line and we end up in combat, now we can use an if statement to go back and recheck the quest to see if its complete and then proceed accordingly but how about the ability to check individual quest tasks so that we do not go round trying to redo a whole quest whilst there is only one or two which need to be finished.
13. The ability to call a macro or text in order to complete some of the new quests such as the Dwarven one where you /whistle at 6 rams. - this idea was posted by Blancharke
14. The ability to cast a spell from a vehicle at a location rather than being forced to use on NPCs.
Example;
15. The ability to use an item but place the "use" down at a specific point, pretty much like a mage would have to do when placing a Blizzard or a Flame Strike.
Also, finally, a nice clear and precise list of all current and future behaviors and their conditions/attributes because currently we have a mix up of information between the official HB quest behaviors and the ones which spurred most of this off from Natfoth.
I also welcome ideas for more sensible behaviors, if they are possible and would be of benefit to profile writing then I will update the list and credit accordingly.
Some simply do not work, others bug out under certain conditions and we still miss some very important ones in order for us to progress them further. Fortunately most of the other writers and profile users have already documented the issues in both the forums and the bug tracker so I will not go into specifics here.
Instead I will move on to what we still need in terms of behaviors;
1. Set and Use Hearth. This has been a request for far too long, I know some users don't want profiles to use hearthstones but perhaps a toggle in HB to ignore the behavior line if its a use or set hearthstone.
2. The ability to use a spell/item on an item which is either equipped or is in a bag, this would greatly assist in quests such as the Death Knight needing to forge their weapon.
3. The ability to loot from a container in your inventory, some quests require you just to open the container, extract the items and then hand in.
4. Occasionally we are required to equip items for the duration of a quest, for example the Death Knight Quest where we are required to equip two daggers and attack an NPC. This would also need to temporarily block Autoequip or Equipshit, some will say run without them but it is simply not an option, especially as a Death Knight in the starter zone.
5. This one uses both points 3 and 4. So far I have come across one quest that will require this but no doubt there are or will be many more. The quest requires a Death Knight to loot a container in the inventory, equip the two daggers and then proceed to beat down NPCs until the NPC gives us the information we require to complete the quest. Perhaps a behavior or even an optional attribute to the behavior request of 4. which allows you to check for specific yellow text and quit fighting once it is displayed then move onto the next step.
6. The ability to take quests from items in the inventory, this doesn't even need to be a behavior, it could simply be a new thing in the PickUp lines which tells it to check for an item in the inventory.
7. The ability to talk to an NPC without requiring a you to be on a quest or even supply a quest ID. Some quests, specifically one in Durotar, requires you to talk to an NPC which then flashes up the new quest frame prompting you to accept that quest.
8. The ability to pick up and complete above mentioned quest types.
9. The fixing and the advancement of regecksqt's work on transport behaviors which saw us able to use elevators for the very first time.
10. The ability to walk away and grind in a surrounding area if an NPC is not there to interact with for whatever reason. Set it to something like 10mins before retrying and if after X amount of tries it still can not proceed it should log out or something. - this idea was posted by Khurune.
11. We need some sort of hard coded check to see if an NPC that we wish to interact with is in combat, if they are, assist and then proceed with the step once the NPC is available to interact with. This speeds up the process and makes you look far less bot like. - this idea was posted by Khurune
12. We all know what happens when we use the Useitem line and we end up in combat, now we can use an if statement to go back and recheck the quest to see if its complete and then proceed accordingly but how about the ability to check individual quest tasks so that we do not go round trying to redo a whole quest whilst there is only one or two which need to be finished.
13. The ability to call a macro or text in order to complete some of the new quests such as the Dwarven one where you /whistle at 6 rams. - this idea was posted by Blancharke
14. The ability to cast a spell from a vehicle at a location rather than being forced to use on NPCs.
Example;
PHP:
<CustomBehavior File="VehCastSpellAt" QuestId="1234" X="" Y="" Z="" />15. The ability to use an item but place the "use" down at a specific point, pretty much like a mage would have to do when placing a Blizzard or a Flame Strike.
Also, finally, a nice clear and precise list of all current and future behaviors and their conditions/attributes because currently we have a mix up of information between the official HB quest behaviors and the ones which spurred most of this off from Natfoth.
I also welcome ideas for more sensible behaviors, if they are possible and would be of benefit to profile writing then I will update the list and credit accordingly.
Last edited:
