Results 1 to 4 of 4

Thread: "FatherAnc" and "GeneralWithAncKilled" condition do not work

  1. #1

    Default "FatherAnc" and "GeneralWithAncKilled" condition do not work

    From docudemons:
    Code:
    ---------------------------------------------------
    Identifier:              FatherAnc
    Trigger requirements:    character_record
    Parameters:              ancillary name
    Sample use:              FatherAnc holy_grail
    Description:             Test to see if character's father posses this ancillary
    Battle or Strat:         Strat
    Class:                   FATHER_ANC
    Implemented:             Yes
    Author:                  Grig
    ---------------------------------------------------
    Identifier:              GeneralWithAncKilled
    Trigger requirements:    character_record
    Parameters:              ancillary name
    Sample use:              GeneralWithAncKilled holy_grail
    Description:             Test to see if a general with specified ancillary was killed in the battle
    Battle or Strat:         Both
    Class:                   GENERAL_ANC_KILLED
    Implemented:             Yes
    Author:                  Grig
    I tested mostly the "FatherAnc" condition, but I see that "GeneralWithAncKilled" condition works in the same way. The event I used in most tests was the "FatherDiesNatural" which was triggered both by death of old age and via kill_character DET_NATURAL.
    Well, they do not work as described. They always returns false when I use an ancillary name and always true if I use ancillary type, regardless if this ancillary is relevant or not ("if "father" has this ancillary or any ancillary of this particular type or not).

    Is there anyone that has these conditions work in the way they are described in docudemons?

  2. #2
    Withwnar's Avatar Script To The Waist
    Join Date
    Oct 2008
    Location
    Earth
    Posts
    6,329

    Default Re: "FatherAnc" and "GeneralWithAncKilled" condition do not work

    I have it in my notes that GeneralWithAncKilled doesn't work. Somebody must have said it somewhere.

    TATW uses quite a few FatherAnc conditions and always with FatherDiesNatural but I can't confirm either way if it works. However, there's nothing in the way that they're coded to prevent ALL children from getting the anc even though they are supposed to be unique items. I don't recall any reports like "I have two Nenya rings" so might suggest that the condition doesn't work.

    Anyway, I just tried FatherAnc with a CharacterSelected EDA trigger: didn't work. I tried something similar in CS - in case it was an EDA issue only - and it didn't work there either. No log errors, just a silent fail.

    Kingdoms grand campaign, crusades and tuetonic all use FatherAnc 24 times. Surely these are all broken then.

    When you try TYPE it is probably an error (in the log too?) because there is no anc with such a NAME, and a condition that results in an error is treated as "true".

  3. #3
    Gigantus's Avatar I am not special - I am a limited edition.
    Patrician took an arrow to the knee spy of the council

    Join Date
    Aug 2006
    Location
    Goa - India
    Posts
    53,125
    Blog Entries
    35

    Default Re: "FatherAnc" and "GeneralWithAncKilled" condition do not work

    FatherAnc tests for the type, not the name - see here.

    Edit: never mind - just confirmed that a non-existing type fires true as well.
    Last edited by Gigantus; February 20, 2017 at 11:25 PM.










  4. #4
    Titus le Chmakus's Avatar Biarchus
    Join Date
    Aug 2014
    Location
    Skiing on the Spine of the World or hunting in Lurkwood
    Posts
    648

    Default Re: "FatherAnc" and "GeneralWithAncKilled" condition do not work

    GeneralWithAncKilled does not work, that is certain. Dunno for FatherAnc, never used it ...

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •