MODELDEF : Inheritance

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is ON
[img] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: MODELDEF : Inheritance

Re: MODELDEF : Inheritance

by SPZ1 » Tue Mar 23, 2021 3:45 pm

I was thinking that the child list would start off where the parent list ended so you could still specify more paths and frames or whatever it may be

Re: MODELDEF : Inheritance

by Cherno » Mon Mar 15, 2021 2:56 pm

From what I understand, this is not possible due to the way MODELDEF is parsed internally. The advantage of the current system is that you can change path, models and (surface)skins at any point in the MODELDEF lump, for example in between two FrameIndex lines. This would not be possible with inheritance.

MODELDEF : Inheritance

by SPZ1 » Mon Mar 15, 2021 11:59 am

Would it be easier to inherit from a parent to change a skin than to copy 100 frames to do so?

Code: Select all

MODEL ChildModel : ParentModel {
   skin 0 "alternate.jpg"
} 

Top