What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Plugin] AdvancedItemFilter RELOADED !

Status
Not open for further replies.
Can you add plz
ItemIs Map and ItemIsMirror ->>>>>>>>>>>> SELL
ItemIs Map and ItemIsRare ->>>>>>>>> SELL

i want to sell all rare maps and all mirror ones

Rare maps should be fine using

item.IsMap and item.IsRare

Need to figure out how to find out one if mirrored or not ;)
 
@ toNyx

I have my filters set to ID all rares except accessories and to sell all ID rares. No issues before

Since trying to use the AIF pluging, I'm having difficulties with the bot ID'ing all rares (not uniques) and stashing. I'm trying to trouble shoot this but when i go to tools -> Item Filter Editor i get a popup that states "current bot does not support using Item Filter Editor"

I cannot get into the settings unless i shut down and reopen the bot.

Any idea what's causing this or how to rectify the issue?

Thanks,

JayDee
 
@ toNyx

I have my filters set to ID all rares except accessories and to sell all ID rares. No issues before

Since trying to use the AIF pluging, I'm having difficulties with the bot ID'ing all rares (not uniques) and stashing. I'm trying to trouble shoot this but when i go to tools -> Item Filter Editor i get a popup that states "current bot does not support using Item Filter Editor"

I cannot get into the settings unless i shut down and reopen the bot.

Any idea what's causing this or how to rectify the issue?

Thanks,

JayDee

It's not an issue, it's how it's supposed to work. Next build will remove static filters entirely, people will be forced to use CustomRules with AIF. No matter what. Some people reported that issue, we're still investigating and found some things, need to double check
 
Heyho toNyx!

Just noticed "IncreasedAttackSpeed" is missing from the available values :)
 
Is there any reason why running this plugin seems to disable using Item Filter Editor from tools? Says something like "this bot cannot run the editor" or smth, before I installed this plugin it wasn't the case. Or is it unrelated and an issue on my side?
 
I have another suggestion. We all know that sometimes we end up with 30 rings but no amulets. There is a vendor recipe that allows us to convert Paua and Coral Rings into Paua/Coral Amulets if we add 7 Iron Rings( doesn't matter if they are normal or blue, and its itemlevel doesn't matter either).

We could set for instance if the ring:amulet ratio is bigger than X then we convert a ring into an amulet. We also had to pick up White/Blue Iron Rings to make this possible :)
 
I have another suggestion. We all know that sometimes we end up with 30 rings but no amulets. There is a vendor recipe that allows us to convert Paua and Coral Rings into Paua/Coral Amulets if we add 7 Iron Rings( doesn't matter if they are normal or blue, and its itemlevel doesn't matter either).

We could set for instance if the ring:amulet ratio is bigger than X then we convert a ring into an amulet. We also had to pick up White/Blue Iron Rings to make this possible :)
This.
 
Is there any reason why running this plugin seems to disable using Item Filter Editor from tools? Says something like "this bot cannot run the editor" or smth, before I installed this plugin it wasn't the case. Or is it unrelated and an issue on my side?

I wondered this myself. As I dont want my entire stash filled up with white items I dont want to chance
 
Na dude, I'm just trolling you. Tony fixed a bunch of bugs(with my awesome help, by awesome, I mean constant bitching).
So other features are planed as other features tba I assume. Gotta suck up to Tony if you really want something, otherwise code it yourself.
 
Na dude, I'm just trolling you. Tony fixed a bunch of bugs(with my awesome help, by awesome, I mean constant bitching).
So other features are planed as other features tba I assume. Gotta suck up to Tony if you really want something, otherwise code it yourself.

Dude cmon, I'm at work stop telling people to suck me... it's getting me horny.

Homerrox, in the next release build AIF will exclude ENTIRELY default static filters when using CustomRules, because it was causing major issues with decisions. Lot of issues were addressed and fixed as I already said in PM, and it seems to work flawlessly now, lot of debug has been added.

Tho, even with all the things I've put in place, it seems like sliders values are still going nuts, why? I don't know. It's a raw value that is set when moving sliders around. They're never changed, and used correctly... I'll dig deeper and try to find why it's doing that tho. It's the only issue the release build still have (or maybe not anymore, who knows)

My bots are in a testing phase until 1PM, and will see if anything got stashed above the sliders thresholds.

Anyway, I would also give a little information about the BETA and other things with the upcoming awakening :

- As soon as this build is stable and 99.9% usable AFK for days/weeks, I'll work on the Awakening version.

Loads of changes occured to tasks/plugins/interfaces and it'll most likely have to be rebuilt around this new system. This won't change the logic, but the way it's triggered and this way it'll be excluded from the Bot's processing thread/tasks. Plugins will now be "independants" and lot of stuff is possible, we already talked about few things, that could help us (me, alcor, dbf, exv, jyam or whoever is on this fucking channel) to communicate and act in our plugins, without having to code things.

A simple example, with the actual state of the BETA, we will be able to broadcast things to plugins. It means 1 single plugin can provide others Functions, Methods, Events, or whatever exists in this bot.

It's for now "experimental" and needs to be tested but we can expect a synergy between plugins in the extension :)

The shit is real !
 
Hey toNyx! Thanks for all of the effort put into this. This plugin has worked phenomenally.

I'm running 1.0.1.0, and it tells me that that the current bot does not support using the item filter editor. I really don't mind, because the plugin takes care of almost everything I need. But it still stashes non quality gems, and utility flasks, which I don't want it to do. I would also like it to sell 6s items by default.

I tried to a couple things that didn't work, but I can't even validate this one:

item.IsGem (sell)

I get the long error log for:
[Application_DispatcherUnhandledException] Unhandled exceptionSystem.InvalidOperationException: Sequence contains no matching element

If you could help me out with the filters, that would be amazing. But if you could help me start from making a custom sell gems rule, that would be great. Thanks!
 
Hey toNyx! Thanks for all of the effort put into this. This plugin has worked phenomenally.

I'm running 1.0.1.0, and it tells me that that the current bot does not support using the item filter editor. I really don't mind, because the plugin takes care of almost everything I need. But it still stashes non quality gems, and utility flasks, which I don't want it to do. I would also like it to sell 6s items by default.

I tried to a couple things that didn't work, but I can't even validate this one:

item.IsGem (sell)

I get the long error log for:


If you could help me out with the filters, that would be amazing. But if you could help me start from making a custom sell gems rule, that would be great. Thanks!

Yep, validation is broken, fixed it yesterday ;) now working again

The error you get when clicking on the default EB's GUI is normal, I replace the default evaluator by the one in AIF. so it becomes sort of un-reachable. It's still here tho, but you can't access GUI. The only way to access it is at the first time your launch the bot. don't start it, and click on it, it'll appear ;)
 
Yep, validation is broken, fixed it yesterday ;) now working again

The error you get when clicking on the default EB's GUI is normal, I replace the default evaluator by the one in AIF. so it becomes sort of un-reachable. It's still here tho, but you can't access GUI. The only way to access it is at the first time your launch the bot. don't start it, and click on it, it'll appear ;)

I messed around with this some more, I got the new version 1.0.1.1. I tried a few combinations, but now when I validate, item.IsGem returned true for all types of items.

I also closed the bot to access item filters and it's ignoring my pickup filter and sell filters I made in there. I saw that you planned to phase out item filter usage entirely, but Custom Rules should be fine if I can get them to work.

Assuming I got it to work, it would return False if an item didn't match my rule, right? I tried to setup " item.IsGem and item.Quality <= 5 ", but it returned true for gems of higher quality, and a random amulet I validated too. All returned true for the filters I attempted to make. Any ideas?


E: Also, despite it returning true, I still ran it to test, and it still stashes everything.
 
Last edited:
I messed around with this some more, I got the new version 1.0.1.1. I tried a few combinations, but now when I validate, item.IsGem returned true for all types of items.

I also closed the bot to access item filters and it's ignoring my pickup filter and sell filters I made in there. I saw that you planned to phase out item filter usage entirely, but Custom Rules should be fine if I can get them to work.

Assuming I got it to work, it would return False if an item didn't match my rule, right? I tried to setup " item.IsGem and item.Quality <= 5 ", but it returned true for gems of higher quality, and a random amulet I validated too. All returned true for the filters I attempted to make. Any ideas?


E: Also, despite it returning true, I still ran it to test, and it still stashes everything.

The current version isn't as stable as the upcoming one, heres' a sample of how it's handled (ID this one) :

Code:
                // Python parsing
                if (Main.AdvSettings.EnableCustomRules)
                {
                    var pickupRules = Main.CustomRulesManager.Rules.Where(r => r.Enabled && r.Type == Enums.RuleType.Pickup);

                    foreach (var customRule in pickupRules)
                    {
                        if (PythonParser.EvaluateCondition(item, customRule.Rule, customRule.Type))
                        {
                            Main.Log.DebugFormat("[CustomRules][Pickup] {0} returned true for {1}", customRule.Rule, item.FullName);
                            return true;
                        }
                    }

                    return false;
                }

if a rule returns true, then it's fine, log a little thing in EB, and process. Else, it returns false, that means it won't pickup it.

[Pickup] Rule item.IsGem and item.Quality > 0 returned True for Item Rarity

This in the text file means he picked up a gem (Item Rarity) with quality > 0. so it has been handled correctly.

If the CustomRules are unchecked, and item is not handled by AIF or any other options, it goes through :

Code:
return _staticItemEval.Match(item, type, out filter);

Which is the StaticItemFilterEvaluator, so your rules are used.

Atm the only issue in the new build, is that it's sometimes ignoring sliders values for Maximum items to keep (recipes) and it's fucking up everything so we need to figure it out.
 
Does the plugin just assume you ahve a full set when you have amu + belt + 2 rings? I don't have a set, but have all those (some weird bug, another half-set got sold for no reason). The bot with plugin enabled just goes into infinite loop of trying to sell a set. Which he doesn't have, so he doesn't do anything except for running to and from vendors and looting/stashing belt, amy + rings. With plugin disabled - no problem.
 
Chaos recipe is a bit bugged. Grind in A2, get a complete set for chaos, withdrawing works but then gets into eternal loop while searching for Clarissa (who is in A3)

[WaitForNpcDialogPanel] Timeout.
[OpenNpcSellPanel] Clarissa was interacted, but dialog window is not open.
[RecipeSellTask] Sell panel isn't opened, can't process recipe.
 
Status
Not open for further replies.
Back
Top