• Errors

    TOC

    Parsing Errors

    Example Trace:

    Parsing Error:
  "examples/Hamlet.cuesheet" (line 5, column 1):
  unexpected "D"
  expecting "  " or lf new-line

    Possible Causes:

    This likely means you forgot a newline somewhere or forgot to give the block the right amount of indentation.

    Possible Fixes:

    Make sure there is a newline after every unit block. Look at the example to see where newlines and indentions appear.

    NoMatchError

    Example Trace:

    Processing Error:
  [NoMatchError] The following marker could not be placed:

    (line) @BARNARDO:"I never say this..."

  Perhaps you spelled something incorrectly or have used the wrong index.

    Possible Causes:

    The cue group you specified did not have any matching line in the script. Perhaps the character you specified never says those words or makes the entrance/exit. A more likely alternative, is that you've mistyped a word in the quoted line.

    Possible Fixes:

    • Double check the character says/does what you think they do in the script.
    • Check that all words are spelled correctly and are exactly one line.

    AmbiguousError

    Example Trace:

    Processing Error:
  [AmbiguousError] The following marker has too many possible options:

    PromptMarker {pMarker = (line) @BARNARDO:"h", pCues = [#LX {1} STBY "t",#SD {1} GO "comment 2",#BS {1} WARN]}

  Here are all the possible matches:

    PromptMarker {pMarker = (line) @BARNARDO:"Who's there?", pCues = []}
    .
    .
    .
    PromptMarker {pMarker = (line) @BARNARDO:"It was about to speak when the cock crew.", pCues = []}


  Please disambiguate the placement by providing an index or specifying more of a line:
        (visual) @CECIL:ENTR (99)
     OR
        (line) @CECIL:"more words here"

    Possible Causes:

    A cue group has many matches within a scene. > Prompt will give this error if there is more than one possible placement within a scene of the specified cue. It will enumerate ALL possible placements so you may pick one.

    Possible Fixes:

    Add more context to disambiguate the placement by either providing more words from the line or adding a parenthesised index after the cue group.

    DuplicateCharacterDeclaration

    Example Trace:

    Compiling Error:
  [DuplicateCharacterDeclaration] The following character is defined twice:

    @BARNARDO

  Delete the extra occurences in your 'Characters' declaration block.

    Possible Causes:

    You declared a character more the once:

    Characters:
  @HAMLET
  @POLONIUS
  @HAMLET

    Possible Fixes:

    Delete any duplicate occurences.

    DuplicateDepartmentDeclaration

    Example Trace:

    Compiling Error:
  [DuplicateDepartmentDeclaration] The following character is defined twice:

    #LX

  Delete the extra occurences in your 'Departments' declaration block.

    Possible Causes:

    Similar to above, except with departments:

    Departments:
  #LX
  #SD
  #LX

    Possible Fixes:

    Delete any duplicate occurences.

    UndeclaredCharacterError

    Example Trace:

    Compiling Error:
  [UndeclaredCharacterError] The following character was referenced in a cue, but not defined:

    @HAMLET

  Perhaps it is a typo? If not, please declare the character in the 'Characters' block.

    Possible Causes:

    You tried to refer to a character that you forgot to declare or you made a typo when specifying their name.

    Possible Fixes:

    Add the character to the declaration list:

    Characters:
  @POLONIUS
  @HAMLET

    or check for a typo!

    UndeclaredDepartmentError

    Example Trace:

    Compiling Error:
  [UndeclaredDepartmentError] The following department was referenced in a cue, but not defined:

    #TYPO

  Perhaps it is a typo? If not, please declare the department in the 'Departments' block.

    Possible Causes:

    Analogous to above.

    Possible Fixes:

    Analogous to above.

    UnkownTargetCharacterError

    Example Trace:

    Compiling Error:
  [UnkownTargetCharacterError] The following character was referenced in a the cuesheet,
                               but does not appear in the target script:

    @NONEXISTENT

  Perhaps it is a typo? If so, please change the character declaration and all references.

    Possible Causes:

    You correctly declared a character and used it in the cue sheet, but the character doesn't exist in the destination script.

    Possible Fixes:

    Check the spelling and look at the character list of the destination script. Use the names as declared in the destination script.

    OutOfOrderOrDuplicateActError

    Example Trace:

    Compiling Error:
  [OutOfOrderOrDuplicateActError] The following act was declared out of order or twice:

    Act 1

  Please check the numbering.

    Possible Causes:

    The Act 1 declaration came after Act 2 or another later act. Or you declared Act 1 twice.

    Possible Fixes:

    If you have duplicated occurrences, simply merge the two together. Otherwise, reorder so that acts appear in numerical ascending order.

    OutOfOrderOrDuplicateSceneError

    Example Trace:

    Compiling Error:
  [OutOfOrderOrDuplicateSceneError] The following scene was declared out of order or twice:

    Scene 1

  Please check the numbering.

    Possible Causes:

    Analogous to above.

    Possible Fixes:

    Analagous to above.

    What the @%^!?
    Next: Introduction