Search results

Well something like this might work: A : is spirit < 75 before we use dash? use dash B : are charges at max 300ms (or some other number) after use? if A && B then some kind of casting buff has to be active.

I was looking for a way to find out if the In-Geom buff was active but I could not find it. I've commented out some code in PlayerMover.cs, you can find it if you search for "geom". It will make the bot use all charges now and then but if you are using In-Geom I think it is worth it. Give it a...

Haha, it seems wherever I am I came through the back door ignoring all the signs at the front... :cool: I will do some reading, then next update will be as you command!

Ok these should work with the latest from Git. Get that and replace these files. Help me test it, just started myself so no guarantees! @rrrix : It will still use the last charge but it seems less so. The "Dashing to" logger is a bit cryptic now after you used GetTargetName(). Not sure if it...

The bot using up the charges is because of a "bug" in PlayerMover.cs from when I was testing In-Geom. I'll post a new file as soon as I can merge rrrix changes that seem to fix the issue with charges in general. Should be good :cool:

I'm sorry to ask such basic questions but I can see you added some new code which I want to merge with mine. However it's not in the SVN it seems. I don't even know what the difference is in practice (Git vs SVN). I've learned how to effectively diff and merge via SVN but if it's not in the SVN...

Exactly!! rrrix, have a look please :o

I'm at ~17LPH now, been doing runs since yesterday (18 hours ago) which started with 50 rift keys - then 50 trials - now doing tier 40+ grifts. (Limited the trials to get more out of my rift keys, started around tier 30ish). My settings are kinda standard, low trash count and 20 trash radius...

You guys should try my HandleTarget.cs btw. if not already. It should be dashing more for avoidance and globes. Haven't had the time to observe it much though so feedback would be good. It's from 2.8.1 so if you are using a newer one just search for dashing strike and add the code to yours.

I've been trying to eliminate every possible source of it using up the charges with no luck so I also suspect something like this.

I second this. Especially for gem upgrades, when you are pushing higher grifts than you can handle just to get some more levels on your gems this is bound to happen.

Here are my latest, still 2.8.1 though.

Can you post your trinity combat settings? I can have a look :) I think rrrix fixed that last problem in QuestTools or the newest R-Rift. I'll see if I can find the time to upload my changes as I'm at work atm. Have not yet merged with 2.8.3 but it's working good with 2.8.1.

rrrix gonna give it to ya

Wow that was useful! I should look around for more things like this before I ask twenty questions. :)

Does CacheData.Buffs.HasCastingShrine work? I'm guessing it's for channeling pylon. It would be great to use it in PlayerMover.cs to make the bot use dash for shorter distances while having the effect. Maybe we could detect In-Geom buff as well? Or check if In-Geom is equipped and something like...

@rrrix: would something like this work? Line #314 HandleTarget.cs: // If we're doing avoidance, globes or backtracking, try to use special abilities to move quicker if ((CurrentTarget.Type == GObjectType.Avoidance ||...

Thanks. What is the best way to merge it with my code? I'm not that experienced with assembla/git.

I mean use dashing strike to get wherever he is trying to go and if charges are low attack with generator. I realize that you can never get more charges by having more spirit, but it should be doing something while waiting for charges. Pylons etc. should at least be an easy fix with regards to...

OK so here are my changes to 2.8.1 this far. Should be about the same as earlier. In MonkCombat.cs users without Bastions of Will set (Focus/Restraint) could remove the following from line #173: (or we could implement a check for the set? not sure if it exists, I guess I'm a little trigger...