Separate the action from the timing
Aim automation can change the direction of a player’s view or select a target. Trigger automation concerns when an action is sent. A setup can show either behavior independently. A clip in which the camera does not visibly move can still contain an automated action, while camera motion alone cannot establish how the action was initiated.
A repeating macro plays a preset sequence. A condition-driven system chooses whether to send an action based on a current signal. ConsoleTuner’s Gtuner IV overview documents programmable scripts and recorded macros as different kinds of work. A listing should explain the difference if it claims the action depends on a changing game state.
Work through an illustrative event timeline
Imagine a 12-second local training recording. A game cue appears at seconds 2 and 9. One input log shows action events at seconds 2, 6 and 10. Another shows events at seconds 2 and 9. The first sequence has two extra events and misses the cue at second 9. The second aligns with both cues.
These timestamps are illustrative. A person could have reacted at seconds 2 and 9, or an overlay could have been aligned with the scene after recording. To label what happened, ask whether the footage is continuous and whether the log shows physical input, outgoing input or a game animation.
Check for a game-side explanation
A game can repeat a menu action while a button is held, or display an animation after a prior input. Try one ordinary tap and one hold in the game’s local controls screen to learn what is normal for that title. Check the publisher’s current policy for the relevant mode when interpreting claims about permitted third-party automation.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.