Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
using System;
using System.Collections.Generic;
using System.Windows.Controls;
using log4net;
using Loki.Bot;
using Loki.Bot.Logic.Bots.BasicGrindBot;
using Loki.Bot.v3;
using Loki.Game;
using Loki.Utilities;
namespace ItemFilterExample
{
public class ItemFilterExample : IPlugin
{
private static readonly ILog Log = Logger.GetLoggerInstanceForType();
private bool _enabled;
// We want to loot 2 Royal Skeans before disabling the filter.
private int _royalSkeanCount = 2;
#region Implementation of IPlugin
/// <summary> The name of the plugin. </summary>
public string Name
{
get { return "ItemFilterExample"; }
}
/// <summary> The description of the plugin. </summary>
public string Description
{
get { return "A plugin that shows some example logic for changing item filters at runtime."; }
}
/// <summary>The author of the plugin.</summary>
public string Author
{
get { return "Bossland GmbH"; }
}
/// <summary>The version of the plugin.</summary>
public Version Version
{
get { return new Version(0, 0, 1, 1); }
}
/// <summary>Initializes this plugin.</summary>
public void Initialize()
{
Log.DebugFormat("[ItemFilterExample] Initialize");
}
/// <summary> The plugin start callback. Do any initialization here. </summary>
public void Start()
{
Log.DebugFormat("[ItemFilterExample] Start");
BasicGrindBot.OnLoot += BgbOnOnLoot;
}
/// <summary> The plugin tick callback. Do any update logic here. </summary>
public void Tick()
{
}
/// <summary> The plugin stop callback. Do any pre-dispose cleanup here. </summary>
public void Stop()
{
Log.DebugFormat("[ItemFilterExample] Stop");
BasicGrindBot.OnLoot -= BgbOnOnLoot;
}
public JsonSettings Settings
{
get { return null; }
}
/// <summary> The plugin's settings control. This will be added to the Exilebuddy Settings tab.</summary>
public UserControl Control
{
get { return null; }
}
/// <summary>Is this plugin currently enabled?</summary>
public bool IsEnabled
{
get { return _enabled; }
}
/// <summary> The plugin is being enabled.</summary>
public void Enable()
{
Log.DebugFormat("[ItemFilterExample] Enable");
_enabled = true;
}
/// <summary> The plugin is being disabled.</summary>
public void Disable()
{
Log.DebugFormat("[ItemFilterExample] Disable");
_enabled = false;
}
#endregion
#region Implementation of IDisposable
/// <summary> </summary>
public void Dispose()
{
}
#endregion
#region Override of Object
/// <summary>
///
/// </summary>
/// <returns></returns>
public override string ToString()
{
return Name + ": " + Description;
}
#endregion
private void BgbOnOnLoot(object sender, BasicGrindBot.OnLootEventArgs onLootEventArgs)
{
if (onLootEventArgs.Name == "Royal Skean" && _royalSkeanCount > 0)
{
_royalSkeanCount--;
Log.InfoFormat("[ItemFilterExample] We are about to loot a Royal Skean. We now need {0} more.",
_royalSkeanCount);
if (_royalSkeanCount <= 0)
{
// Only do this logic if the current item evaluator is DefaultItemEvaluator.
var itemEvaluator = ItemEvaluator.GetItemEvaluator() as DefaultItemEvaluator;
if (itemEvaluator == null)
{
return;
}
// Loop though the looting filter categories.
foreach (var category in itemEvaluator.ItemEvaluator.Categories)
{
// Only care about Pickup filters.
if (category.Type != ItemEvaluator.EvaluationType.PickUp)
continue;
// Loop though all current filters.
foreach (var filter in category.Filters)
{
// Only match our own filters. Please don't go around changing the user's other filters.
if (filter.Description == "ItemFilterExample-RoyalSkean")
{
Log.InfoFormat("[ItemFilterExample] Now disabling the {0} filter.", filter.Description);
// Disable the filter so no more items are looted.
filter.Enabled = false;
// This is specific to BasicGrindBot. We want to remove any items pending for looting, to avoid looting more items than we need.
// BGB caches items as they appear and evaluates them for looting once, to avoid performance issues and constant item evaluation.
var toRemove = new List<AreaStateCache.Location>();
foreach (var location in AreaStateCache.Current.ItemLocations)
{
// We want to avoid removing the location of the item we're about to loot, so this should roughly do it.
// It's not pefect, but it shouldn't matter much really. If tons of the item you want to loot at the same time drop,
// you'd just have extras.
if (location.Name == "Royal Skean" &&
LokiPoe.Me.Position.Distance(location.Position) > 50)
{
Log.InfoFormat(
"[ItemFilterExample] We will remove the location {0} at {1} to avoid excess looting of the item.",
location.Name, location.Position);
toRemove.Add(location);
}
}
foreach (var location in toRemove)
{
AreaStateCache.Current.RemoveItemLocation(location);
}
// TODO: This is not 100% correct, since the item filter supports custom paths. However, that's not used by the bot,
// and the current implementation doesn't save the path interanlly. This will be changed later.
itemEvaluator.ItemEvaluator.Save(ItemEvaluator.DefaultPath);
}
}
}
}
}
}
}
}
) the Stashsearch stuff from exVaults MapRunner.@ pushedx - You'd actually don't even have to with draw the chances. I only pickup like 5 Sort of Items and only those with 3L or more so my stash doesn't get filled up too quickly.
Now the thing actually missing is the "GoToYouStash.ChanceItemX1->ChanceItemX2->ChanceItemX3."-task and so on. Because we could ... borrow / partially (
lol
Well from trying it last night. The approach I would do is.I'm an idea guy but not able to code myself :x
Doin the same shit for work
That's not true, ExVault, Naut, and some others dev. Some are better then me and do not publish, but keep it private, this is understandable.
blasphemy and lies, this bot is all kinds of amazing ^_^
Due to popular demand, I put something basic together
no doubt darkblue's will be far more elegant when it's ready
IMPORTANT NOTE: this is barely tested, it was made quickly over a remote connection while at work. shh
How to use:
place the file in ExileBuddy\Plugins\ChanceItems\
set your basicgrindbot settings to fill chance orbs
set your loot filter to pick up the white items you want to chance
when in town it will chance specified white items, assuming you have chance orbs in your inventory already. It will not get chance orbs from your stash, or use them directly from your stash
What it does after chancing will depend on your loot filters (if set to vendor magic / rare items, stash rares with specific attributes etc)
You need to specify what items to chance by editing the code, but it's basic and outlined below:
1. open ChanceItems.cs in notepad or similar
2. find line 184. Alternatively, use the notepad search feature, and search for 'FullName'
4. Edit this code, explanation and examples below
//ENTER STUFF TO CHANCE BELOW THIS
(item.FullName == "Gavel") ||
(item.FullName == "Siege Axe") ||
(item.FullName == "Glorious Plate")
//ENTER STUFF TO CHANCE ABOVE THIS
in the included example, it will chance any normal gavel, siege axe or glorious plate
You can add more by copying the format, and including another line, just change the name to what you want to chance. Note: If it is not the bottom item, it should have '||' at the end of the line
example adding 'occultist's vestment':
//ENTER STUFF TO CHANCE BELOW THIS
(item.FullName == "Gavel") ||
(item.FullName == "Siege Axe") ||
(item.FullName == "Glorious Plate") || <-- we added || at the end of this line, which was not there previously. This is because it is no longer the last item
(item.FullName == "Occultist's Vestment") <-- this does not have ||, as it is the last item
//ENTER STUFF TO CHANCE ABOVE THIS
Example removing 'Glorious Plate':
//ENTER STUFF TO CHANCE BELOW THIS
(item.FullName == "Gavel") ||
(item.FullName == "Siege Axe") <-- we removed the || as 'siege axe' is now the last item
//ENTER STUFF TO CHANCE ABOVE THIS
example of only 'siege axe':
//ENTER STUFF TO CHANCE BELOW THIS
(item.FullName == "Siege Axe") <-- we removed the || as 'siege axe' is the last (and only) item
//ENTER STUFF TO CHANCE ABOVE THIS
5. save the file in notepad
6. start exilebuddy, and hope there's no red text that it failed to compile
Do any developers have suggestions on how I can make this more user friendly?
I could have it chance any normal item without checking the name, but does anything else show up as rarity.Normal, such as quest items? which may cause problems
I could have textboxes in the plugin settings from within the bot, to type the names to check against. But I wouldn't know how to make a variable number of them, and it's unknown how many item types the user may want to chance. Could maybe get around it by making a large amount like 20
Thanks!
View attachment 156931