How plugins affect profiles

[Rusty_Trombone]

I want to ask any developer in here a question. How plugins that affect looting (eg a plugin that searches for trasures) interact with profiles. I tested a plugin in the uncatalogued...category and I realized that when it searches for chest and find one, it sets it as the new PoI. That works bad with quest profiles (eg 6.2 apexis dailies) and ignores mobs etc. If I deactivate the search for chests feature, the profile will work normally. How can one rectify this?

 

[aash]

How plugins that affect looting (eg a plugin that searches for trasures) interact with profiles.

It is a good question!
Such erroneous behavior is the plugin`s developer fault. In the course of profile execution BotBase is changing it`s state. BotBase expects that state can not be chaged from the outside. So let's imagine that BotBase programmer defined following state transition A -> B and plugin was changed it to A -> X so BotBase will try to find matching X -> ??? transition. In your case plugin is interfereing with normal BotBase workflow.

IMHO plugins should not interfere with BotBase workflow, or at least try to revert it`s changes into the state.

 

[Rusty_Trombone]

Thank you for your response. This raised several questions but I will only ask 2

1. When should one choose to develop a Botbase vs a profile based on the default botbases? And do you happen to know any botbase development resources for HB?

2. So, you say that plugins should only do specific things that will not mess up with bot functionallity unless they imlpement some cleanup like restore the state. The problem is that a plugin developer might now know the botbase specifics. Anyway, are there any guidelines for plugin development?

 

[Aion]

Thank you for your response. This raised several questions but I will only ask 2

1. When should one choose to develop a Botbase vs a profile based on the default botbases? And do you happen to know any botbase development resources for HB?

2. So, you say that plugins should only do specific things that will not mess up with bot functionallity unless they imlpement some cleanup like restore the state. The problem is that a plugin developer might now know the botbase specifics. Anyway, are there any guidelines for plugin development?

Generally speaking, the default Questing Botbase is linear, it perform scripted behaviors one-at-a-time, so for compatibility it is not recommended to use Plugins, aimed at heavy movement (like chest collecting ones) with complex questing profiles (like Kicks 1-100 for example) for several reasons.

1. The plugin itself, (unless it is part of the questing profile, Like Thebrodieman's, which plugins work in synergy with his questing profiles) is completely unaware what the Questing profile is performing, and it could interrupt a critical behavior, coded within the Quest profile - like Escort, gauntlet or scripted "dance" behavior.
I think this is the sole reason, why Questing is not recommended to be run in Mixed mode too.

2 With the above taking into account, if plugin is being developed, obviously it cannot timelapse to former moments of time, but a good move would be to pause the plugin, when incompatible behavior is performed by the botbase. I can see this only if the profile and plugin work in synergy. Both should be aware of the "other's presence"

 

[roboto]

generally speaking, plugins shouldnt be ment to override/pause/freeze or work into a botbase, they're plugins for that reason.

 

[Rusty_Trombone]

Generally speaking, the default Questing Botbase is linear, it perform scripted behaviors one-at-a-time, so for compatibility it is not recommended to use Plugins, aimed at heavy movement (like chest collecting ones) with complex questing profiles (like Kicks 1-100 for example) for several reasons.

1. The plugin itself, (unless it is part of the questing profile, Like Thebrodieman's, which plugins work in synergy with his questing profiles) is completely unaware what the Questing profile is performing, and it could interrupt a critical behavior, coded within the Quest profile - like Escort, gauntlet or scripted "dance" behavior.
I think this is the sole reason, why Questing is not recommended to be run in Mixed mode too.

2 With the above taking into account, if plugin is being developed, obviously it cannot timelapse to former moments of time, but a good move would be to pause the plugin, when incompatible behavior is performed by the botbase. I can see this only if the profile and plugin work in synergy. Both should be aware of the "other's presence"

Funny you replied because the initial post came from your Apexis 6.2 profile! It never engages with the Tannan rares! I don't know if you have blacklisted these mobs in order to satisfy lower ilvl toons but it surely does not engage. The same with treasure. It will not gather any. Of course you never said you would. So, I used a plugin that had some issues. This is the reason for the discussion!