Help With Script Error

[Furiousfox]

Hey I just put subclasses into my GTBS game and when I am in a tactical battle and press B twice over an enemy to view their stats and class I get this error and the game crashes.
I have no idea how I would define a subclass. I think it would be fine if pressing BB on an enemy to see their stats just didnt show their subclass, anyway to fix this?

 

[Shaz]

I've moved this thread to RGSSx Script Support. Thank you.

Please add a link to the script. I don't know why it would be calling Draw Actor Class for an enemy ... what other scripts do you have that affect enemies?

 

[Furiousfox]

The script is GTBS 2.4 with Yanfly subclass system added I believe. Its a tactical battle system and normally you can press a character to see their stats and class, but when I try and do it on an enemy it gives that error. Maybe because I dont have a subclass setup for the enemy? But I dont know how to set one up.
Pic related is it working with regular PC Characters but it doesnt work with enemies.

 

[Roninator2]

Yanfly subclass system added I believe

Please be precise.
Yanfly class system?
Can you not give the names at least? A link to the script is what is always preferred.
This just allows us to help you better and faster, otherwise we could give a solution for something that you're not even using.

Add above that line (741) this line
return if actor.is_a?(Game_Enemy)

 

[Furiousfox]

All the scripts say GTBS and are dated 2015. I do not have a link to the script unfortunately. Perhaps I can upload all the scripts im using somewhere? (although they all say GTBS)

 

[Roninator2]

Still... you are using a yanfly script.
Regardless I posted a possible solution above.

 

[Furiousfox]

Sorry I did not see the solution before I replied, it worked, you are amazing how do I virtually hug and kiss you?

 

[Andar]

@Furiousfox
just an added comment about something I see in your error message screenshot.

whenever you add a script, you should name the slot you place the script in.
see that part "script '' Line 741" in that screenshot?
That should read "Script 'name of scriptslot' Line 741"

It doesn't matter if you know the script that has a problem, but if the error comes from a combination of scripts and you have to use the backtracer or anything else more complex, the missing name of the scriptslot will make bughunting extremely complicated.