Search results

...possible values (e.g. for the proposed sample rule, you would not want to test separately for spells of levels 5, 6, 7, 8, etc.). To handle special relati ...object really needs to be handled via a field value, yet you still need to test that state within tag expressions. One option would be to maintain both the

..."Elven" from the "Language" group. Or a more complex tag expression could test whether a thing has the "Language.Elven" tag and also has either the "Race. ...ll Boolean logic (i.e. "and", "or", "xor", "not") and can even extract and test numeric values from tags, tag expressions can model extremely complex condi

...then block consists of two separate statements. The first statement is the test to be performed and uses the syntax "if (expr1 comparison expr2) then". The ...tion jumps to the line following the "endif" statement. If the conditional test fails, then execution jumps to the line following the "else" statement. An

...of developing your data files, there will be times where you want to fully test that everything is working the way you want. There will also be times when ...a files, you'll need to load those changes into HL so that you can use and test them. The obvious way to do this is to go to the "File" menu and select "Sw

...ded to the same container. Now we'll further assume that ThingA has a Live test that is currently failed. This means that ThingA is treated as not existing ...ootstrap is added normally. However, if the container does not satisfy the test, no bootstrap is added.

{{important}}When the bootstrap include a ContainerReq test, the tags are only assigned to the pick when ContainerReq tag expression is ...ntainerReq tests, the value assignment is applied when the final condition test is resolved for the pick.

...pty, no timing dependencies may be defined elsewhere that depend upon this test. Default: Empty. ...If omitted, all things are assumed to match and the container requirement test is applied to them all.

{{important}}This element is only applicable when the condition test is defined within a component. In all other cases, this element may not be

...without reporting individual errors. In such cases, you can have the rule test all picks and mark them as invalid, but suppress any actual message. Defaul {{important}}This element is only applicable when the condition test is defined within a component. In all other cases, this element may not be

|class="leftnormal"|[[#test|test]] ...ite is satisfied. If omitted, the pre-requisite is assumed to satisfy this test.

...pplied. Consequently, the first sort key represents the primary comparison test used, the second sort key is the secondary comparison, etc. The comparisons The "sortkey" element defines the particulars for an individual comparison test that will be employed when sorting. The complete list of attributes for thi

...with a specific pre-requisite test for the current pick, where the desired test is given by ''index''. The index is zero-based, so the values 0 through 4 s

...with a specific pre-requisite test for the current pick, where the desired test is given by ''index''. The index is zero-based, so the values 0 through 4 s

If the test occurs during the evaluation cycle, the test is applied against the current set of tags for the container. Consequently,

...with a specific pre-requisite test for the current pick, where the desired test is given by ''index''. The index is zero-based, so the values 0 through 4 s

...with a specific pre-requisite test for the current pick, where the desired test is given by ''index''. The index is zero-based, so the values 0 through 4 s

If the validation test is not satisfied, the message and summary for the rule are displayed within ...as its initial context. You are free to navigate through the hierarchy and test the state of anything that impacts the rule. However, a given EvalRule scri

...you want, provided only the object and the container are considered by the test. The requirement is always either satisfied or not satisfied. This is deter ...reason for the container as the initial context is that the pre-requisite test is defined on the thing. Consequently, the thing will know about itself and

...cter to put at the start of each error and then performs the tests. If any test fails, a suitable error message is appended to the message.

...after each new evaluation cycle. If the container fails the tag expression test, then the visual element is completely hidden. In addition, any Position sc ...able item by the user, the "live" state is checked. If the thing fails the test and ends up being non-live, the thing is completely omitted from the list o