Can't get why CanCondition ignores

[Weer36 3]

<EasyQuest>
      <Name>easy</Name>
      <QuestType>KillAndLoot</QuestType>
      <QuestClass xsi:type="KillAndLootEasyQuestClass">
        <HotSpots>
          ...
        </HotSpots>
        <EntryTarget />
        <IsGrinderNotQuest>false</IsGrinderNotQuest>
        <IsHotspots>true</IsHotspots>
      </QuestClass>
      <CanCondition>return true;</CanCondition>
      <IsCompleteCondition>return false;</IsCompleteCondition>
      <RepeatableQuest>false</RepeatableQuest>
      <NotRequiredInQuestLog>false</NotRequiredInQuestLog>
      <PickUpQuestOnItem>false</PickUpQuestOnItem>
      <PickUpQuestOnItemID>0</PickUpQuestOnItemID>
      <GossipOptionRewardItem>1</GossipOptionRewardItem>
      <RequiredQuest>0</RequiredQuest>
      <MaxLevel>100</MaxLevel>
      <MinLevel>0</MinLevel>
      <WoWClass>None</WoWClass>
</EasyQuest>

 

I'd read about NotRequiredInQuestLog: when you use "NotRequiredInQuestLog" WRobot ignore "CanCondition"

Why EasyQuest don't start in   <QuestsSorted Action="Pulse" NameClass="easy" /> ?

[Droidz 2738]

Hello,

If you are using an old version of the bot try to put a quest id (even fake).

[Weer36 3]

Tryed, but can't see that bot checks CanCondition: tested it with <CanCondition>Logging.WriteDebug("123"); return true;</CanCondition>

[Droidz 2738]

Sorry,

"CanCondition" is called only when bot run "PickUp" step.

Use IsCompleteCondition 

[Weer36 3]

Thats way works fine, just tried to understand how it should works correctly. Thanks.