Wrong dialogue trigger? (extremely tiny bug)

I just noticed this; it really doesn't matter at all, but it does seem like a bug.

In "11_bs_glanfathan_reactives.conversation":

    </FlowChartNode>
    <FlowChartNode xsi:type="TalkNode">
      <NodeID>42</NodeID>
      <Comments />
      <PackageID>1</PackageID>
      <ContainerNodeID>-1</ContainerNodeID>
      <Links />
      <ClassExtender>
        <ExtendedProperties />
      </ClassExtender>
      <Conditionals>
        <Operator>And</Operator>
        <Components>
          <ExpressionComponent xsi:type="ConditionalCall">
            <Data>
              <FullName>Boolean IsPlayerBackground(Background)</FullName>
              <Parameters>
                <string>Scholar</string>
              </Parameters>
            </Data>
            <Not>false</Not>
            <Operator>Or</Operator>
          </ExpressionComponent>
          <ExpressionComponent xsi:type="ConditionalCall">
            <Data>
              <FullName>Boolean IsPlayerBackground(Background)</FullName>
              <Parameters>
                <string>Scientist</string>
              </Parameters>
            </Data>
            <Not>true</Not>
            <Operator>Or</Operator>
          </ExpressionComponent>
        </Components>
      </Conditionals>

 

And in the stringtable:

      <ID>42</ID>
      <DefaultText>"Many estramorwn come to study our mathematics."</DefaultText>

 

The line is currently unlocked by being a Scholar or by not being a Scientist. Thus, everybody except Scientists gets it and the Scholar line is completely superfluous; I would assume it's supposed to read
 

 

              <FullName>Boolean IsPlayerBackground(Background)</FullName>
              <Parameters>
                <string>Scientist</string>
              </Parameters>
            </Data>
            <Not>false</Not>

 

instead.

There are similar checks in "te_barks_all.conversation" and "db_barks_all.conversation", which are unlocked by being a Scholar, Philosopher, or not a Scientist; I can't check those barks easily, but logically, it's very likely a bug.

Edited May 24, 201510 yr by Bubbles