sinterlkaas
New Member
- Joined
- Jan 17, 2012
- Messages
- 536
I do have the same problem. Relogger opens my D3 session until the part where he should login and then the following error appears. (Demon Buddy has no been started to this point) I do have demon buddy path and D 3 path update in the relogger (they are not in the same folder)
[31.10.2012 13:29:58] Relogger Crashed! with message Der Index lag au?erhalb des Bereichs. Er muss nicht negativ und kleiner als die Auflistung sein.
Parametername: index
[31.10.2012 13:29:58] bei System.ThrowHelper.ThrowArgumentOutOfRangeException()
bei System.Collections.Generic.List`1.get_Item(Int32 index)
bei YetAnotherRelogger.Helpers.Bot.ProfileScheduleClass.get_GetProfile()
bei YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.Start()
bei YetAnotherRelogger.Relogger.ReloggerWorker()
What does your profile schedule look like?
Everything working fine as far I can tell.
However, there is a weird problem for me, the tool will open a game according to the profile set, then it will stop and start the bot while in loading screen (why?).
This however does something bad to the bot or the profile and it just won't move at all.
I will post a log once I get access to the VM where the bot is running on
Could be related to the AntiIdle mechanism built in .. also check demonbuddy log what happened there..
Last edited: