• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

"Invalid Tag template"

Paragon

Well-known member
Anybody have any idea why the following construct would be producing the above result? It doesn't seem to be a problem with the tag itself (that produced a different error). Is there something generically wrong with this as a construct, or is it a case where individual game systems all do this different (as I'm pretty sure I've used this sort of construct for an exp-req in SW before without trouble)? If its a system specific issue I'm obviously in the wrong place, but this kind of construct seems to work in more than one, so I'm assuming I'm missing something subtle.

hero.tagis[ClassFeature.fArdPsiAug] <> 0

Edit: Far as that goes, and I think I've asked this before, is there a generic way to tell in the editor what a given tag group is?
 
Last edited:
hero.tagis[ClassFeature.fArdPsiAug] <> 0
The issue here is that a Group.Tag has the same 10 character limitation that Unique ID's do. It has to do with the way the 10 characters are created into a unique pointer in HL. In other words "ClassFeature" is too long to be the name of a Tag Group.


Edit: Far as that goes, and I think I've asked this before, is there a generic way to tell in the editor what a given tag group is?
Not sure I follow the question. Tag Groups are defined in a .1st file that is one of the primary building blocks of HL system. In that .1st file you can define if a tag group is dynamic and can "grow" based on tags defined in .user files. Otherwise the specific "Tags" are defined in the .1st.

Hopefully that helps. Otherwise need more info... :)
 
Ah, then the problem is with the Group tag. I'd assumed it wasn't because the error message changed when I was fiddling with that.

And you actually answered my question, as I'd either never had my attention brought to, or had forgotten about "tags.1st".

Edit: However now that I've located the actual Tag Group ("ClassFeat") according to the list, I'm getting the error "Syntax error in pre-requisite rule script on line one -- group 'ClassFeat' not defined." When doing a search for valid objects to use in the expression, the category of Class Features comes up empty, though there are clearly a long list of them when I look manually (of course I don't know any way to tell if that's actually the group ID, but the tags.1st says it is).
 
Last edited:
To answer the question, in case anyone else runs into it, you can determine the actual tags with group if you have a character constructed, turn on "Enable Debug Tracing" under Diagnostics in the Tools menu, and then in the Develop menu its one of the "Floating Info Windows" available.
 
To answer the question, in case anyone else runs into it, you can determine the actual tags with group if you have a character constructed, turn on "Enable Debug Tracing" under Diagnostics in the Tools menu, and then in the Develop menu its one of the "Floating Info Windows" available.
Opps. I meant to come back and mention that and I got busy at work and totally forgot. :(

The debugging tools are VERY handy!
 
Back
Top