[A3] - Skycrown Battlements - Massacre - XPgrind 10min runtime [Act 3 - Skycrown Battlements - Massacre - (XP Grinder)] v1.1 (twisted Firestarter) This is my first profile, it stats at the beginning of Act 3, runs through the whole level and lights 5 beacons. In testing on a lvl 45 Monk with reasonable gear, hitting ~1kdps I was getting approx 1m XP/hour in NM and a whole run takes around 10 mins. The idea is to run the whole first quest from act 3 and to get as much bonus XP as possible from "Massacre" as possible. It's intended as a leveling profile that won't hit game limits (unless you die a lot!) In testing on level 55 Monk with 7k dps it clocks ~3m XP/hour in Hell. Known issues: It'll get stuck if you have it set to chase Treasure Goblins and it chases so far it gets 'lost' Tested with DB .204 Giles MonsterPriority 1.5.5, GilesWorldObjectHandler 1.5.2, XP Counter 1.1. Set trigger range in Monster Priority to 30, and set to ignore treasure goblins. I use the defaults for object handler with gold pile set to 100. You need the 2nd quest of Act3, bot will take things from there. (3.1.2 Lighting the Beacons) Set Death Handling to Logout Credit to tozededao's original skycrown short profile that I expanded. Code: Version History: v0.1b - Initial version, Nightmare only v0.2 - Toggles combat=false for beacon lights to light the fires more reliably, some pathing improvements, NM and Hell versions released v1.1 - Pathing improvements, and beacon lighting fixed.
A tip is to make the bot have combat=False when you use an object! You can have this under a split second. But its still importent because that will help it to ALWAYS click it the same way, which will make it failsafe. Ive had to do this in my profile A1 when then bot is about to go down to rest or crypts in festering woods. Hope it helps you
Thanks for the tip, now incorporated, need to improve the pathing slightly so it lights up every run.
Tested your nm run, So far it's done a damn well job. Hasn't been stuck once. There are a few points where the bot just stay put for a good 4-5 second, usually when it gets close to lighting a beacon. As well as the path of the bot gets really close to certain corners where it could can cause an issue.
Thanks. It has a habit of pausing sometimes when one of those bird things swoops in to grab a soldier, bot wants to attack it but can't and it stands there for a few secs until it notices there is nothing to attack and then carries on. I've had 1.1 running for 4 hours or so now and not had any stucks.
I ran the nm for 3 hours today, didn't get stuck once, and it hit every single signal beacon during that time. I also ran hell for 2.5 hours and it is just as good as the nightmare one, only problem what hitting the light beacon twice out of the 25 runs.
Actually, been running a few times without stuck, its situational, probably only with ranged classes, and most likely the fault of the combat profile not recognizing the target is not getting hit, not even sure how you would fix. But for melee classes I'm sure this wouldn't happen. Good profile, thanks! EDIT: Also... would be super sweet if we just added FOS to this, do FOS then battlements, IDK, Im just looking for exp profiles that aren't too involved, used to just ZK til 60 in a2 norm, lol.
If you are using GilesMonsterPriorityChanger you can set the trigger range lower, which will probably mostly fix it. You can use DB scheduler (click the downarrow in the DB window to the right of the 'Load' box that you click to load profiles to get to it) to run a FoS profile then this one for the moment. I'd like to get the whole of act 3 profiled eventually so FoS is on the to do list...
Getting stuck at the fireplace on the middle-left of the map. Wasn't using monster priority plugin and will install now and use the settings as stated in the first post to see if it fixes it. If not does anyone have an idea? It sort of sticks to the fireplace like a magnet and even if monsters come it won't attack them. *edit* The profile is fine. The problem is that there is a DB bug which starts the next quest before restarting the game hence it restarts into the next quest. Happens with ZK and Queen too.
It used to do that in an early version where it was trying to interact with something that was no longer there (trying to light a beacon twice) it shouldn't do that in the later version at all. It walks up to a beacon, clears any mobs in combat radius, then walks to a lighting point, turns off combat lights up and turns combat back on again (if you leave combat=true then it sometimes won't interact with the beacons) then continues on to the next area. I'm going to redo this profile as a GF optimised version as well as this XP version, and will release it sometime "soon" (hopefully in the next couple of weeks) along with a Rakkis crossing, and my own version of Core all aimed at Gold farming in lower levels or champ farming in inferno. Work is looking really busy though for me atm, so don't hold your breath or anything
Using the Hell profile, when my char dies it teleports to town and tries to walk to an unreachable place and walks towards wall.
set death handling to logout. It's trying to walk to a waypoint it can't get to cos it's in the wrong part of the map. If you set it to logout on death then it resets and starts over if it dies. If you die a lot you might want to up the idle time between attempts so you don't hit game limits. I'd probably run NM till about 45, then buyout a few pieces of reduced lvl req gear and a reduced level weapon to equip then switch to Hell and you should rarely if ever die.
Great Profile!!!!! Been using it for 2 weeks, could you extend it to include Turning the Tide to get more use out of the stacks? I dont know anything about making a profile or I would try.
Works Fine but sometimes it just doesn't kill that big ugly thing spitting soldiers that we find at each beacon Still it's a nice profile .. Ty keep it up
