Any particular reason it keeps killing the act 3 keywarden with less than 5 stacks? edit: turns out it only kills it about 30% of the time, it is trying to run away.
First off, hope the wife is doing good, I get cut on myself on monday, thats never fun. I am having a problem with keywarden 1.8 though, demonbuddy wont recognize the plugin due to an error? I can work my way around code eventually, and tried playing with it, and everytime I fixed one error for it, it came up with another, I'd love to get the new version of keywarden going, because the 3.2 version just needs alot of tlc, got to get the new barb a hellfire lol ><
Same here and the below message appear when using latest Trinity 1.7.2.10; [05:18:12.455 N] Demonbuddy v1.0.1370.304 started [05:18:14.328 N] Logging in... [05:18:15.909 N] Attached to Diablo III with pid: 6200 [05:18:15.919 N] Flashing window [05:18:19.789 D] Executable Path: H:\DemonBuddy\Demonbuddy 1.0.1370.304\Demonbuddy.exe [05:18:19.789 D] OS Architecture: AMD64 [05:18:19.789 D] OS: Windows 7 Service Pack 1 64-bit [05:18:19.789 D] OS Language: English [05:18:19.839 D] Reloading AssemblyLoader<Zeta.CommonBot.ICombat> - Initializing [05:18:23.579 D] Reloading AssemblyLoader<Zeta.Common.Plugins.IPlugin> - Initializing [05:18:25.809 N] Compiler Error: h:\DemonBuddy\Demonbuddy 1.0.1370.304\Plugins\KeyRun\KeyRun.cs(23,7) : error CS0246: The type or namespace name 'GilesTrinity' could not be found (are you missing a using directive or an assembly reference?) If something is wrong?
Trying it out now. So far it's done 2 Act 2 runs with no problems at all . Running your A1-3 version 4.0, KeyRun 1.8, Trinity 1.7.2.11. Thanks! I'll be trying this on other acts later, but act 2 is where I need the most keys
Trinity has a new version: 1.7.2.11. Not sure if that matters, but it's working for me. Also, make sure you're running Keyrun 1.8, and try version 4.0 of this profile.
Why does my bot killed the keywarden in act2 with only 4 stacks of NV? Just started this profile, and ive only seen the act2 so far! Great profile tho!
It does this every so often... the bot wil "try to run away" from the keywarden if it has less than 5 NV but sometimes it can't run away and it ends up killing the KW
Plugin not loading properly. Any idea why? I've never been able to get this to work. Using latest Trinity and cleared compiled assemblies. I noticed when I copied your plugin to my Plugins folder, QuestTools by rrrix disappeared.
I can't seem to get this profile to work take a look at this. [14:56:01.079 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:01.319 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:01.563 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:02.386 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:02.652 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:02.916 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:03.198 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:03.471 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:03.822 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:04.072 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:04.314 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:04.557 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:04.794 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [14:56:05.036 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18
the profile is not working here is what is going on [15:32:39.934 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18 [15:32:40.160 N] Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18
I got the same error... using latest Trinity CE, latest profiles and keyrun plugin (both from Magi?s dropbox): Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" act2profile="act2_start.xml" act3profile="act3_start.xml" />) Line 18
The newest keyrun plugin causes the above errors for me as well. if you downalod 1.7 instead you can load the bot. the bot does not work correctly for me though, it stops when it finds a warden without having 5 stacks which it never has. the order in which it does stuff is really stupid as well.
While that may be the case, keyrun 1.7 causes crashes constantly here (the bot won?t run for more than 20-40 minutes before crashing), while even with those errors version 1.8 still runs without crashes, but doesn?t seem to count keys properly - or at all... Ok something happened, keyrun 1.8 makes it not run AT ALL - it keeps creating games and going back to resume screen, doesn?t do anything anymore. I wonder wth happened...
Are you guys running version 3 or version 4 of this profile? I'm using v4.0 of this profile, trinity 1.7.2.11, KeyRun 1.8, and yesterday I got 11 act 1 keys and 11 act 2 keys on MP5, no errors Look at post #942, and click on Magi's link. https://www.dropbox.com/sh/70pu8ssbwgyxv99/jRgGVnflLu That will give you access to version 4.0 of his profile. The link to KeyRun 1.8 is in his signature.
If anyone could help me I'd really appreciate it, I'll submit a log if I have to but I'm sure plenty of other people have this problem and it seems to be fixed for most of you now. In Act 2 as soon as I enter the Oasis my bot runs down that south path right near the entrance and runs right up to the wooden door and will AFK there until my gold timer trips. Anyone?
Still Failed to load profile: Element KeyRunProfile is not supported. Please check your XML and try again. (<KeyRunProfile questId="1" act1profile="act1_start.xml" Oh, and when I use keyrun 1.8 it doesnt even SHOW on plugins tab alrightty then: I deleted everything, fresh installed latest beta DB, fresh DL?ed trinity routine, fresh DL?ed ONLY necessary plugins - latest trinity and keyrun 1.8, fresh DL?ed ONLY latest profile and... so far so good! no crashes for well over 90 minutes... TYVM If crashes occur, I?ll update info here. Just on a side note (pissed off): I hate weekends... latency was between 100 and 250, now it?s around 700-800ish, and I know it?ll remain that way for most of the weekend
