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

[Plugin] Profile Switcher - keep your Nephalem Buffs!

now running_log.txt relays:

--------------------------NEW RUN--------------------------
Randomization order for this run:
1: C:\Profiles\A1\Antidote_FieldsofMiseryB.xml
2: C:\Profiles\A1\Antidote_WeepingHollowB.xml
3: C:\Profiles\A1\Antidote_OldTristram.xml
4: C:\Profiles\A1\Antidote_LeoricsHuntingManorB.xml
5: C:\Profiles\A1\Antidote_SouthNorthHighlandsA.xml
6: C:\Profiles\A1\Antidote_FesteringWoodsB.xml

all i have to do is update random.txt each time i run the bot. very happy thank you.

Great to hear that you're happy with our plugin!

The only thing I would do differently is that i would give Antidote_OldTristram.xml a higher priority - there are no elites there - only sarktoth & the other cellars. It's not very profitable if this profile is the first profile after randomization. Thats the reason why we have implemented those priorities :)

Hey thanks for this plugin, I've been using it a lot recently and its been great.

There is one issue which im noticing, I had set the number of retries from 2 to 4, but it doesnt seem to retry it 4x, all the time. It seems to randomly decide to move onto the next profile, between 1-4 deaths. Furthermore, once the death handler fails the first time, it will then not report the correct death amount going forward, like if i died on the 2nd try in one profile, the logs would say:

number of retries #1...
number of retries #2...
number of retries #3...
number of retries #4... Next profile

Then moves onto the next profile without trying 2 more times. (It doesnt say those exact words above ofc but you get the point.)

Changing the number or retries didnt do anything either, i had set it to 8 last night and it still does the samething.

Sorry i cant post any actual logs at the moment, currently at work.

I also experienced this problem - sometimes DB spams OnPlayerDied to often and skips some retries. Doesn't happen very often on my bots, so I see it as a "randomization feature"^^

If it happens to often you can try to raise the time value for ignoring death in the OnPlayerDied method

if (ts.TotalSeconds < 3) <--- this line, raise 3 to maybe 5 or so
 
^ can you tell me which file i need to open to edit that line? i will give that a shot, thanks!

Yea i agree that it is a cool unintentional deathhandler feature, BUT not when the elite pack is 2 hits away from dying and then it just gives up and moves on >.<.
 
Last edited:
^ can you tell me which file i go into to edit that line? i will give that a shot, thanks!

Yea i agree that it is a cool randomizing deathhandler feature, BUT not when the elite pack is 2 hits away from dying and then it just gives up and moves on >.<.

in the ProfileSwitcher.cs :)

That's bad i know!
 
Ok just tested it out and it seems to be working a lot better, still randomly changes on death but less frequently.

I also noticed that on death handling retries, it does not reset the count once a profile has been completed, before moving onto the next. It would instead keep the current count of the death and carry it over into the next profile until the # of retries have been fulfilled.

ie: when i set number of retries on death to 4,

profile 1: dies 1
profile 2: dies 1
profile 3: dies 2x....exits profile and goes onto the next one because it sees 4 deaths total



I thought i was supposed to work like this:

profile 1: dies 1
profile 2: dies 1
profile 3: dies 2x
profile 4: dies 4x...exits profile and goes onto the next one because it sees 4 deaths total

correct me if im wrong.
 
Last edited:
Ok just tested it out and it seems to be working a lot better, still randomly changes on death but less frequently.

I also noticed that on death handling retries, it does not reset the count once a profile has been completed, before moving onto the next. It would instead keep the current count of the death and carry it over into the next profile until the # of retries have been fulfilled.

ie: when i set number of retries on death to 4,

profile 1: dies 1
profile 2: dies 1
profile 3: dies 2x....exits profile and goes onto the next one because it sees 4 deaths total



I thought i was supposed to work like this:

profile 1: dies 1
profile 2: dies 1
profile 3: dies 2x
profile 4: dies 4x...exits profile and goes onto the next one because it sees 4 deaths total

correct me if im wrong.

That's right. It should reset the deathcounter after switching to the next profile. The problem maybe only occurs when the other bug hits you. Will have a look at it!
 
added some random.txt files that it is even more plug and play
 
For anyone who has some patience ive dropped a quick batch file to generate data for random.txt every 2 hours.
Can be adapted to any profile folder & removes the need to play with A/B profiles.
It skips the 'Start Here' file & completes Old Tristram last.
Edit: Should mention this particular script is for Ciggarc A1 Champion Hunting

@ECHO OFF
set /a number=1
ECHO.
ECHO [ +++ RANDOM PROFILE DELAY +++ ]
:LOOP
ECHO.
@echo off
set /a min=1
set /a max=0
set /a myrandom=%random% * 3 %% 2
if %myrandom%==1 (
echo 1 > random.txt
echo 0 >> random.txt
echo Festering Woods A
) else (
echo 0 > random.txt
echo 1 >> random.txt
echo Festering Woods B
)
set /a myrandom=%random% * 3 %% 2
if %myrandom%==1 (
echo 1 >> random.txt
echo 0 >> random.txt
echo Fields Of Misery A
) else (
echo 0 >> random.txt
echo 1 >> random.txt
echo Fields Of Misery B
)
set /a myrandom=%random% * 3 %% 2
if %myrandom%==1 (
echo 1 >> random.txt
echo 0 >> random.txt
echo Leorics Hunting Manor A
) else (
echo 0 >> random.txt
echo 1 >> random.txt
echo Leorics Hunting Manor B
)
echo 2 >> random.txt
echo Old Tristram (Finale)
echo 1 >> random.txt
echo Highlands
echo 0 >> random.txt
echo Start Here (Skipped)
set /a min=1
set /a max=0
set /a myrandom=%random% * 3 %% 2
if %myrandom%==1 (
echo 1 >> random.txt
echo 0 >> random.txt
echo Weeping Hollow A
) else (
echo 0 >> random.txt
echo 1 >> random.txt
echo Weeping Hollow B
)
ECHO.
ECHO Number Of Generations: %number%
set /a number+=1
PING -n 7600 127.0.0.1>nul
GOTO LOOP
 
Last edited:
That's right. It should reset the deathcounter after switching to the next profile. The problem maybe only occurs when the other bug hits you. Will have a look at it!

TYVM.

I am not a coder so excuse if i sound ignorant but would it be possible to add a line where it would force a reset of the retry count as soon as a new profile begins?
 
TYVM.

I am not a coder so excuse if i sound ignorant but would it be possible to add a line where it would force a reset of the retry count as soon as a new profile begins?

Already added this - now testing if this doesn't mess up something. Deathcount wasn't resetted if UnstuckMe loads the next profile!
 
Hi Haley,
For the A3 profiles I'm running Azmodan last but should any others in particular be first/last as well?
 
Hey sfj & Haley,

Im currently using CIGGARC's Act 3 profiles and i'd like to implement the randomization feature you added on, In the OP, you stated the following :

"with <nextProfile/> the Plugin switches automatically to the next Profile (alphabetical order - except you've a random.txt) (INSIDE OF THE PROFILE Folder)

If i interpreted that correctly, do i have to edit all the profiles statement on the bottom to <nextprofile/> inorder for the randomizer to work.

ie: for their Silhouettes_Rakki.xml

I would replace this line: <Continue profile="Silhouettes_DamnedTower.xml" /> and change it to <nextprofile/>

or

Do I just leave everything alone and simply put a random.txt file in the folder?
 
Last edited:
Hey sfj & Haley,

Im currently using CIGGARC's Act 3 profiles and i'd like to implement the randomization feature you added on, In the OP, you stated the following :

"with <nextProfile/> the Plugin switches automatically to the next Profile (alphabetical order - except you've a random.txt) (INSIDE OF THE PROFILE Folder)

If i interpreted that correctly, do i have to edit all the profiles statement on the bottom to <nextprofile/> inorder for the randomizer to work.

ie: for their Silhouettes_Rakki.xml

I would replace this line: <Continue profile="Silhouettes_DamnedTower.xml" /> and change it to <nextprofile/>

or

Do I just leave everything alone and simply put a random.txt file in the folder?

Leave it as it is - our plugin is also compatible to <Continue> tag!

Just put our random.txt in the profiles directory (& maybe modify it to fit your needs) - randomization must be turned on since CICCARC use such a silly naming scheme...

In some of the actual ACT 3 profiles is no UseTownPortal at the start of the profile - this could cause a bug if the plugin switches to next profile because the toon died to often (or exceed max run time limit after death). But this also happens with Rad's plugin...
 
^ yeup thats exactly what happens, which i posted earlier, i guess its unavoidable, but still your plugin rocks! thanks again
 
dunno what i'm doing wrong, but after some runs/death the profile switcher doesn't work and it always stops after 1 profile and starts again with the same...
any solution on this?
 
dunno what i'm doing wrong, but after some runs/death the profile switcher doesn't work and it always stops after 1 profile and starts again with the same...
any solution on this?

Try using path override. If that doesn't help please post logs
 
Profiles path override in ProfileSwitcher settings
only got this settings :/

unbenannt.webp
 
So what happens if u dont have that random.txt file in your folder and have checked in randomization? Thats what Ive done and I went from 30 yellows per hour to 23. Was using radsprofilemanager before that. Dunno if its bad luck or it like skips a couple of profiles per run?
 
Then you have posted in the wrong thread - you havn't even installed my plugin!

Ask Radonic for support
 
Back
Top