Before the project etal forums went down, there was a post in the wiki by mf022 that did this. I don’t know if I still have the old version of the files but I think he added an anti-idle function into libs/common/prototypes.js and an entry into tools/toolsthread.js to assign a key to it. I always ran D2BotMap and logged in manually, then hit the “/” key to activate it. It would run around whatever acts you have unlocked on that toon and a timer would sit over the toons head. I’ll look for my old files but you could check github and see if he ever posted it over there.
I just had it in my head to have it use D2BotMule in order to auto log mules, and then maybe incorporate a portion of IP hunter’s waiting time, or even the SOJ sold wait time portion - somehow. Yeah there was alot of good resource on projetal. I can access some of it through the Internet Time machine, but it’s pretty hit and miss, same with Blizzhackers.
The mule perming was added to MuleLogger.js.
All you have to do is to use D2BotMuleLog.dbj starter script and to edit MuleLogger.js with appropriate value for IngameTime (check the description on line 30)
Change this below in Mulelogger.js
IngameTime: rand(20, 30), // (180, 210) to avoid RD, increase it to **(7230, 7290) for mule perming** //Change (20, 30) to (7230, 7290) for perming
20 - 30 sec in game with a lot of accounts when you are trying to reset the countdown timer is too low, and you’ll get a temporary restriction soon. The repeatedly quitting of the games below 2 minutes is quickly restricted.
Anyway, this topic was about perming new mule chars, with 7200 + sec in game, so … the default timers mentioned in the comment on line 30 of MuleLogger.js are ok.
Maybe there are other private scripts that are still working for perming mules, but it’s ok to use for free the default D2BotMuleLog.dbj starter script and you can perm easily a lot of d2 accounts.