Search results

My body can't handle the hype :D

Not picking up scrolls at all may be a problem, if at some point you will run out of them and bot can't ID rares and TP. The best solution would be to limit the amount of scrolls in the stash by some small amount (like 2-3 stacks) and only start picking them up when all depleted. But that...

Thanks for the golem code, I used it too, also I suggest that people who selfcast golem make a stopwatch for it with 5-10ish seconds cooldown to avoid getting raped while trying to recast golem in a bad situation. The code for stopwatch can be taken from the moltenshell section of the default...

Ok, so I've figured out why exactly the routine doesn't like to cast all 3 of my aura+2heralds (all the time it only casts 2 of those and refuses to cast the 3rd) After setting the "Debug auras" checkbox, this line started appearing and it explains stuff: [CanCast] We cannot cast [AuraName]...

Are you sure you have the checkbox enabled? :D

I feel kinda dumb, but can you explain to me for what reasons it works like this then? -_- Why not have IsRGB recognize for pickup and sell 3Link 5socket items or 4 link for socket items which are eligible to get sold for a chromatic? -_- It's not that it breaks stuff, but the bot leaving them...

Shouldn't it be <= 5 and <=4 ? -_- Or am I misunderstanding the purpose of that stat? Am I supposed to use Item.IsChromatic instead (will it even work in custom rules?) "- IsRGB : used for items worth a chromatic orb" - 4 link RGB + random is also worth chromatic (and not much else, shouldn't...

Hey, I think the code for "IsRGB" is kinda not working properly. I've seen the bots miss (not pickup) an RGB item twice (both times the item had more than 3 sockets and more than 3 links). Are you sure that 4 link with 3 of them being RGB and one random is processed correctly under that rule? It...

[WithdrawItemsCoroutine] The current tab should not be withdrawn from. Skipping it. [WithdrawItemsCoroutine] NextTab failed. [RecipeWithdrawTask] Seems like we had a problem withdrawing (Boots : True) [WithdrawItemsCoroutine] The current tab should not be withdrawn from. Skipping it...

How to evade this error crashing my bot? Recently it's almost a garanteed chance that I return to a crashed bot with invalid session in logs... (3 times in 2 days) If it'd at least pause bot and reconnect session later, but it just closes the bot and idles. That's really not that cool -_-

Damn that's baws :D

That I don't know. I think maps are considered the proper endgame farming, not piety, but I've never actually put it to a serious number test.

Mapping for a continuos period of time cannot possibly be a red flag, since that's what most people do anyway. Actually, I would even say that switching maps > dominus > piety > maps I would consider a much more *strange* behaviour than just map farming (or farming one of those bosses)

Well, it doesn't take a detective to ***** this mistery though -_-

the 6socket one? "item.Sockets == 6" I mean, it doesn't get easier than that -_- Encountered a bug today where the bot stashed a ring for chaos recipe in the tab which he was supposed to ingnore and then went into an endless loop of trying to loot that last ring while ignoring the tab. Had to...

Also is there a syntax for comments in the custom rules json? I like to modify them by hand rather than by GUI so I would like to leave comments for todo stuff and questionable filters to check out later.

how do I check if an item is a fishing rod within custom rules? =)

Consider the directory structure. It needs to go something like: "EB\Plugins\AutoFlask\Autoflask.cs" not "EB\Plugins\Autoflask 2.0\AutoFlask\Autoflask.cs" and like that for other plugins

the same exact thing happened to me again (except there was no desecrated ground). Also I think it was the same type of map (Graveyard or maybe Cemetery, I only noticed the tileset, not the name of map). Maybe that's the problem one, I'll blacklist it for now.

Came back to a bot dead in the desecrated ground trying to open a chest with logs [LootItemTask] The current item to loot is [12159] Maelström Staff at {xx, yy}. We have been on this task for 00:00:01.2576838 and have been attempting to interact for 00:00:00.9519662. [RemoveItemLocation] The...