This may have started out as an Alkaizer run, but has turned in to something more over time. The name of the game is still efficiency, mainly trying to not use TP unless we absolutely have to.
Required Plugins
Trinity 1.7.2.4 (or newer)
Required Quest
7.3 Kill Azmodan
The profile requires that you be able to hit resume and enter a game at the required quest.
If you're not on the right quest when D3 starts, simply switch to 7.3 and hit "Start Game".
You can then start to run the profile from inside that game or you can exit the game and you'll be able to resume from the correct quest.
What it Does
Other Recommendations
Run at mp0 or mp1. The faster you kill the more XP per hour and the more loot that gets dropped so accordingly, GPH goes up too.
If you can run about the same speed at mp1 as you do at mp0, all the better for mf. I wouldn't go much higher than that myself, both for speed and for the other big rule of thumb which is no deaths.
Deaths are an efficiency killer (pun sort of intended) so trying to run those higher mp levels may actually be hurting your overall productivity
Changelog
Code:
v0.8 Smart Dungeons
[INDENT]Random dungeons now use the TrinityExplore function to find exits quickly
More death handling checks
Removed Stonefort in favor of running Skycrown backwards to Town
Removed Arreat Crater Level 1 due to low mob density
Added nitrous oxide boosters and special sauce to increase run efficiency[/INDENT]
v0.7 New Areas
[INDENT]Added Skycrown and Stonefort after AC2
Kind of boring update, but should help lengthen run
Older versions no longer linked in thread but always available in git repository[/INDENT]
v0.6 I'm Back Baby
[INDENT]Trinity is now REQUIRED
Replaced many MoveTo elements with TrinityMoveTo for efficiency
Added unsafeRandomDistance to most TrinityMoveTo elements to help wiht randomization
Improved error and death handling
Anyone read these changelogs?
Reversed Keeps exploring order to make it more solid and reliable
Added a pinch of magic
Included RelogLoader to help reloggers now that TrinityMoveTo is used[/INDENT]
v0.5 TPs are bad mmkay
[INDENT]Run is now Core > Crater 1 > Tower 1 > Keeps 2 + 3 > Rakki > FoS > Crater 2
Thank you Magi!
No TPs welcome here[/INDENT]
v0.4 Streamline
[INDENT]Added some coordinate points back to Core and Tower to remove nav server hits (less dependency = a good thing)
Improved code to find Exits/WPs in random areas (Keeps, Crater)
Tweaked ExploreArea tags more for random areas to improve reliability
Better Death handling, now attempts to resume if profile gets reloaded on death due to a plugin
Extra dash of awesome[/INDENT]
v0.3 Overhaul
[INDENT]Run now does Core > Tower > Keeps 2 > Keeps 3 > Crater 2
Removed extraneous coordinates from Core and Tower sections
Ensure clearing around Crater 2 Exit
More tweaking to ExplorArea tags
Now leaves game if you have a plugin that reloads profile on death
Probably other things I forgot[/INDENT]
v0.2 Random Area Improvements
[INDENT]Tweaked the ExplareArea tags on Crater and Keeps to make the be cleared more evenly
Added a little logic to get Keeps to stop exploring once The Breach is found
Some code maintenence, questIds, stepIds, etc.[/INDENT]
v0.1 Initial Release
[INDENT]Yup, first version[/INDENT]
Proposed Changes
Here are some things I'm planning on doing for v0.9, make your voice heard:
Randomize the middle
I'll be [attempting to] randomize the middle of the run. The start will still be Core and Tower to gather NV, but from there will, in random order, Keeps 2+3, Rakki+FoS, Crater 2. Finally the run will still finish with Skycrown run to Town for a quick game exit.
Random Crater 1
I'm considering adding a random chance to run Crater 1 after Tower of the Damned. The idea would be to run around Tower and then, if the random chance hits, we'll run up the stairs (instead of to WP) and run Crater 1 backwards. Then use the Crater 1 WP to continue the run.
Vote on the random chance here:
Straw Poll
Previous releases will always be available in the master branch
Feel free to try versions in the development branch but be warned they are unproven and very likely to have bugs (big nasty ones with hair on their legs and venom dripping from their mandibles)
Reloggers
I've now included TinnkaizerRelogLoader.xml for those who use a relogger such as YAR, ARelog, etc.
This file is used when getting the "Failed to load profile: Element TrinityMoveTo is not supported" error.
It happens because the profile gets loaded before the plugins when using a relogger. Since TrinityMoveTo is given by the Trinity plugin, this causes a problem.
The TinnkaizerRelogLoader.xml linked below will always be kept up to date with the latest version and won't be needed on versions before 0.6.
