Thanks for the quick reply Ben, what do you recommend ? flame totem or incinerate ? and does this support dual totems ?
Either can be used though it was made originally for flame totem. It can go up to three totems and work fine. See page 2.
Version 1.1 is now released. Please see the opening post for a link to the release page, which contains the release notes and a download link.
Been running without any major errors and bugs in Ledge, Catacombs, Fellshrine and Docks for a while now - except for one thing. Getting the occasional "Input Error "skill (coordinates). OutsideClientSpace" errors when moving downwards/south. The bot stops just outside of range of the enemies and takes damage until the chicken script is triggered. Not sure if it's due to the distance settings of the totem, the actual bot logic or my screen resolution settings. Any thoughts? I adjusted the heath pot trigger to 90% health instead of 70% in my copy, just to better suit hardcore. Aside from that I'm really liking 1.1. Looking forward to curse support (and possibly other auras and arctic armor?). Thanks for the good work.
OutsideClientSpace issues are a result of the way our code currenttly works. It's being worked on and changed up, but the short term solution is to lower your combat distance so the mobs on your screen will never be below the options button. Basically, we eliminate actions that would not be within the current screen's resolution + a padded area marked by the options button. This helps solve issues where targeting below your character would be interfered by the HUD. Typically, the issue shouldn't be a problem because you'd be able to handle the error through the spell casting api, but the way that is currently setup with BTs poses some problems. You need to handle the result of Spell.Cast and if it's OutsideClientSpace, either temporarily blacklist the mob or make the character move closer until it's targetable. Some of the new changed input code will make use of coroutines to handle this, as it's a somewhat interesting problem to solve.
I pulled over the curse logic from the Exile CR - it is available for you to check out in the dev branch. My testing of it was pretty.......intense. I tossed a curse on my bar and set the bot off on it's merry way. I had to step away for a moment, and when I came back the bot was in a high level zone in a room with TWO yellow strongboxes. It opened them both at the same time; I just about crapped my pants. Still, the bot actually held up well and lived. It threw out some cold snaps, frost walls, and curses. I was pretty pleased and got a good laugh too. Anyways, please test out the curses. My concern is that with a low mana pool the curse will delay the first totem too much, but maybe that isn't warranted. Let me know how it works out for you. Edit: I watched a couple piety runs and everything went very smooth.
I actually died and had to reroll. Not the bots fault, the AvoidBaddies script in my head malfunctioned when I was playing myself. Working on levelling up again. Shouldn't be long. I did some testing in standard though and I'm having more problems with the OutsideClientSpace-errors with the cursing so I'm going to have to figure out how to get rid of those before I can give any proper feedback. As the bot tries to curse the enemies as soon as they're within range before combat I'm getting that error every encounter unless the enemy is fast enough to run within a clickable range. Leapers etc. From what I've seen in those cases the cursing works well, however. This problem is more apparent with the cursing than the general combat. Yeah, this must be it since it seems to be indifferent of what resolution I run. I've tried everything from 800x640 to 2560x1600. The only combat range that made this error show up less frequently was below 30 and that causes the bot to do weird things, such as run straight past enemies even on a linear area such as Ledge.
I am seeing an issue with the bot not initiating combat until it has already run into a pack of mobs and dies. It happens pretty consistently so I plan on doing some testing. The exception I keep seeing actually points toward GrindBot's exploration code. I've also started seeing he bot die while trying to open a door that is too far away. I'll be posting a log to he support as soon as I can. As pushedx said, we should be able to work around the client space issues in the CR. I just need to get some time to take a look. If anyone is able to solve this before I can get to it, please send me a patch (or I can give you access to create feature branches and pull requests in the repo). Ben Edit: here is the support thread I opened regarding the bot running into a pack without triggering the CR: http://www.thebuddyforum.com/showthread.php?t=153766
Version 1.2 is released: - Pulled Granite/Jade flask support over from the Exile CR. - Pulled curse logic over from the Exile CR.
Hello benkoren, I've been using this CR for searing bond it is amazing but I notice that there are some problems. 1. if the mobs are casters, bot won't place the totem into the mobs, instead he is waiting for mobs to kill the totem and then place a new totem into them. This is kind of wasting time. 2. Sometimes bot will not place the second totem, he is waiting for the first totem to be killed. 3. I keep getting an error, bot is standing, neither moving nor attacking. The error message from ExileBuddy is "Input error casting Searing Bond at {804, 1381}. OutsideClientSpace". If you can figure out a way to fix this, I would be very thankful.
besides, I also get error messages like, Input error casting Searing Bond at {763, 774}. MouseNotInRange Input error casting Searing Bond at {1261, 799}. NotOnTerrainFrame
What do you guys find is the best for this ? Incinerate or Flame ? I'm running Incinerate but I feel like the damage is pretty low
I used it with searing bond, and although it did okay, the clearspeed was kinda low. If you really want you can use it ofcourse (I used it only from 51->55)
Just tried to run this after #796 beta and it's referencing things that aren't there anymore. I hope this is still an active routine as I'd love to play with it some more.
here is my fixed version , i will probably improve this routine logic. Btw which zone are you farming with this routine ? i tend to die a lot maybe my temp is too low stuff which build are you using ? https://www.dropbox.com/s/w5464o890vbrdmv/BenTotem.rar you can try this version where improved trap logic working far better for me. https://www.dropbox.com/s/pj7if2fwtxlrpl9/BenTotemBetterTrap.rar
Be sure to use a CWDT combo such as CWDT+immortal call+molten shell+enduring cry. Make sure molten shell goes off before cast when damage taken and meets the CWDT's level requirment. edit: For some reason the bot stopped casting frost wall even though I did not edit the .cs or changed skills on my bar. I have plenty of mana as well.
Thanks for the routine, its working good for me so far, but i was wondering if its hard to implement the ability to summon zombies? I'd try it myself but i have no clue if i would mess up the totem AI since its more important to keep them up
