In the October 20 player discussion, [[ ]] marks dialogue directed at Rex and commonly accompanies a Yes/No reply opportunity; << >> is described as general chatter. Watch for the actual on-screen response prompt. The replies do not establish that every bracketed line requires input or that a particular answer changes an ending.
On this page
Recognize the line before looking for a button
| Notation | Reported use | Your immediate check |
|---|---|---|
<< >> | General conversation or chatter | Continue following the mission objective unless a separate prompt appears |
[[ ]] | A line addressed to Rex, often with a reply opportunity | Look for the displayed Yes/No choice and its current input labels |
ToeSniffer245 links the square brackets to a Yes/No option. harishnzf describes the distinction as general chat versus speech addressed to Rex, and qualifies the response as usual rather than universal. Those explanations are kept as player reports.
Use the prompt that is actually displayed
- Read the speaker and line, then look for a response choice rather than treating punctuation itself as a button.
- Follow the input labels displayed for your current controller or keyboard mapping. This source does not verify a universal key binding.
- If no reply prompt appears, do not infer a broken control from brackets alone. Observe whether the dialogue and mission continue normally.
- If a visible prompt genuinely fails, retain the exact line, platform, input device and game version so the problem can be reproduced.
Being able to choose the displayed reply is the immediate task. It is separate from whether an answer has a later narrative consequence.
What these replies cannot tell you
The discussion supplies no verified romance route, alternate-ending condition, relationship score or list of irreversible answers. Do not restart a campaign on the assumption that a missed response blocks completion.
Use the character overview for identifying a speaker, and the control-style comparison for aircraft handling. Neither replaces the input label on a dialogue prompt.
Sources & limits
Community reports are attributed, not tests performed by this site. Builds are unspecified unless stated.
- Reddit: Fawfulster’s dialogue-mark question ↗
Original and two visible replies read October 20; exact client build unspecified.
- Reddit: ToeSniffer245 on the Yes/No option ↗
Player explanation, not a complete dialogue or consequence database.
- Reddit: harishnzf on speech directed at Rex ↗
Says such dialogue usually requires a reply; not every line is asserted to demand input.