No "routine fitting for your class"

[noamchomsky]

Fresh install of 5800. Using the Questing option. When I click Start I get this error.

Could not find a routine fitting for your class. Please make sure you have a proper combat class routine in your folder, and restart Honorbuddy.

How do I fix it please?

I already have a fresh installation of the Singular CCs installed in the default location ( ..\Honorbuddy\CustomClasses\Singular\ClassSpecific\DeathKnight ). Using Kick's questing profile: [Fly][N - Quest] Hyjal 80-82 [Kick].xml

Thanks!

 

[projektt]

Here's your problem

[8:07:04 PM:326] Could not compile CC from M:\games\WoW\Honorbuddy\Honorbuddy\CustomClasses\Singular!

exactly why it says this

[8:07:06 PM:941] Could not find a routine fitting for your class. Please make sure you have a proper combat class routine in your folder, and restart Honorbuddy.

Go redownload it because it seems as if you messed with the file since it is saying all this


File: Holy.cs Line: 68 Error: 'Singular.Settings.PriestSettings' does not contain a definition for 'DivineHymnCount' and no extension method 'DivineHymnCount' accepting a first argument of type 'Singular.Settings.PriestSettings' could be found (are you missing a using directive or an assembly reference?)
File: Holy.cs Line: 82 Error: 'Singular.Settings.PriestSettings' does not contain a definition for 'PrayerOfHealingSerendipityHealth' and no extension method 'PrayerOfHealingSerendipityHealth' accepting a first argument of type 'Singular.Settings.PriestSettings' could be found (are you missing a using directive or an assembly reference?)
File: Holy.cs Line: 82 Error: 'Singular.Settings.PriestSettings' does not contain a definition for 'PrayerOfHealingSerendipityCount' and no extension method 'PrayerOfHealingSerendipityCount' accepting a first argument of type 'Singular.Settings.PriestSettings' could be found (are you missing a using directive or an assembly reference?)
File: Holy.cs Line: 85 Error: 'Singular.Settings.PriestSettings' does not contain a definition for 'CircleOfHealingHealth' and no extension method 'CircleOfHealingHealth' accepting a first argument of type 'Singular.Settings.PriestSettings' could be found (are you missing a using directive or an assembly reference?)
File: Holy.cs Line: 85 Error: 'Singular.Settings.PriestSettings' does not contain a definition for 'CircleOfHealingCount' and no extension method 'CircleOfHealingCount' accepting a first argument of type 'Singular.Settings.PriestSettings' could be found (are you missing a using directive or an assembly reference?)
File: Holy.cs Line: 107 Error: 'Singular.Settings.PriestSettings' does not contain a definition for 'HolyFlashHeal' and no extension method 'HolyFlashHeal' accepting a first argument of type 'Singular.Settings.PriestSettings' could be found (are you missing a using directive or an assembly reference?)
File: Holy.cs Line: 111 Error: 'Singular.Settings.PriestSettings' does not contain a definition for 'HolyGreaterHeal' and no extension method 'HolyGreaterHeal' accepting a first argument of type 'Singular.Settings.PriestSettings' could be found (are you missing a using directive or an assembly reference?)
File: Holy.cs Line: 115 Error: 'Singular.Settings.PriestSettings' does not contain a definition for 'HolyHeal' and no extension method 'HolyHeal' accepting a first argument of type 'Singular.Settings.PriestSettings' could be found (are you missing a using directive or an assembly reference?)

 

[noamchomsky]

Yes but only when updating the Singular folder to its SVN, Revision 607: /trunk/Singular

I'll try a fresh installation again, this time without updating Singular....

 

[Kickazz006]

it means there is no spec in that cc for you

change your spec

but first... re-install hb

 

[noamchomsky]

Ok, thanks! That time it worked because (after the fresh installation) I did NOT do the SVN update on top of the existing Singular folder (build 576 ?). Instead, I removed the original, created a new folder named Singular and then did the SVN update to build 607. (Just an FYI in case anyone else has this issue.)

Thanks again for the awesome support guys!