-= Gametoast.com =-

This is probably very trivial, but can anyone explain this error? I'm assuming it has something to do with the odf files.

Message Severity: 3
.\source\Entity.cpp(121)
Entity base class "" not found

I think that means a class couldn't find its ClassParent

These are BF1 sides. None of the units odf's use class parents.
Edit 1: Then again I did setup a secondary skin file for all of them. Maybe I screwed up somewhere.
Edit 2: Yep, that did it. BF1 doesn't use classparents.

It might be down to the munger. I've seen BF2 sides moved into BF1 in the past prior to the release of the BF2 mod tools and they worked somewhat.

ClassParents don't work in SWBF1, from what I know. Rather, they aren't even a feature. Another reason why I don't mod the game.

It's very limited mod wise. I added all the information necessary for the odf's and it worked.
The SWBFII mod tools are sooo much nicer.

Marth8880 wrote:ClassParents don't work in SWBF1, from what I know. Rather, they aren't even a feature. Another reason why I don't mod the game.

As far as I know, nobody has actually tried the ODFMunge from BF2 with the BF1 mod tools. There's probably code to parse ClassParent behaviour in the BF2 ODFMunge application but not in the BF1 ODFMunge.

I agree that the bf1 mod tools are limited. SWBF2 has much more possibilities and potential. The bf1 tools are mostly used to munge sound. Luckily my bf2 sound munge works just fine though with the edited .bats.


OFF TOPIC:
almost comma spliced.

ggctuk wrote:

Marth8880 wrote:ClassParents don't work in SWBF1, from what I know. Rather, they aren't even a feature. Another reason why I don't mod the game.

As far as I know, nobody has actually tried the ODFMunge from BF2 with the BF1 mod tools. There's probably code to parse ClassParent behaviour in the BF2 ODFMunge application but not in the BF1 ODFMunge.

The engine got several significant upgrades between SWBF and SWBF2(Lua, ODF, materials). So it wouldn't know what to do with ClassParent codes if it smacked them upside the head with 'em.

THEWULFMAN wrote:

ggctuk wrote:

Marth8880 wrote:ClassParents don't work in SWBF1, from what I know. Rather, they aren't even a feature. Another reason why I don't mod the game.

As far as I know, nobody has actually tried the ODFMunge from BF2 with the BF1 mod tools. There's probably code to parse ClassParent behaviour in the BF2 ODFMunge application but not in the BF1 ODFMunge.

The engine got several significant upgrades between SWBF and SWBF2(Lua, ODF, materials). So it wouldn't know what to do with ClassParent codes if it smacked them upside the head with 'em.

It depends on whether ClassParent is processed by the game, or by the munger. It's entirely possible that the munger 'combines' the properties of the classparent into the child ODFs.

It doesn't. ClassParent does not exist in SWBF1 in any form, and ODFs are still largely just text files after the munge.

Interesting... but now that we're on the subject I can remember a mod for BF1, prior to the release of BF2's mod tools, that ported the BF2 sides over to BF1, and they still worked (to an extent).. I can't seem to find the mod though, but I seem to recall it being hosted on SWBFFiles.