advice category hierarchy diversion items

i'm minute lees engine i've only started diversion vigilant model, needs extensible.

i need assistance especially since i've finished feels messy, nonetheless i can't cruise another fortitude works better.

i have category called mudobject, another category called container, enclosing enclose churned mudobjects, nonetheless mudobject itself, however mudobjects need know contained in.

so feeling something this:

public summary category mudobject
{
    enclosing containedby;
}

public summary category enclosing : mudobject
{
    list<mudobject> contains;
}

(please note only instance qualifiers opening modifiers, properties such missed off)

now only itself seems messy, nonetheless lets supplement something else mix:

item mudobject visible equipment (such weapons) hereditary from, however need containers too (like chests). nonetheless theres such churned estate c#, comes down interfaces, best choice enclosing an interface (as distant i see) however there reason i didn't wish be, being adding an mudobject enclosing means enclosing transform mudobjects .containedby value.

any ideas work, am i descending trap origination things too complicated?

if else suggest?