-
that’s not a problem to copy with a different name the default starter script, so you can have a 2nd starter script for the 2nd profile, like D2BotMuleLogg.dbj
-
Edit the new D2BotMuleLogg.dbj in lines 38, 39 and 41 renaming the variable LogAccounts from MuleLogger.js. I guess that you could add an s at the end:
for (i in MuleLogger.LogAccountss) {
if (MuleLogger.LogAccountss.hasOwnProperty(i) && typeof i === "string") {
...
chars.push(MuleLogger.LogAccountss[i]);
- Edit the new D2BotMuleLogg.dbj in line 250 , adding an s after default LogGame:
createGame(MuleLogger.LogGames[0] + gameCount, MuleLogger.LogGames[1], 0);
-
Edit the new D2BotMuleLogg.dbj by renaming the log file from MuleLog.json to MuleLogg.json in lines 265, 272-273, 295, 427-428, 453
-
Edit MuleLogger.js adding for the 2nd profile, just after 23rd default line:
LogAccountss: {
"account1/password/realm": ["all"],
"account2/password/realm": ["all"]
},
- Edit MuleLogger.js adding a new line after previous step, with the game name and password for 2nd profile:
LogGames: ["", ""], // ["gamename", "password"]
- Edit MuleLogger.js replacing the default 78th line:
if (getScript("D2BotMuleLog.dbj") && this.LogGame[0] && me.gamename.match(this.LogGame[0], "i")) {
with
if ((getScript("D2BotMuleLog.dbj") && this.LogGame[0] && me.gamename.match(this.LogGame[0], "i")) || (getScript("D2BotMuleLogg.dbj") && this.LogGames[0] && me.gamename.match(this.LogGames[0], "i"))) {
-
select that 2nd starter script on your 2nd mule profile
-
other things:
-
keep in mind the games/hour/…
-
for perming(2h in game) the chars/accounts the number of games/h aren’t an issue
-
for countdown timer refresh there is another way only to log the characters in the lobby, keeping them there a random delay (15-25 sec), then switch to other char. One profile is enough cause it’s really fast. https://d2bot.discourse.group/t/d2bottimerrefresh-dbj/390