Search results

feel free to do so ... ... it cleared grift 72 sofar ... Key element ... wait on CoE 1 or 2 cycles ... on higher rift 70+ ... better with waiting for 2 cycles ... provoke can stay on 1 ... public static Element[] CrusaderCoERotation = { Element.Physical, Element.Fire...

... I made some changes for the invoker punish build ... cleared 70 rift ... ... it will be active as long as you wear the full bonus invoker set and are using punish ... changes: - added waiting on CoE Physical, max 2 elemental cycles (will wait when on light and holy) - iron skin...

I implemented the CoE for Invoker ... using a maxWaitCylce function which allows to wait only for x cycles on CoE ... public static bool ShouldWaitForConventionElementMaxWaitSec(Element element, int maxWaitCycle) { if...

.... added new stuff to item viewer ...

you might start to use some sort of macro ... might be easier ... @TRIFE := ([AS%] * [CRIT%] * [CRITDMG%]) > 0 and use them like this ... [QUALITY] == "Rare" && [TYPE] == "Gloves" # [@TRIFE] also there are new ... stats .... that I implemented in itemrules2 in the up coming release...

nope, skills haven't been added to ItemRules interpreter so far and aren't supported by the DB API, I'm asking for it since around 1 Year, but with out success .... cooldown reduction and ressource reduction will be in in a later DB release ... I will add them to the Item Rules ...

probably its [D3QUALITY] what you mean Magic2 / Rare4 / Rare5 / Rare6. [QUALITY] is only Magic, Rare, Normal ... and so on ... [ROLL] is 2 4 5 6 ... it's all written in the ItemRules.txt I did my documentation task ^^ //...

I trying to do that ... but need some stuff implemented into the API .... working on it. :-)

... back to botting d3 ... now with 7 accounts ... preparing for the exp. :-)

... it seems like D3Starter ... is the cause for bans ...

TrinityMonitor (beta) is available now in Donators repo ... also the itemrules opt .... latest trinity to support trinitymonitor

im updating it today ... for the new monitor release ...

[QUALITY] == "Rare" && [LEVEL] > 58 && [BASETYPE] == "Weapon"

if u wanna be sure to really get all the stuff u want to have unidentified ... u need to do it like i did for my private rule sets .... this will also work with out the item ids ... indentify.dis // +---------------------------------------------------------------------------+ //...

trash will not happen ... if it fails it just identifys it .. ^^ u will need to activate item ids ... for names to work ....as they are already given in unidentifed state ..

yep ... shouldwork but not with names ... with item ids ^^ :-)

pickup.dis // +---------------------------------------------------------------------------+ // | ______ _______ ______ __ __ _______ ______ // | | __ \_ _| | |/ | | | | __ \ // | | __/_| |_| ---| < | | | __/ // | |___|...

on the donator repository ...

which rule ?

just be sure to have no generic weapon pickup earlier to this line [QUALITY] == "Rare" && [TYPE] == "Wand" -> [IGNORE]