Continuing to write the XML for our new example attribute, hogtied, we need to define to WACS how and when it should be used. So we need to add more fields to our XML entry:

  <atgroup>objects</atgroup>
  <atvalidset>Y</atvalidset>
  <atvalidmodel>N</atvalidmodel>
  <atvalidother>N</atvalidother>
  <atmarkset>Y</atmarkset>
  <atmarkmodel>N</atmarkmodel>
  <atmarkother>N</atmarkother>
  <atsetsearch>Y</atsetsearch>
  <atmodsearch>N</atmodsearch>
  <atcombsearch>N</atcombsearch>
  <atothsearch>N</atothsearch>
 </entry501>

So the first three values: atvalidset, atvalidmodel and atvalidother control what types of entity these can be applied to. Certain attributes like tattooing, shaven pussies and flat chestedness can apply equally to both sets and to the models. Things like toys and surroundings are really only applicable to sets. In this case, hogtied applies to the set exclusively and so only atvalidset is set to Y and the rest set to No. The meaning of "other" is yet to be defined so the default for now is No for that.

The next set of three control what this type can be marked on - thus if atmarkset is Y then wacssetmgr will offer it as a markable attribute for sets. If atmarkmodel is Y then wacsmodelmgr will offer it as a markable attribute for models. In this case, it's exclusively a set attribute and so only atmarkset is set to Y.

The final four control how you may search for it - they are respectively as a set attribute, a model attribute, as an attribute on a combined search that covers sets and models together and as an "other" attribute. The decision on the combined attribute is up to you - generally the combined screen rapidly becomes cluttered and it's best to only include those criteria for sets that will match a large proportion of the sets in the collection. If say a quarter of the sets featured hogtied models, then you might want to set this so that users could select just hogtied redheads. Otherwise you probably don't want to.

There is a similar set of four values for "detailed" searches which may well be supported in a future release of wacs - they are the corresponding atsetdetail, atmoddetail, atcombdetail and atothdetail. It's probably as well to set these too.