New version instantly closes

Ask for key and when I click the login button it instantly closes. Not just me. I asked a few friends who use it and all of them are having the same issue.

Any ideas?


Log file has this:

Code:

[22:28:55.773 N] Logging in...
[22:28:55.955 N] T: 5247390379785548426 H: 1907076952
[22:28:56.074 D] Microsoft Windows NT 6.2.9200.0
[22:28:57.780 D] System.Exception: Assembly failed!  Error code: -108;  Error Line: 2
   at Fasm.ManagedFasm.Assemble(String szSource, Int32 nMemorySize, Int32 nPassLimit)
   at ff14bot.Core.()
   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 ff14bot.App.Main()

 

It has already been reported. No need to make a new thread for it.
https://www.thebuddyforum.com/rebor...pment-priorities-post1987930.html#post1987930

 

No clue what you are talking about. I do not see a thread in the Reborn forums where it was already reported. Which is why I created this one.

Thank you for the smartass response though.

 

https://www.thebuddyforum.com/rebor...pment-priorities-post1987930.html#post1987930

 

Ah so it was posted in a Development Priority thread where it does not belong and makes no sense for it to be and have no reason to look for it there.

Thanks again.

 

I would think it would belong in the development priority thread myself, since its a priority in development.. since its an expansion and all, but none the less, its been reported.

 

Either way this is the proper place to create the thread and a full log was attached for him to see. Weather you think it is needed or not does not really concern me. Have a good day.

 

both issues aside support issues go in the support forum not the general.

 

I like chocolate milk

 

Bread makes me poo!

 

The new Beta build should be working now, update to 1.0.25.0

 

Sweet thanks.

 

Will it work on the old Pre-Expansion questlines or for grinding?

 

Questing is broken atm. I'd wait for word from mastahg on it through a later update.

 

Thanks. How about grinding?

 

all movement is disabled. he shut down the nav server. you will get a connection closed as soon as you call for a location to move to. combat assist only it seems. maybe old crafting I havent tried.

 

Thanks, I'm assuming that includes the fate bot as well. Sorry for the 20 q's - this is the first time I've used this bot (came from Honorbuddy & WoW).

 

yeah for now we can only use combat assist. much like yourraidingbuddy and enyo from wow (kind of) but mastahg is cranking it out so we may see more soon.

 

Where we can find the new beta build please ?

 

https://www.thebuddyforum.com/rebornbuddy-forum/218462-expansion-update-thread.html

Second post