What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Rebornbuddy64 beta

Status
Not open for further replies.
If your having any issues please try the following:

1) Clean directory, don't install any third party software, if it starts fine then its an issue with your addons.
2) Disable any antivirus that may be running. If your getting filenotfound theres a good chance its deleting one of our dlls
3) Uninstall all installed versions of .net and vc++ runtime and rerun the wizard. Sometimes .net installs get corrupted
 
Iam starting RebornBuddy as admin and the Key window pop up. After pressing log in the Windows goes away and comes back not more.

[16:56:59.899 N] RebornBuddy64 1.0.140.0
[16:57:41.067 N] Logging in...
[16:57:41.493 N] T: 5248026949038131945 H: 2655232094
[16:57:41.602 N] Error during login procedure
[16:57:41.719 N] Authentication failed!

I checked the Key already and its right. (it worked before Stormblood.)

Your using the release version, not the beta. That is why its not working. Download the beta in the first post of the thread.
 
Getting a ton of latency issues,

[02:00:21.806 N] Latency to Buddy service: 123 ms
[02:00:38.275 N] Latency to Buddy service: 104 ms
[02:01:07.033 N] Latency to Buddy service: 84 ms
[02:02:21.839 N] Latency to Buddy service: 85 ms
[02:02:38.113 N] Latency to Buddy service: 192 ms

Is this something to be concerned about? It at times stops my botting. Not sure what's going on as I have a great connection and nothing else is lagging.

That's not high latency, and it is not stopping your botting.

Post a log if your having issues.
 
I just downloaded the software today - so it's completely clean. I'm running Windows 10 and it's up to date. Mine seems to be an issue with the gathering profiles from 50-60. I haven't tried any other profiles.
 
The direct x 9 version of final fantasy is not supported by this client, use reborndubby = please helpppppppp i cant open my bot
 
If your having any issues please try the following:

1) Clean directory, don't install any third party software, if it starts fine then its an issue with your addons.
2) Disable any antivirus that may be running. If your getting filenotfound theres a good chance its deleting one of our dlls
3) Uninstall all installed versions of .net and vc++ runtime and rerun the wizard. Sometimes .net installs get corrupted
nope it didn't work any of the 3 im on Windows 10 Creators up todate one and here is the Event Viewer

Application Error - Event ID 1000-------
Faulting application name: RebornBuddy.exe, version: 1.0.112.0, time stamp: 0x5950430d
Faulting module name: KERNELBASE.dll, version: 10.0.15063.296, time stamp: 0xa0527b0c
Exception code: 0xe0434352
Fault offset: 0x0000000000069e08
Faulting process id: 0x19ac
Faulting application start time: 0x01d2eeaa1b12ac6a
Faulting application path: C:\Users\XXXXXl\Downloads\Rebornbuddy64BETA 1.0.112.0\RebornBuddy.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 0edbaddf-c0d9-4eb6-95e8-f5ca40f4d1b7
Faulting package full name:
Faulting package-relative application ID:

.NET Runtime - Event ID 1026-------
Application: RebornBuddy.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at ff14bot.Core.InitalizeHook()
at ff14bot.App.Current_Startup(System.Object, System.Windows.StartupEventArgs)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at ff14bot.App.Main()

alot of people are having the same problem with the Windows 10 Creators
 
nope it didn't work any of the 3 im on Windows 10 Creators up todate one and here is the Event Viewer

Application Error - Event ID 1000-------
Faulting application name: RebornBuddy.exe, version: 1.0.112.0, time stamp: 0x5950430d
Faulting module name: KERNELBASE.dll, version: 10.0.15063.296, time stamp: 0xa0527b0c
Exception code: 0xe0434352
Fault offset: 0x0000000000069e08
Faulting process id: 0x19ac
Faulting application start time: 0x01d2eeaa1b12ac6a
Faulting application path: C:\Users\XXXXXl\Downloads\Rebornbuddy64BETA 1.0.112.0\RebornBuddy.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 0edbaddf-c0d9-4eb6-95e8-f5ca40f4d1b7
Faulting package full name:
Faulting package-relative application ID:

.NET Runtime - Event ID 1026-------
Application: RebornBuddy.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at ff14bot.Core.InitalizeHook()
at ff14bot.App.Current_Startup(System.Object, System.Windows.StartupEventArgs)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at ff14bot.App.Main()

alot of people are having the same problem with the Windows 10 Creators

I'm using the creators update, a clean install of windows 10->buddywizard results in the bot working correctly. Something on your machine is interfering with the bot from working properly.

I just downloaded the software today - so it's completely clean. I'm running Windows 10 and it's up to date. Mine seems to be an issue with the gathering profiles from 50-60. I haven't tried any other profiles.
That's a profile issue, post in the profiles thread.
The direct x 9 version of final fantasy is not supported by this client, use reborndubby = please helpppppppp i cant open my bot
Set ff14 to use directx11 in the launcher

I just deleted and reinstalled, same error popping up. Attached the logfile.

No you didn't. There a tons of additonal items in that log. Fresh Download -> Unzip -> Run bot
 
No you didn't. There a tons of additonal items in that log. Fresh Download -> Unzip -> Run bot

Those items are from downloads I did today. Reborn Buddy itself works, but from what I can see unless I'm a total noob (which is entirely possible these days) is that I need to select a profile for mining to take me from 50-60. When I load the RB software it starts up, logs me in etc. But when I try to run y2crayzs's mining profile (located here: https://www.thebuddyforum.com/threads/order-bot-mining-leveling-1-60-1-50-quests.223348/) , that's where I get hung up.

Is this just an issue with the profile?
 
nope it didn't work any of the 3 im on Windows 10 Creators up todate one and here is the Event Viewer

Application Error - Event ID 1000-------
Faulting application name: RebornBuddy.exe, version: 1.0.112.0, time stamp: 0x5950430d
Faulting module name: KERNELBASE.dll, version: 10.0.15063.296, time stamp: 0xa0527b0c
Exception code: 0xe0434352
Fault offset: 0x0000000000069e08
Faulting process id: 0x19ac
Faulting application start time: 0x01d2eeaa1b12ac6a
Faulting application path: C:\Users\XXXXXl\Downloads\Rebornbuddy64BETA 1.0.112.0\RebornBuddy.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 0edbaddf-c0d9-4eb6-95e8-f5ca40f4d1b7
Faulting package full name:
Faulting package-relative application ID:

.NET Runtime - Event ID 1026-------
Application: RebornBuddy.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at ff14bot.Core.InitalizeHook()
at ff14bot.App.Current_Startup(System.Object, System.Windows.StartupEventArgs)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at ff14bot.App.Main()

alot of people are having the same problem with the Windows 10 Creators

I have the same problems on 2 Machines, the third is running well. The strange thing is, that the outdated client worked until Stormblood. Just the Beta doesn´t open the Login screen. No AV active, clean install of Beta, Buddywizard used.
 
I'm using the Fatebot now, seems to be working ok at level 30 in beta. Still trying to figure out mining and OrderBot though.
 
I have the same problems on 2 Machines, the third is running well. The strange thing is, that the outdated client worked until Stormblood. Just the Beta doesn´t open the Login screen. No AV active, clean install of Beta, Buddywizard used.
I added some extra debug information to version 116 please try that and upload the log
 
If your having any issues please try the following:

1) Clean directory, don't install any third party software, if it starts fine then its an issue with your addons.
2) Disable any antivirus that may be running. If your getting filenotfound theres a good chance its deleting one of our dlls
3) Uninstall all installed versions of .net and vc++ runtime and rerun the wizard. Sometimes .net installs get corrupted

after talking to @zzi we got all sorted out and i think all of the above helped with it! RB now up and running
 

Attachments

Last edited:
[19:02:20.720 N] RebornBuddy 1.0.488.0
[19:03:20.606 N] Logging in...
[19:03:21.873 N] T: 5248027024435862391 H: 3116664437
[19:03:21.995 N] Error during login procedure
[19:03:22.326 N] Authentication failed!
I just dl the beta it gliches my game screen black than does nothing can i have some help stetting up the rebronbuddy i think the link on the top of the page is broken
 
[19:02:20.720 N] RebornBuddy 1.0.488.0
[19:03:20.606 N] Logging in...
[19:03:21.873 N] T: 5248027024435862391 H: 3116664437
[19:03:21.995 N] Error during login procedure
[19:03:22.326 N] Authentication failed!
I just dl the beta it gliches my game screen black than does nothing can i have some help stetting up the rebronbuddy i think the link on the top of the page is broken

That's not the beta.

Download the beta into a empty folder.
 
with 116 i had the same issues with the slimDX.dll and now with 117 i just got the Rebornbuddy Versionnumber in the log, rebornbuddy is running in background, no window for login popped up. Can´t give more information, i´m at work and logged in via remote Desktop.
 

Attachments

Status
Not open for further replies.
Back
Top