What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Plugin] Giles Combat Replacer

Giles, can't wait for the rend update tonight, it's godly now.

You're doing great work man and are an extreme asset to this community. PLEASE keep it up!
 
Giles sir, please keep up the great work with ALL of your awsome plugins. As for your lastest update, i was watching my barb to act2 champ runs. It did not seem my barb was casting rend every 5 sec( with fury ) just wondering what ruleset that you used. with a since mob it doesn't cast even vs an elite but it seems 4+ it'll cast normally.
 
Last edited:
so I deleted everything and installed on a thumb drive and there is no problem with attacking. Just wanted to let you know that after troubleshooting more it wasnt an issue with the combat routine.
 
Giles sir, please keep up the great work with ALL of your awsome plugins. As for your lastest update, i was watching my barb to act2 champ runs. It did not seem my barb was casting rend every 5 sec( with fury ) just wondering what ruleset that you used. with a since mob it doesn't cast even vs an elite but it seems 4+ it'll cast normally.
He posted a few minutes ago that Rend is receiving an overhaul tonight.
 
so 30 min in and both d3 and db crashed. Could this be combat routines causing the crashes? (seems to happen with all combat routines) or db issue? I think I remember reading before that sometimes combat routines can cause crashes do to certain ability handling?
 
btw from what I am reading generic routine causes instant crash...When I tested belphegor it crashed in like 5 mins and using giles took about 30 min. Not sure if this means anything.
 
He posted a few minutes ago that Rend is receiving an overhaul tonight.

v0.4.1.2
-- Monks now use serenity at <=40% health OR <= 55% health and incapacitated.
-- Barbarian "rend" now set to use max once every 4.8 seconds for the new "lacerate" rune power. Will use on any elites, or small groups of normals, whenever you have enough fury.
-- No longer ignores minions at 100% health - this was previously to avoid "invulnerable minions" - but these no longer exist since patch 1.04.

he already did. l2 read notes..
 
v0.4.1.2
-- Monks now use serenity at <=40% health OR <= 55% health and incapacitated.
-- Barbarian "rend" now set to use max once every 4.8 seconds for the new "lacerate" rune power. Will use on any elites, or small groups of normals, whenever you have enough fury.
-- No longer ignores minions at 100% health - this was previously to avoid "invulnerable minions" - but these no longer exist since patch 1.04.

he already did. l2 read notes..

he's talking about another update.
 
using the new combat routine n it doesnt seem to prioritize goblins. all 4 of my farmers would chase him n if a mob would come along it would kill it first then go back to gob. also on one occasion it just walked past the gob n attacked other mobs n let it run away.

prioritize checked*
 
The constant D3 crashes seem to be caused by DB, from everything I can see. I have forced diagnostics in log-files back on through a plugin change, and tried DB with and without any plugins - it crashes regardless. And when it crashes Db can be doing anything - from moving around to fighting to trying to loot.

There will be another update to the plugin probably tonight, but given that in my humble opinion DB is currently unusable with patch 1.04 without triggering a lot of Diablo 3 crash logs (which may be something Blizzard can pick up on?), I may wait until a DB update.

Edit: Another DB update out already - will try that and see if the crashing is reduced/gone!
 
Last edited:
The update to DB seems to have done wonders (at least initial observations) to Rend. It is noticably more 'spammy' now.
 
v0.5 uploaded:
-- New feature: Backtracking. Bot now records your movement while chasing monsters in combat, and then backtracks along them after combat ends before handing control back to DB, to get you back to your last waypoint safely.
-- New config added, enabled by default, to disable backtracking (incase you hate it/it causes issues).
-- Out of combat avoidance and globe-fetching now implemented - for 5 seconds after combat ends, will continue to look for AOE's to try and avoid.
-- After engaging in combat, kill radius is kept at routine/profile kill-radius setting for a few seconds to allow exp bonus from repeat kills etc. instead of instantly ignoring anything slightly out of range.
-- Treasure goblins set to prioritize now get chased more reliably over other monsters.
-- Should no longer interrupt town-portal-return with trying to spam sprint/out-of-combat buffs.
-- Some changes to various avoidance AOE radius and avoid-percents to improve behavior overall (eg larger radius on bee sting avoidance, lower-health before dodging plague pools)
-- Barbarian Rend now set to use every 4.7 seconds *OR* in half that time if you have 85% or more of your max fury (to allow faster spam, helps when more monsters move into range etc.)
-- Barbarian Rend priority now set to higher than revenge/overpower/one or two other things.
-- Barbarian Battle Rage now set to a "slow-use" skill (usually used for abilities with a long animation time), to try and help prevent cast-failures.
-- Barbarian ancient spear set to target an area behind the mob to extend the range of it (hit more targets etc.)
-- Monk mantra spam now lower-prioritized, and only if you have 90% of your max spirit (so if your max spirit is at 150, then only with 135+ spirit). Mantra spam is lower priority than all except "normal" attacks, and is to keep the 3-4 second buff up while fighting elites and with plenty of spirit to spare.
-- Monk sweeping wind/blinding flash only used on greys when at 80%+ max spirit and 3+ greys in range.
-- Monk cyclone/seven-sided/exploding palm all tweaked in use-intelligence slightly.
-- A few other changes here and there I can't remember/forgot to log :P

^^ Quite a big update with a couple of major new features :)
 
is there a way to make it so it spams sprint?

EDIT: sorry, first time using it, jumped to conclusion too fast. It does use sprint effectively. It's an excellent routine.
 
Last edited:
Back
Top