What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Latest Beta Build After Patch Not Initializing

L

lyvewyre

Member
Joined
Jan 3, 2013
Messages
418
Reaction score
12
Hey Guys,

Installed the latest beta build, copied settings and started up (like every other update) but I got this message:

Code: 
2016-01-14 03:21:17,106 [1] INFO  CustomLogger (null) - Exilebuddy BETA Version: 0.1.3799.1202
Path: D:\...\<ExeName>

OS Name: Windows 8
OS Edition: 
OS Service Pack: 
OS Version: 6.2.9200.0
OS Architecture: x64

2016-01-14 03:21:22,841 [1] INFO  CustomLogger (null) - ExilebuddyBETA [0.1.3799.1202] is up to date!
2016-01-14 03:21:36,140 [6] INFO  CustomLogger (null) - [Pre-Login] Connecting to BestLatency (122.248.233.213)
2016-01-14 03:21:36,942 [6] INFO  CustomLogger (null) - Region: sea
2016-01-14 03:21:36,943 [6] INFO  CustomLogger (null) - T: 5247569403388789079 H: 4213442133
2016-01-14 03:21:41,171 [11] ERROR CustomLogger (null) - The data required to run the bot was not successfully obtained. Please make sure your key is still valid at the Buddy Auth Portal: http://buddyauth.com/User/Keys 

For any further assistence, please contact support: https://bosslandgmbh.zendesk.com/home
2016-01-14 03:21:57,160 [1] INFO  CustomLogger (null) - [BotManager] MsBetweenTicks = 15

EDIT: // FYI, the above is all that gets logged, so I didn't bother posting a log and instead just copied the above for readability.

So I went and checked my key but definitely still active. Deleted my Globalsettings.cs and tried again with manually inputting my key. Same as above. Completely deleted everything and tried a fresh install. Same message. Tried redownloading with fresh install. Same message.

I have been downloading the beta updates from here.

Is this a case where I should be using the release instead of beta file? EDIT: // Ok So I tried an install from updates.buddyauth.com as well as the release file in awakening release section, with previous settings as well as a fresh install, still getting same issue. Have a feeling this might be a server-side issue.

EDIT:// added the latest log file with release version. I've tried aligning everything as SEA instead of leaving it as Best Latency just in case.
 

Attachments

Last edited:
brycem1989 said:
I'm having the same issue
Click to expand...

Could you upload a full log please? (preferably in a new post tbh....makes it easier to know you need assistance for the devs. =D)
Learn How to by clicking HERE!

@OP ... brb looking something up...
 
Last edited:
Were you able to run with the release version? Updating the bot should not change anything to do with authserv AFAIK - but I am usually wrong about everything lol That being said - try a clean install of the release version with no plugins nor routines just to see if you are able to get in that way... Let me know bud!

Edit:
I was just able to download, install and run the beta version from the link in a sandbox (nothing interfering from other programs/apps) C&P my key from authserv and it gave me no issue. Something on your end is wrong, corrupted or maybe there is a space before or after your key?

_123 or 123_ is not the same as 123. I've made the mistake myself before - its a mother fkkr to find when you are flustered lol
 
Last edited:
flairdevil said:
Were you able to run with the release version? Updating the bot should not change anything to do with authserv AFAIK - but I am usually wrong about everything lol That being said - try a clean install of the release version with no plugins nor routines just to see if you are able to get in that way... Let me know bud!
Click to expand...

Yeah I'd tried that. Was running into the same issue. However! I have found a solution. I manually changed my auth server from SEA to North America and its logged in fine so far. I did this on the user/Keys as well as EB. I am going to try and update with all settings and see if it works.

TLDR: Something up with SEA Auth Server from my limit testing. I logged in under NA auth server no worries.

EDIT:// yeah so fresh release install then copied over all my settings and stuff from previous install. Edited GlobalSettings.json on line 48 and changed Authregion to "2" (which is North America) and I've logged in fine.
 
Last edited:
lyvewyre said:
EDIT:// yeah so fresh release install then copied over all my settings and stuff from previous install. Edited GlobalSettings.json on line 48 and changed Authregion to "2" (which is North America) and I've logged in fine.
Click to expand...

Awesome! One down....kinda ;-)
 
Sorry you had issues! I'll mention this to the Auth team, as there's nothing I can do about it myself, as perhaps there was a delay or syncing issue when offsets were uploaded.
 
pushedx said:
Sorry you had issues! I'll mention this to the Auth team, as there's nothing I can do about it myself, as perhaps there was a delay or syncing issue when offsets were uploaded.
Click to expand...
Liar. It's all YOUR fault and you know it! Admitting you have a problem is the first step...
 
Just changed mine to North America also and it fixed this issue. I'll keep an eye on this post to see when I can change back to SEA. Thanks.
 
Just to let you guys know, I was told the SEA issue should now be resolved!
 
You must log in or register to reply here.
Back
Top