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

Error: No routines were loaded. Please ensure there is a routine for your class

Firework

New Member
Joined
Jun 13, 2012
Messages
140
Reaction score
1
Error: No routines were loaded. Please ensure there is a routine for your class before starting the bot.

What causes this error I can't even remember what exactly I did to my witchdoctor setup before this happened:

Fresh install of the latest version:

Sarktooth Farmer r50//Sarktooth Dummy Profile by Inegro
NotificationOkClick 0.9 by neoz

Settings button does nothing when clicked. Not use to this error over all the versions of DB.
 
Is it the Common.IsElite error?
That happens when there's a compiling error for routines.
 
Is it the Common.IsElite error?
That happens when there's a compiling error for routines.

I have no idea but its pissing me off it won't work for Arreat or Sark.

Here is log.

It won't even let me pick between generic or balph it just pukes up the error I mentioned in the title in an error box.

I could screen cap it if you like.
 

Attachments

[06:39:46.120 N] Compiler Error: c:\2\Routines\Belphegor\Routines\WitchDoctor.cs(15,18) : error CS0101: The namespace 'Belphegor.Routines' already contains a definition for 'WitchDoctor'

Try downloading the bot again and replacing the belphegor files.
 
Working now thank you but oddly enough I tried this fix before last time it failed oddly enough. Guess a fresh restart was helpful. Albeit I should post on buddy guys thread to tell him his witch doctor mod for belph is giving errors?
 
Working now thank you but oddly enough I tried this fix before last time it failed oddly enough. Guess a fresh restart was helpful. Albeit I should post on buddy guys thread to tell him his witch doctor mod for belph is giving errors?
Pretty sure it's only you, because if it was everyone nobody would be able bot without a custom WD :)
 
I had this error and figured i got it because i runned my shared HB on a local network. (if somebody else still have this problem) :)
 
Back
Top