I have been getting the "data/secure/++++++++++++++.txt does not exist error" when trying to drop with limedrop.
No clue what causes this, all mules have been created with automule and were dropping fine at some point. I have been rarely using the NumPad6 to update when i drop by hand ( e.g.: when Dropper Keys are in use by soloplay or whatever), but only on already created mules by automule ofc. I have done this in past seasons without problem.
I have been trying with mulelogger on 1 acc and this fixes limedrop for that char.
I would like to kindly ask if there is a possibility that mulelogger could get an "Update Function", where it just updates the existing mules with the configured pw's, but keeps item-information, without creating games.
Or if that is not possible to mulelogger use an existing game by joining, so he can log as quick as the droppers ( 15 secs ingame, 15sec wait in lobby seems fine for droppers). But creating games for as in my case 42x18 chars is an obvious problem.
Any info on what causes/could cause this behaviour appreciated
TY in advance
Update#1 - Logging 1 char per acc with mulelogger fixes the whole acc! So this is manageable
Update#2 - This is how i got it fixed
WARN - risk of temp bans if switching accs too fast - WARN
Do Mulelogger on your accs but provide not existing charnames, it will login, check for char and skip to next acc updating password for these accs but not creating any games
Setup Mulelogger like this:
"account1/password1/realm": ["notexistingchar"],
"account2/password1/realm": ["notexistingchar"],
"account3/password1/realm": ["notexistingchar"],
I tried and 3 accs at a time seems to be fine, 4 was too much already! wait 15-20 secs in between logging attempts ( setup your mulelogger for the next 3 accs meanwhile)
Cheers.
PS.: Mulelogger seemed to randomly skip accs / skip login attempts, not sure if relevant, u can check your droppers by providing not existing game/pass
PPS.: This may be a Workaround for all People receiving the "data/secure/++++++++++++++.txt does not exist error"
PPPS.: Mulelogger only scrolls down through all 18 Chars with the 1st acc, next accs it will login and leave without scolling down, this is unwanted behaviour i suppose, and it smells like it may be linked to the cause of this problem in the 1st point > checking if droppers behave same way on 18 char accs
PPPPS.: Mulelogger doesn't need to login at all to get this result, maybe my "update feature request" could be implemented e.g.: by using a charname in mulelogger configuration that cannot be created on bnet anyways.
I have been getting the "data/secure/++++++++++++++.txt does not exist error" when trying to drop with limedrop.
No clue what causes this, all mules have been created with automule and were dropping fine at some point. I have been rarely using the NumPad6 to update when i drop by hand ( e.g.: when Dropper Keys are in use by soloplay or whatever), but only on already created mules by automule ofc. I have done this in past seasons without problem.
I have been trying with mulelogger on 1 acc and this fixes limedrop for that char.
I would like to kindly ask if there is a possibility that mulelogger could get an "Update Function", where it just updates the existing mules with the configured pw's, but keeps item-information, without creating games.
Or if that is not possible to mulelogger use an existing game by joining, so he can log as quick as the droppers ( 15 secs ingame, 15sec wait in lobby seems fine for droppers). But creating games for as in my case 42x18 chars is an obvious problem.
Any info on what causes/could cause this behaviour appreciated
TY in advance
Update#1 - Logging 1 char per acc with mulelogger fixes the whole acc! So this is manageable
Update#2 - This is how i got it fixed
WARN - risk of temp bans if switching accs too fast - WARN
Do Mulelogger on your accs but provide not existing charnames, it will login, check for char and skip to next acc updating password for these accs but not creating any games
Setup Mulelogger like this:
"account1/password1/realm": ["notexistingchar"],
"account2/password1/realm": ["notexistingchar"],
"account3/password1/realm": ["notexistingchar"],
I tried and 3 accs at a time seems to be fine, 4 was too much already! wait 15-20 secs in between logging attempts ( setup your mulelogger for the next 3 accs meanwhile)
Cheers.
PS.: Mulelogger seemed to randomly skip accs / skip login attempts, not sure if relevant, u can check your droppers by providing not existing game/pass
PPS.: This may be a Workaround for all People receiving the "data/secure/++++++++++++++.txt does not exist error"
PPPS.: Mulelogger only scrolls down through all 18 Chars with the 1st acc, next accs it will login and leave without scolling down, this is unwanted behaviour i suppose, and it smells like it may be linked to the cause of this problem in the 1st point > checking if droppers behave same way on 18 char accs
PPPPS.: Mulelogger doesn't need to login at all to get this result, maybe my "update feature request" could be implemented e.g.: by using a charname in mulelogger configuration that cannot be created on bnet anyways.