Description
Flag an alias shared by distinct supplied character IDs.
Writing records can represent speakers, scenes, aliases, rhyme labels and revision spans. These representations preserve selected conventions: a character count needs an indexing unit, an alias can be active over an inclusive period, and a stage-direction wrapper is a string pattern rather than a grammar. Mechanical labels do not evaluate literary quality or establish authorship.
Flag an alias shared by distinct supplied character IDs.
When to use this tool
Use Character Alias Collision Pair when you already have firstCharacterId, firstAlias, secondCharacterId, secondAlias, caseSensitive and need to flag an alias shared by distinct supplied character IDs.
How to use the tool and how it works
- Enter firstCharacterId, firstAlias, secondCharacterId, secondAlias, caseSensitive. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read collision, sameCharacter. Inspect collision, sameCharacter before interpreting the associated values.
Require character IDs nonempty; compare aliases literally or after JavaScript lowercasing. collision requires distinct character IDs and equal comparison aliases; also report sameCharacter.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstCharacterId | First Character Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| firstAlias | First Alias | Required. Text; maximum UTF-16 length 8192. |
| secondCharacterId | Second Character Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| secondAlias | Second Alias | Required. Text; maximum UTF-16 length 8192. |
| caseSensitive | Case Sensitive | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| collision | Equal aliases under the selected literal/lowercase comparison, but only for distinct character IDs. | Required. Boolean. |
| sameCharacter | Same Character | Required. Boolean. |
{
"input": {
"firstCharacterId": "C1",
"firstAlias": "River",
"secondCharacterId": "C2",
"secondAlias": "river",
"caseSensitive": false
},
"output": {
"collision": true,
"sameCharacter": false
}
}Limitations and assumptions
- Empty aliases are accepted and not trimmed. Same-character pairs never collide; no Unicode normalization, character identity or narrative ambiguity is established.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Inspect the full passage, draft history and editorial style when interpreting the result. Use complete text or narrative analysis for meaning and structure; local markers, offsets and supplied attribution records only organize the stated information.
References
Similar or alternative tools
- Character Alias Period Validity
Check a scene index against a supplied inclusive alias period.
- Dialogue Speaker Label Normalizer
Normalize a dialogue speaker label's spacing and capitalization.