Oh man what a great plugin, it just needs one more thing !
Reloading current profile can cause certain problems, such as azmodan profile or cydea. What it needs to do is start the first profile that db started. This will solve two problems:
The first is the one i mentioned above, while the second is as follows: Some ppl have different folders for different set of profiles. I too like to randomize profile usage on all of my bots and i always choose a set of proiles from different folder each time i start db coz each folder have differently scheduled profiles. Now, if i am to set a starting profile in this plugin i.e. c/user/folder/db/profiles/set1/starthere.xml a problem will occur coz then it will set all of my bots on that set of profiles (in folder set1) after each bot gets stucked. Is there any way it can read the pforile that db first started with and continue from there ? This way we can have each restart to be in its respective folder.
Do this and you have solved the world water crisis... no w8, you just solved the stucks behind walls in underbridge/barracks, still awesome though![]()
Let me understand your requriement.
1. You have multiple instance DB running in the same folder
2. The multiple bot are running different profiles in different folders.
3. If you set the start file for one of your bot, other bot will be forced to use that start file as well.
4. So you want to more dynamic start profile detection, such as, first profile that db loaded, isn't it?
Well, based on my understanding, copy and paste your db folder to multple instance and run them seperatedly would tempory solved this issue.
I will see whether I can auto-detect the start profile when game joined.