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!

Error when trying to start: Object reference not set to an instance of an object

skynetwork

Member
Joined
Jan 25, 2012
Messages
231
all of a sudden my version crashes right after trying to connect!

tried .690 international, .696 international, .696 german, .358 Beta (all clean installs without any plugins or stuff). i did not change anything on my system, no updates or else.

anything worked fine, started the bot during nighttime, working flawless. all of a sudden it broke and when i tried to bring it up again in the morning i got this error. whenever i try to login with whatever version it crashes. not log, nothing. just refuses the login. i tried the regular honorbudyy.exe and the honorbuddy.launcher.exe.

first time ever that i experience such an error and have no idea what might have broken absolutely nothing on my system changed in any way and i did not change anything on the bot (while i was asleep lol).

ofc i am running 32-bit, dx9 and all that stuff. as i already said, the bot worked fine and i did not change anything. now no version works. any idea? i tried to use the search function but did not find anything yet...

1.webp

Unfortunately all the logs only look like this:

Code:
[12:20:27.492 N] Honorbuddy v2.5.8115.368 started.
[12:20:27.493 Q] This is a BETA build of Honorbuddy. This is not meant for general usage. Please report any issues you may have in the beta thread on our forums.
[12:20:27.493 Q] This build may have bugs, and new features which may not be fully tested. Use at your own risk!
[12:20:28.719 N] Logging in...

then it crashes like in the screenshot above...
 
lol nevermind.... it did a complete systemrestart and now the bot works again.... no clue wtf caused this error.... can be closed, thanks :)
 
Back
Top