znuffie
Active Member
- Joined
- Feb 23, 2010
- Messages
- 864
- Reaction score
- 30
Radius for HotSpots.
If we have it for blackspots, I'm pretty sure there could be a way to implement it for hotspots.
It's annoying to see your char being in a hotspot, having mobs that are 40yds away and just ignoring them, because your pull range is 30yds...
Would be nice to have a way to declare a "move to target" radius.
Documentation for all .xml files, supported tags etc.
Yes, I'm aware there are quite a few posts about all the tags that a profile supports - but what is the latest revision?
What's the difference between having a ProtectedItems.xml and having a < ProtectedItems > tag in your profile? Can I put my items in both of the XML files and just have them working like it should? What's the priority if an item is ProtectedItems.xml but it's also in the forcemail list in a profile?
If we can blacklist quests in our profiles, why can't we do it in QuestSettings.xml? Why does that file exists? Couldn't we just include < MinQuestLevel > and < MaxQuestLevel > in our profiles?
Couldn't we have a global blacklisted quests list that all profile could use as a base, but, in the same time, allow all profile creators to define extra-blacklisted quests?
Does < Item >< /Item > still work? I'm guessing < Item Id="" Name="" > is the prefered way. But should we keep using < Item >< /Item > or not?
Capitalisation of attributes. Is it required or no? XML as a standard defines that all attributes (and tags) should be lowercase, but in the same time, it should be case-insensitive. Yet, a lot of people recommend using Id instead of id, and some even swear that using id just doesn't work.
Comments in profiles. Some of us like to keep our work clean, yet we can't see to get the comments in a profile working most of the time.
I can't understand how the order of coords work for Vendors, Mailboxes and Hotspots.
If we have multiple vendors and mailboxes in a profile/subprofile (or even global, in the hbprofile), will it calculate the distance and it will pick the closest one?
What about hotspots? I know there's a randomise option, but if that option is set to false, what's the order of hotspot travels? It's the order from our profile? Once started, the bot will move to the closest hotspot relative to its location or to the first one in the list (per GrindArea)?
Meshing. I know, HB2 has its own mesh that's pretty cool to use! But some parts are horribly meshed - where do we report this? Can we fix it ourselves?
EDIT: Clarification.
Consider the scenario above us (yes, my paint skills suck).
Orange is the pull radius.
Red are hotspots (we have 1-2-3-4 hotspots in here).
Green dots are mobs we want to grind.
As far as I know, this is how it works: Bots moves to hotspot 1. Pulls mobs in our pull area, after he loots, he gets a new target while/after he loots (because he's changing position). If he can't find any valid target in his radius, he moves to a new hotspot.
Now, if this works how I think it does, it will move to hotspot 2, then hotspot 3, then hotspot 4. Normally we should make hotspots 1 and 2 close to each other, so we clear the whole area around us, then move to a new area. But if we have RandomizeHotspots set to true, it will (probably) do something like hotspot1, hotspot4, hotspot3, hotspot2 and so on - and that pretty much makes us looks too botish.
But, if we would consider a range for hotspots (the purple circles in the image), the bot would know to grind the whole area before moving to a new hotspot and we wouldn't need to create lots of hotspots in a larger-than-our-pull-range radius. Hope I made myself clear
These are just questions that I couldn't find any answer in the past few days while I've started creating profiles.
If we have it for blackspots, I'm pretty sure there could be a way to implement it for hotspots.
It's annoying to see your char being in a hotspot, having mobs that are 40yds away and just ignoring them, because your pull range is 30yds...
Would be nice to have a way to declare a "move to target" radius.
Documentation for all .xml files, supported tags etc.
Yes, I'm aware there are quite a few posts about all the tags that a profile supports - but what is the latest revision?
What's the difference between having a ProtectedItems.xml and having a < ProtectedItems > tag in your profile? Can I put my items in both of the XML files and just have them working like it should? What's the priority if an item is ProtectedItems.xml but it's also in the forcemail list in a profile?
If we can blacklist quests in our profiles, why can't we do it in QuestSettings.xml? Why does that file exists? Couldn't we just include < MinQuestLevel > and < MaxQuestLevel > in our profiles?
Couldn't we have a global blacklisted quests list that all profile could use as a base, but, in the same time, allow all profile creators to define extra-blacklisted quests?
Does < Item >< /Item > still work? I'm guessing < Item Id="" Name="" > is the prefered way. But should we keep using < Item >< /Item > or not?
Capitalisation of attributes. Is it required or no? XML as a standard defines that all attributes (and tags) should be lowercase, but in the same time, it should be case-insensitive. Yet, a lot of people recommend using Id instead of id, and some even swear that using id just doesn't work.
Comments in profiles. Some of us like to keep our work clean, yet we can't see to get the comments in a profile working most of the time.
I can't understand how the order of coords work for Vendors, Mailboxes and Hotspots.
If we have multiple vendors and mailboxes in a profile/subprofile (or even global, in the hbprofile), will it calculate the distance and it will pick the closest one?
What about hotspots? I know there's a randomise option, but if that option is set to false, what's the order of hotspot travels? It's the order from our profile? Once started, the bot will move to the closest hotspot relative to its location or to the first one in the list (per GrindArea)?
Meshing. I know, HB2 has its own mesh that's pretty cool to use! But some parts are horribly meshed - where do we report this? Can we fix it ourselves?
EDIT: Clarification.
Consider the scenario above us (yes, my paint skills suck).
Orange is the pull radius.
Red are hotspots (we have 1-2-3-4 hotspots in here).
Green dots are mobs we want to grind.
As far as I know, this is how it works: Bots moves to hotspot 1. Pulls mobs in our pull area, after he loots, he gets a new target while/after he loots (because he's changing position). If he can't find any valid target in his radius, he moves to a new hotspot.
Now, if this works how I think it does, it will move to hotspot 2, then hotspot 3, then hotspot 4. Normally we should make hotspots 1 and 2 close to each other, so we clear the whole area around us, then move to a new area. But if we have RandomizeHotspots set to true, it will (probably) do something like hotspot1, hotspot4, hotspot3, hotspot2 and so on - and that pretty much makes us looks too botish.
But, if we would consider a range for hotspots (the purple circles in the image), the bot would know to grind the whole area before moving to a new hotspot and we wouldn't need to create lots of hotspots in a larger-than-our-pull-range radius. Hope I made myself clear
These are just questions that I couldn't find any answer in the past few days while I've started creating profiles.
Last edited:
