Trait overloading

[catenary]

I haven’t found anything explicitly discussing trait overloading in the reference material, but I may not be searching effectively. What happens if a specific piece redefines a trait (command) defined in its prototype? In a test using layer traits I can see that both are in effect and trait ordering is enforced, but I’m not sure if overloading is a feature to be leveraged or a problem to be avoided.

[marktb1961]

@catenary

nything explicitly discussing trait overloading in the reference material, but I may not be searching effectively. What happens if a specific piece redefines a trait (command) defined in its prototype? In a test using layer traits I can see that both are in effect and trait ordering is enforced, but I’m not sure if overloading is a feature to be leveraged or a problem to be avoid

If you actually want the duplicate traits to be in effect, then I think that the main side-effect that you will encounter is Property masking. Any Property value on the piece will be taken from the bottom property in the trait list.

I’ve used this sometimes to override a Marker trait value in a prototype.

[jrwatts]

Also keep in mind that if 2 traits share the same Key Command, they will both fire when that Command is issued; the order they will fire in is documented on this page.