Code: Select all
Message Severity: 3
.\Source\Explosion.cpp(171)
Explosion base class "com_weap_inf_detpack_dispenser_exp" not foundModerator: Moderators

Code: Select all
Message Severity: 3
.\Source\Explosion.cpp(171)
Explosion base class "com_weap_inf_detpack_dispenser_exp" not found


Into the sides folder? Yes, I did. I didn't change them at all.-_- wrote:Are you sure you copied the Common assets as well?




I checked in F:\BF2_ModTools\assets\sides\Common\odf, but there is no file named "com_weap_inf_detpack_dispenser_exp" there. Does someone else have this file? Could someone post its contents so I can move on?psych0fred wrote:com_weap_inf_detpack_dispenser_exp is in C:\BF2_ModTools\assets\sides\Common\odf so if you want to use parent classes you will have to create them in your mod. Otherwise just consolidate all the parent class contents into your side odfs and get rid of the parent class line. Parentclass lines just tell it to compile all the linked odfs into one file during the munge. If it can't find the file it can't collect it's contents. The only reason parent classes were used to change the properties of many objects at the same time (so they all inherit the changes). If you instead put all the data in the file in your side you won't have a problem.
In case that isn't clear, for BF2 a single odf was broken up into several, where the parentclass odf can be inherited by other odfs so all of their contents is pooled into a single ODF during the munge. That way when you want to change the properties of something that more than one unit uses you change one file instead of a couple dozen.

