Inherited tags losing names

[AndrewD2]

So I have an IsAttr.? identity tag on my Attribute component.

then in my tags.1st file I have:

  <group
    id="IsAttr"
    dynamic="yes">
    </group>
    
  <group
    id="AttrPrim"
    dynamic="yes"
    inherit="IsAttr">
    </group>
    
  <group
    id="AttrSec"
    dynamic="yes"
    inherit="IsAttr">
    </group>

I did this to make copies of the IsAttr tag but I didn't want the tags on the attributes themselves.

After creating an editor tab for classes and assigning the tags to the class, testing, and reloading the system. When I went back into the tab to create a new class the names of the tags were replaced with just the id. Is there a way to get the names back?

 

[Mathias]

Look for <tag group="IsAttr" tag="attrCon"/> among your thing entries - there's probably places that don't name them, or places that have name="attrCon" in them, and HL is finding that and using it for the tag name.

 

[AndrewD2]

The only place IsAttr is named is via the Identity Tags. There is no place in any file I have that actually declares a copy of the IsAttr tag on anything.

 

[Mathias]

Try adding the tags you want to the tags.1st file, with the proper names set up.

 

[AndrewD2]

That works, its just the purpose of doing the inherited tags is to not have to manually make every tag. Guess I'll just do that for now.

 

[Mathias]

You've got a choice - either get the tag group name right by defining the tag group, or get the tag id names right by letting them be generated as identity tags. inherit="" is a lightweight mechanism, and doesn't copy everything in every circumstance.

 

[AndrewD2]

Is it a viable idea to do an identity tag and then have a component script delete the tag really early if you don't want the tag on the thing all the time?

 

[Mathias]

Wait for the next update of HL itself:

<identity group="Whatever">
  <match><![CDATA[
    !thing.showonly
    ]]></match>
  </identity>

 

[AndrewD2]

Interesting. Does that mean only the matching items will get the tag assigned or only matching items will have the tags created?

 

[Mathias]

Created - that'll be great for cleaning up the editor, since we can exclude lots of things that don't actually need those tags, like the way that the "Available to Classes" selection on the Custom Ability tab shows three options for every base class (which is actually the class, the secondary class, and the archetype header for that class), and we may also be able to clean out all the races, or at least most of them (I'll have to test that part). I think the races are only there in order to handle the option of making them monster classes.

 

[ShadowChemosh]

Nice!

 

[AndrewD2]

Very nice. It would also be nice for something like a "noassign" attribute that would create a tag in memory but not assign it. I can see uses for that.