It always seems like the moment I look away (or fall asleep rather) the bot decides to take a break. Last night I put on a timer for two hours and started to loop Infestation. When I logged in this morning I had 6 completion tokens (about half of what I expected). Anyway - here's the log from about an hour after I went to sleep:
Looped about a million times. It's the only log file that was made between last night and this morning when I logged on and started getting Nav Server error logs. And while I'm on the topic, what exactly does the Nav server being down entail? Is that all on WB core or something to do with Carbine or.. other? For a long time I only used Agility so this is the first time I've experienced Nav Server issues.
Code:
2015-12-29 05:00:01,361 [Pulsator Thread] DEBUG While Tag - While Tag executing <MatchmakingJoin /> (Line #7)
2015-12-29 05:00:01,370 [Pulsator Thread] DEBUG GameLua - Error in pcall: 2
2015-12-29 05:00:01,370 [Pulsator Thread] ERROR Profile Bot - Exception during execution of profile tag <While Condition="1 == 1" /> (Line #3)
Buddy.Wildstar.Game.LuaException: [string "?"]:11: attempt to index field 'wndJoinGame' (a nil value)
at Buddy.Wildstar.Game.GameLua.GetRawValues(String lua)
at Buddy.Wildstar.Game.ConfirmActionButton.()
at Buddy.Wildstar.Engine.PerCachedValue`1.get_Value()
at Buddy.Wildstar.BotCommon.ProfileTags.Matchmaking.MatchmakingJoinTag.<ProfileTagLogic>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Buddy.Wildstar.Engine.Profiles.WhileTag.<ProfileTagLogic>d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Buddy.ProfileBot.ProfileBot.<CoroutineImplementation>d__17.MoveNext()Looped about a million times. It's the only log file that was made between last night and this morning when I logged on and started getting Nav Server error logs. And while I'm on the topic, what exactly does the Nav server being down entail? Is that all on WB core or something to do with Carbine or.. other? For a long time I only used Agility so this is the first time I've experienced Nav Server issues.
