xenohadden
New Member
- Joined
- Jul 30, 2011
- Messages
- 242
- Reaction score
- 2
Shut the fck up, nobody is asking your opinion you monkey.
someone throw a temp ban on this fool, needs to learn some manners.
Shut the fck up, nobody is asking your opinion you monkey.
remember the plugin will save the profile you used when you pressed START, so if you will press STOP. The plugin will run these profiles until the next will match the profile which got saved when you press start!
So this probably happend because you stopped the bot and then started it middle of the profile order!
Glad to hear that its working out for you!Thanks Radinoc!! My WD is running this 24/7 for the last several days and he hasn't died or gotten himself stuck yet. What I did notice was that once I improved the gear all of the stuck issue went away. I noticed prior to my gear upgrade that my guy would tend to run and avoid allot more maybe moving himself to far from the designated point and then backtracking would get him stuck. I also only use the recommended plugins the only one I don't use is the combat plugin. I just use Belgfor and I modified to suit me WD build.
Not sure if this would resolve everyone issue with getting stuck, but I haven't yet experienced it.
Does the author include in the next version?
- more accurate killing mobs
It is the ideal solution after the 1.0.4 and paragon levels
Its set to 2 because if you got lower the plugin will bug out!Hi again,
some updates regarding my experience with this profile:
I found out that the issue that me and other people were experiencing related with the profile not creating new games was, fundamentally, due to just deep stupidity: When Stopping the profile and then Starting it again DB will load the 'last' profile which, given the fact that this profile is composed by a bunch of different files, will be one of the different profiles for the static areas of A1 (Antidote_FieldsOfMiseryA.xml, for instance). Yeah, I apologize for that one... super shame on me.
Besides that, based on what I've just read a few pages before that, someone also found out that the profile's productivity sky rockets if you set the RadsProfileManager to switch the profile every SINGLE death, not every two as it is by default.
Fact is that you'll probably notice that the Slider at RadsProfileManager plugin's UI has a min value of 2 deaths. Open the file "RadsProfileManager.xaml", find the line:
<Slider Name="slideNP" Height="24" HorizontalAlignment="Left" .... Minimum="2" IsSnapToTickEnabled="True" Maximum="10" />
... And set that "2" to "1". Then, you'll be able to change the min death value to 1 @ the RadsProfileManager GUI.
Nopp, too much letters xP And you can just look at the gits if you want to know@Radonic can you add your developed things to your signature with date updated and version numbers
so we can track
ty
thank you, i cant see which WP it trys to reach though :S
I guess its the B profile also?
And does it happend also, or was this a one time thing?
Well we name all the waypoints so you easy can debug themWhat would I need to screenshot to show the attempted WP? I thought the bottom line on the DB window displayed that.
Didn't check for A or B profile, will check if it happens again and I catch it.
I've seen it quite a few times now.
Thanks