After logging in, the bot doesn't open.

[WarlockSteve]

Name speaks for it's self, I logged into the Bot and nothing pops up, and when I attempt to open and log in again it returns a Max Sessions message.

 

[zeekan]

Happening to me to, i think its cause of the patch but if you could check out my most recent thread and help it would be appreciated thanks!

 

[WarlockSteve]

Yeah I'm not having the same issue as you with your fate scripts not being there.

 

[WarlockSteve]

[14:20:21.975 N] Logging in...
[14:20:22.639 N] T: 5247091142647505915 H: 631338592
[14:20:23.110 D] Microsoft Windows NT 6.1.7601 Service Pack 1
[14:20:23.438 D] System.Exception: Error while writing Memory!
at GreyMagic.ExternalProcessMemory.WriteByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.WriteBytes(IntPtr addr, Byte[] bytes)
at ff14bot.Core.Corze()
at ff14bot.App.Current_Startup(Object sender, StartupEventArgs e)
at System.Windows.Application.OnStartup(StartupEventArgs e)
at System.Windows.Application.<.ctor>b__1(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run(Window window)
at System.Windows.Application.Run()
at ff14bot.App.Main()
here's a log just incase it's needed.

 

[garretjax]

This is from mastahg
Alot of their internal data structs have changed with this patch. Going to mid afternoon EST probably before I will be able to get a version out.

 

[mastahg]

This was to prevent use during the downtime while the bot was being updated.