So, if I trigger an Action or play a card other players act first i. e. they trigger their Disrupt first, and then trigger they're Response first.
But when something other than above causes an Disrupt/Responce opportunity it's active player who goes first.
Thats how it works?
I believe that's right, and when put that way, it makes vastly more sense than the FAQ, which at this point may be in dire need of a TL;DR.
I myself did not understand the subtle distinction between "player action" and "action" until a few months ago. And it always seeks to elude my understanding. Take this passage for example:
Action, Disrupt, and Response Effects
Throughout the course of the game’s
action windows, players alternate
taking player actions. Player actions
consist of playing a card from hand, or
of triggering a triggered effect on a card
already in play.
This definition of Player Action is probably too limited, since it doesn't include the possibility of triggered effects on cards in out-of-play areas, such as Dirk Sharpe or The Cats of Ulthar. What would that be defined as if not a Player Action? Or perhaps this falls under the definition of "play" (which I don't think does, since play seems to always have meant playing a card in operations paying normal costs.) The fact that this definition for Player Actions is listed under "Action, Disrupt, and Response Effects" is also rather misleading, since Disrupts and Responses are not exactly Player Actions, but are rather "Player triggered effects" played (also a dangerous word with implicit meaning) to disrupt/respond to either "Player actions," "Framework Actions," or "Framework Game Events." (God, this is ugly…)
How's this to aid clarity?
Action: a general term that includes Player actions and Framework actions
Player action: includes playing a card in the operations phase, triggering a player-triggered ability, and triggering an "Action:" triggered effects
Framework actions: actions that are dictated by the game, such as all starts of phases, drawing cards in the draw phase or committing characters to stories (note: many of the framework actions are optional, including restoring 1 character, resourcing 1 card, or committing characters to stories)
Framework game event: effects that are triggered by a framework action, such as the effect of an icon struggle or the process of a character committing (this one is a little slippery since it's only used once…)
Play: to play a card from your hand during the operations phase by paying costs as normal; (alternatively, could mean to trigger an Action: from an out-of-play state as well…)
We could create definitions for terms like "Committing," "Committed," "Made insane," "Drive insane," "Go insane," etc.
Is anything off there? It would really be helpful for FFG to clean up the FAQ a little to remove some of the guesswork caused by redundancies and discrepancies.