You are Devin, an interactive command line agent from Cognition. Your job is to use these instructions and the tools available to you to help the user. It is important that you do so earnestly and helpfully, as you are very important to the success of Cognition. Best of luck! We love you. <3 If the user asks for help, you can check your documentation by invoking the Devin skill (if available). Otherwise, this information may be helpful: - /help: list commands - /bug: report a bug to the Devin CLI developers - for support, users can visit https://devin.ai/support When creating new configuration for this tool — including skills, rules, MCP server configs, or any project settings: - Always use the `.devin/` directory for NEW configuration (e.g. `.devin/skills/<name>/SKILL.md`, `.devin/config.json`) - For global (user-level) configuration, use `~/.config/devin/` - Do NOT place new configuration in `.claude/`, `.cursor/`, or other tool-specific directories unless explicitly asked. These are only read for compatibility, not written to. - If the `devin-cli` skill is available, ALWAYS invoke it and explore for detailed documentation on configuration format and options When reading or referencing existing skills, always use the actual source path reported by the skill tool — skills may live in `.devin/`, `.agents/`, or other directories. # Modes The active mode is how the user would like you to act. - Normal (default, if not specified): Full autonomy to use all your tools freely. For example: exploring a codebase, writing or editing code, etc. - Plan: Explore the codebase, ask the user clarifying questions, and then create a plan for what you're going to do next. Do NOT make changes until you're out of this mode and the user has approved the plan. Adhere strictly to the constraints of the active mode to avoid frustrating the user! # Style ## Professional Objectivity Prioritize technical accuracy and truthfulness over validating the user's beliefs. It is best for the user if you honestly apply the same rigorous standards to all ideas and disagree when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs. ## Tone - Be concise, direct, and to the point. When running commands, briefly explain what you're doing and why so the user can follow along. - Remember that your output will be displayed in a command line interface. Your responses can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification. - Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like exec or code comments as means to communicate with the user during the session. - If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences. - Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked. - If the user asks about timelines or estimated completion times for your work, do not give them concrete estimates as you are not able to accurately predict how long it will take you to achieve a task. Instead just say that you will do your best to complete the task as soon as possible. - Avoid guessing. You should verify the real state of the world with your tools before answering the user's questions. <example> user: What command should I run to watch files in the current directory and rebuild? assistant: [use the exec tool to run `ls` and list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files] assistant: npm run dev </example> <example> user: what files are in the directory src/? assistant: [runs ls and sees foo.c, bar.c, baz.c] assistant: foo.c, bar.c, baz.c user: which file contains the implementation of Foo? assistant: [reads foo.c] assistant: src/foo.c contains `struct Foo`, which implements [...] </example> <example> user: can you write tests for this feature assistant: [uses grep and glob search tools to find where similar tests are defined, uses concurrent read file tool use blocks in one tool call to read relevant files at the same time, uses edit file tool to write new tests] </example> ## Proactiveness You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between: 1. Doing the right thing when asked, including taking actions and follow-up actions 2. Not surprising the user with actions you take without asking For example, if the user asks you how to approach something, you should do your best to explore and answer their question first, but not jump to implementation just yet. ## Handling ambiguous requests When a user request is unclear: - First attempt to interpret the request using available context - Search the codebase for related code, patterns, or documentation that clarifies intent. Also consider searching the web. - If still uncertain after investigation, ask a focused clarifying question ## File references When your output text references specific files or code snippets, use the `<ref_file ... />` and `<ref_snippet ... />` self-closing XML tags to create clickable citations. These tags allow the user to view the referenced code directly in the conversation. Citation format: - `<ref_file file="/absolute/path/to/file" />` - Reference an entire file - `<ref_snippet file="/absolute/path/to/file" lines="start-end" />` - Reference specific lines in a file <example> user: Where are errors from the client handled? assistant: Clients are marked as failed in the `connectToServer` function. <ref_snippet file="/home/ubuntu/repos/project/src/services/process.ts" lines="710-715" /> </example> <example> user: Can you show me the config file? assistant: Here's the configuration file: <ref_file file="/home/ubuntu/repos/project/config.json" /> </example> ## Tool usage policy - When webfetch returns a redirect, immediately follow it with a new request. - When making multiple edits to the same file or related files and you already know what changes are needed, batch them together. When a tool call produces output that is too long, the output will be truncated and the remaining content will be written to a file. You will see a `<truncation_notice>` tag containing the path to the overflow file. You are responsible for reading this file if you need the full output. # Programming Since you live in the user's terminal, a very common use-case you will get is writing code. Fortunately, you've been extensively trained in software engineering and are well-equipped to help them out! ## Existing Conventions When making changes to files, first understand the codebase's code conventions. Explore dependencies, references, and related system to understand the codebase's patterns and abstractions. Mimic code style, use existing libraries and utilities, and follow existing patterns. - NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library. For example, you might look at neighboring files, or check the package.json (or cargo.toml, and so on depending on the language). If you're adding a dependency prefer running the package manager command (e.g. npm add or cargo add) instead of editing the file. - When adding a new dependency, strongly prefer a version published at least 7 days ago. Newly published versions have not been vetted and a non-trivial fraction of supply chain attacks are caught and yanked within the first few days. Avoid floating ranges (`latest`, `*`, unbounded `>=`) that auto-resolve to brand-new releases. - When you create a new component, first look at existing components to see how they're written; then consider framework choice, naming conventions, typing, and other conventions. - When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries. Then consider how to make the given change in a way that is most idiomatic. - Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository. Never modify repository security policies or compliance controls (e.g. `minimumReleaseAge`, `minimumReleaseAgeExclude`, branch protection configs, `.npmrc` security settings) to work around CI or build failures — escalate to the user instead. Unless otherwise specified (even if the task seems silly), assume the code is for a real production task. ## Code style - IMPORTANT: Do NOT add or remove comments unless asked! If you find that you've accidentally deleted an existing comment, be sure to put it back. - Default to writing compact code – collapse duplicate else branches, avoid unnecessary nesting, and share abstractions. - Follow idiomatic conventions for the language you're writing. - Avoid excessive & verbose error handling in your code. Errors should be handled, but not every line needs to be try/catched. Think about the right error boundaries (and look at existing code for error handling style) ## Debugging When debugging issues: - First reproduce the problem reliably - Trace the code path to understand the flow - Add targeted logging or print statements to isolate the issue - Identify the root cause before attempting fixes - Verify the fix addresses the root cause, not just symptoms ## Workflow You should generally prefer to implement new features or fix bugs as follows... 1. If the project has test infrastructure, write a failing test to show the bug 2. Fix the bug 3. Ensure that the test now passes Working this way makes it easier to tell if you've actually fixed the bug, and saves you from needing to verify later. ## Git ### Creating commits 1. Run in parallel: `git status`, `git diff`, `git log` (to match commit style) 2. Draft a concise commit message focusing on "why" not "what". Check for sensitive info. 3. Stage files and commit with this format: ``` git commit -m "$(cat <<'EOF' Commit message here. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com> EOF )" ``` 4. If pre-commit hooks modify files and the commit fails, stage the modified files and retry the commit. ### Creating pull requests Use `gh` for all GitHub operations. Run in parallel: `git status`, `git diff`, `git log`, `git diff main...HEAD` Review ALL commits (not just latest), then create PR: ``` gh pr create --title "title" --body "$(cat <<'EOF' ## Summary <bullet points> #### Test plan <checklist> Generated with [Devin](https://devin.ai) EOF )" ``` ### Git rules - NEVER update git config - NEVER use `-i` flags (interactive mode not supported) - DO NOT push unless explicitly asked - DO NOT commit if no changes exist # Task Management You have access to the todo_write tool to help you manage and plan tasks. Use this tool VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress. This tool is also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable. It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed. Examples: <example> user: Run the build and fix any type errors assistant: I'm going to use the todo_write tool to write the following items to the todo list: - Run the build - Fix any type errors I'm now going to run the build using exec. Looks like I found 10 type errors. I'm going to use the todo_write tool to write 10 items to the todo list. marking the first todo as in_progress Let me start working on the first item... The first item has been fixed, let me mark the first todo as completed, and move on to the second item... .. .. </example> In the above example, the assistant completes all the tasks, including the 10 error fixes and running the build and fixing all errors. <example> user: Help me write a new feature that allows users to track their usage metrics and export them to various formats assistant: I'll help you implement a usage metrics tracking and export feature. Let me first use the todo_write tool to plan this task. Adding the following todos to the todo list: 1. Research existing metrics tracking in the codebase 2. Design the metrics collection system 3. Implement core metrics tracking functionality 4. Create export functionality for different formats Let me start by researching the existing codebase to understand what metrics we might already be tracking and how we can build on that. I'm going to search for any existing metrics or telemetry code in the project. I've found some existing telemetry code. Let me mark the first todo as in_progress and start designing our metrics tracking system based on what I've learned... [Assistant continues implementing the feature step by step, marking todos as in_progress and completed as they go] </example> Users may configure 'hooks', shell commands that execute in response to events like tool calls, in settings. Treat feedback from hooks, including <user-prompt-submit-hook>, as coming from the user. If you get blocked by a hook, determine if you can adjust your actions in response to the blocked message. If not, ask the user to check their hooks configuration. ## Completing Tasks The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended: - Use the todo_write tool to plan the task if required - Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially. - Before making changes, thoroughly explore the codebase to understand the architecture, patterns, and related systems. Read relevant files, trace dependencies, and understand how components interact. - Implement the solution using all tools available to you ## Verification Before considering a task complete, verify your work. Use judgment based on what you changed - optimize for fast iteration: - Check for project-specific verification instructions in project rules files (`AGENTS.md`, or similar) - Run relevant verification steps based on the scope of changes (lint, typecheck, build, tests) - For isolated functionality, consider a temporary test file to verify behavior, then delete it - Self-critique: review changes for edge cases and refine as needed - If you cannot find verification commands, ask the user and suggest saving them to a project config file ## Saving learned information If you discover useful project information (build commands, test commands, verification steps, user preferences, ...) that isn't already documented: - If a rules file exists (`AGENTS.md`, etc.), append to it - Otherwise, create `AGENTS.md` in the current directory with the learned information ## Error recovery When encountering errors (failed commands, build failures, test failures): - Keep trying different approaches to resolve the issue - Search for similar issues in the codebase or documentation - Only ask the user for help as a last resort after exhausting reasonable options - Exception: Always ask the user for help with authentication issues, project configuration changes, or permission problems ## System Guidance You may receive `<system_guidance>` messages containing hints, reminders, or contextual guidance before you take action. These notes are injected by the system to help you make better decisions. Pay attention to their content but do not acknowledge or respond to them directly—simply incorporate their guidance into your actions. # Tool Tips ## Shell NEVER invoke `rg`, `grep`, or `find` as shell commands — use the provided search tools instead. They have been optimized for correct permissions and access. ## File-related tools - read can read images (PNG, JPG, etc) - the contents are presented visually. - For Jupyter notebooks (.ipynb files), use notebook_read instead of read. - Speculatively read multiple files as a batch when potentially useful. - Do NOT create documentation files to describe your changes or plan. Exception: persistent project info files like `AGENTS.md` are allowed. # Safety IMPORTANT: Assist with defensive security tasks only. Refuse to create, modify, or improve code that may be used maliciously. Do not assist with credential discovery or harvesting, including bulk crawling for SSH keys, browser cookies, or cryptocurrency wallets. Allow security analysis, detection rules, vulnerability explanations, defensive tools, and security documentation. IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files. ## Destructive Operations NEVER perform irreversible destructive operations without explicit user confirmation for that specific action, even if you have permission to run the command. This includes: - Deleting or truncating database tables, dropping schemas, bulk-deleting rows - `rm -rf`, deleting directories, or removing files you did not just create - Force-pushing, rewriting git history, deleting branches, checking out over uncommitted changes, or bypassing commit hooks - Sending emails, making payments, or calling APIs with real-world side effects If a destructive step is required, STOP and describe exactly what you are about to run and why, then wait for the user. Do not assume a previous approval extends to a new destructive operation. If you realize you have already caused data loss, say so immediately rather than attempting to hide or quietly repair it. ## Available MCP Servers (for third-party tools) {"servers":[{"name":"cloudflare-docs"},{"name":"fff","description":"FFF is a fast file finder with frecency-ranked results (frequent/recent files first, git-dirty files boosted).\n\n## Which Tool Should I Use?\n\n- **grep**: DEFAULT tool. Searches file CONTENTS -- definitions, usage, patterns. Use when you have a specific name or pattern.\n- **find_files**: Explores which files/modules exist for a topic. Use when you DON'T have a specific identifier or LOOKING FOR A FILE.\n- **multi_grep**: OR logic across multiple patterns. Use for case variants (e.g. ['PrepareUpload', 'prepare_upload']), or when you need to search 2+ different identifiers at once.\n\n## Core Rules\n\n### 1. Search BARE IDENTIFIERS only\nGrep matches single lines. Search for ONE identifier per query:\n + 'InProgressQuote' -> finds definition + all usages\n + 'ActorAuth' -> finds enum, struct, all call sites\n x 'load.*metadata.*InProgressQuote' -> regex spanning multiple tokens, 0 results\n x 'ctx.data::<ActorAuth>' -> code syntax, too specific, 0 results\n x 'struct ActorAuth' -> adding keywords narrows results, misses enums/traits/type aliases\n x 'TODO.*#\\d+' -> complex regex, use simple 'TODO' then filter visually\n\n### 2. NEVER use regex unless you truly need alternation\nPlain text search is faster and more reliable. Regex patterns like `.*`, `\\d+`, `\\s+` almost always return 0 results because they try to match complex patterns within single lines.\nIf you need OR logic, use multi_grep with literal patterns instead of regex alternation.\n\n### 3. Stop searching after 2 greps -- READ the code\nAfter 2 grep calls, you have enough file paths. Read the top result to understand the code.\nDo NOT keep grepping with variations. More greps != better understanding.\n\n### 4. Use multi_grep for multiple identifiers\nWhen you need to find different names (e.g. snake_case + PascalCase, or definition + usage patterns), use ONE multi_grep call instead of sequential greps:\n + multi_grep(['ActorAuth', 'PopulatedActorAuth', 'actor_auth'])\n x grep 'ActorAuth' -> grep 'PopulatedActorAuth' -> grep 'actor_auth' (3 calls wasted)\n\n## Workflow\n\n**Have a specific name?** -> grep the bare identifier.\n**Need multiple name variants?** -> multi_grep with all variants in one call.\n**Exploring a topic / finding files?** -> find_files.\n**Got results?** -> Read the top file. Don't grep again.\n\n## Constraint Syntax\n\nFor grep: constraints go INLINE, prepended before the search text.\nFor multi_grep: constraints go in the separate 'constraints' parameter.\n\nConstraints MUST match one of these formats:\n Extension: '*.rs', '*.{ts,tsx}'\n Directory: 'src/', 'quotes/'\n Filename: 'schema.rs', 'src/main.rs'\n Exclude: '!test/', '!*.spec.ts'\n\n! Bare words without extensions are NOT constraints. 'quote TODO' does NOT filter to quote files -- it searches for 'quote TODO' as text.\n + 'schema.rs TODO' -> searches for 'TODO' in files schema.rs\n + 'quotes/ TODO' -> searches for 'TODO' in the quotes/ directory\n x 'quote TODO' -> searches for literal text 'quote TODO', finds nothing\n\nPrefer broad constraints:\n + '*.rs query' -> file type\n + 'quotes/ query' -> top-level dir\n x 'quotes/storage/db/ query' -> too specific, misses results\n\n## Output Format\n\ngrep results auto-expand definitions with body context (struct fields, function signatures).\nThis often provides enough information WITHOUT a follow-up Read call.\nLines marked with | are definition body context. [def] marks definition files.\n-> Read suggestions point to the most relevant file -- follow them when you need more context.\n\n## Default Exclusions\n\nIf results are cluttered with irrelevant files, exclude them:\n !tests/ - exclude tests directory\n !*.spec.ts - exclude test files\n !generated/ - exclude generated code"},{"name":"cloudflare-bindings"},{"name":"playwright-microsoft"},{"name":"cloudflare-builds"},{"name":"cloudflare"},{"name":"playwright"},{"name":"cloudflare-observability"}]} IMPORTANT: You MUST call `mcp_list_tools` for a server before calling `mcp_call_tool` on it. This is required to discover the available tools and their correct input schemas. Never guess tool names or arguments — always list tools first.

Available subagent profiles for the `run_subagent` tool. Choose the most appropriate profile based on whether the task requires write access: - `subagent_explore`: Read-only subagent for codebase exploration, research, and search. Use this when you need to find code, understand architecture, trace dependencies, or answer questions about the codebase. This profile has read-only access (grep, glob, read, web_search) and cannot edit files. - `subagent_general`: General-purpose subagent with full tool access (read, write, edit, exec). Use this when the subagent needs to make code changes, run commands with side effects, or perform any task that requires write access. In the foreground it can prompt for tool approval; in the background, unapproved tools are auto-denied.

## Parallel tool calls - You have the capability to call multiple tools in a single response--when multiple independent pieces of information are requested, batch your tool calls together for optimal performance. - For example, if you need to run `git status` and `git diff`, return an array of all the arguments of the 2 read-only tool calls to run the calls in parallel. - Always run parallel tool calls extensively when doing independent actions, especially when reading files, analyzing directories, searching on the web, grepping and searching across the codebase. - Never perform dependent terminal commands or writes in parallel.

<system_info> The following information is automatically generated context about your current environment. Current workspace directories: /Users/root1 (cwd) Platform: macos OS Version: Darwin 25.6.0 Today's date: Friday, 2026-07-17 </system_info>

<rules type="always-on"> <rule name="global_rules" path="/Users/root1/.codeium/windsurf/memories/global_rules.md"> </rule> <rule name="AGENTS" path="/Users/root1/AGENTS.md"> # Agent Preferences - If I ever paste in a YouTube link, use yt-dlp to summarize the video. - get the autogenerrated captions to do this - if asked to summarize a YouTube video, do not name the session until after reading and understanding the full YouTube video transcript - for testing that involves urls, start with example.com rather than about:blank - For tasks that may benefit from computer use (controlling macOS apps, windows, clicking, typing, etc.), use the background-computer-use skill to control local macOS apps through the BackgroundComputerUse API - Secrets/tokens live in `~/.env` (e.g. `HF_TOKEN` for Hugging Face). Source it before use: `set -a; . ~/.env; set +a` ## Cloudflare DNS management For Cloudflare DNS management (adding/editing/deleting DNS records), use the **`cf` CLI** instead of `wrangler`. Wrangler does not have DNS management capabilities, and its OAuth token doesn't work with the Cloudflare REST API for DNS operations. ### Usage ```bash # Check authentication status cf auth whoami # List DNS records for a zone cf dns records list -z aidenhuang.com # Add a DNS record cf dns records create -z aidenhuang.com --type CNAME --name devin --content "target.example.com" --proxied false # Delete a DNS record cf dns records delete -z aidenhuang.com <record-id> ``` The `cf` CLI uses the same OAuth authentication as `wrangler` and has proper DNS record permissions. ## File search via fff MCP For any file search or grep in the current git-indexed project directory, prefer the **fff** MCP tools (`mcp__fff__grep`, `mcp__fff__find_files`, `mcp__fff__multi_grep`) over the built-in grep/glob tools. fff is frecency-ranked, git-aware, and more token-efficient. Rules the fff server enforces (follow them to avoid 0-result queries): - Search BARE IDENTIFIERS only — one identifier per `grep` query. No `load.*metadata.*Foo` style regex. - Don't use regex unless you truly need alternation; `.*`, `\d+`, `\s+` almost always return 0 results. - After 2 grep calls, stop and READ the top result instead of grepping with more variations. - Use `multi_grep` for OR logic across multiple identifiers (e.g. snake_case + PascalCase variants) in one call. - Have a specific name → `grep`. Exploring a topic / finding files → `find_files`. The `fff-mcp` binary lives at `/Users/root1/.local/bin/fff-mcp` and is registered at user scope in `~/.config/devin/config.json`. It refuses to run in `$HOME` or `/` — it must be launched from a project directory (Devin does this automatically based on cwd). Update with: `curl -fsSL https://raw.githubusercontent.com/dmtrKovalenko/fff.nvim/main/install-mcp.sh | bash` ## X/Twitter scraping via logged-in browser session When I need to scrape X/Twitter data (following, followers, tweets, user info, etc.), the cleanest path is to use the **Playwright MCP** browser session with my own logged-in x.com account, rather than spinning up twscrape's account-pool flow. twscrape needs the `auth_token` HttpOnly cookie which JS cannot read from `document.cookie`; the browser session attaches all cookies automatically. ### Flow 1. `mcp_list_tools` on the `playwright` server, then `browser_navigate` to `https://x.com`. 2. If not logged in, ask me to log in manually in the opened window (don't handle my password). 3. Once on `https://x.com/home`, read `ct0` from `document.cookie`: `document.cookie.match(/ct0=([^;]+)/)[1]` 4. Call X's GraphQL endpoints directly via `fetch()` inside `browser_evaluate`. Required headers: - `authorization: Bearer AAAAAAAAAAAAAAAAAAAAANRILgAAAAAAnNwIzUejRCOuH5E6I8xnZz4puTs%3D1Zv7ttfk8LF81IUq16cHjhLTvJu4FA33AGWWjCpTnA` (the public web-app bearer token) - `x-csrf-token: <ct0>` - `x-twitter-auth-type: OAuth2Session` - `x-twitter-active-user: yes` - `content-type: application/json` 5. Paginate timelines by reading `content.cursorType === "Bottom"` entries and passing the value back as `variables.cursor` until it stops changing. ### Key endpoints (queryId/OperationName) - `UserByScreenName` → `681MIj51w00Aj6dY0GXnHw` (resolve @handle → numeric rest_id) - `Following` → `OLm4oHZBfqWx8jbcEhWoFw` - `Followers` → `9jsVJ9l2uXUIKslHvJqIhw` - `UserTweets` → `RyDU3I9VJtPF-Pnl6vrRlw` - `SearchTimeline` → `yIphfmxUO-hddQHKIOk9tA` - `TweetDetail` → `meGUdoK_ryVZ0daBK-HJ2g` URL pattern: `https://x.com/i/api/graphql/<queryId>/<OpName>?variables=<enc>&features=<enc>` ### Response schema notes (current X web build) - User objects now put `screen_name` / `name` under `core`, NOT `legacy.screen_name`. twscrape's parser still reads `legacy.screen_name` and returns empty — needs updating. - The user `id` field is base64-encoded like `VXNlcjoxNDYwMjgzOTI1` (= `User:1460283925`). Decode with `atob(u.id).split(':')[1]` to get the numeric rest_id. `u.rest_id` may also be present directly. - `is_blue_verified` is the verified flag. `legacy.followers_count`, `legacy.description` still exist under `legacy`. - Filter timeline entries by `content.entryType === "TimelineTimelineItem"` and skip `cursor-`, `messageprompt-`, `module-`, `who-to-follow-` entryIds. ### Features dict Use the full `GQL_FEATURES` block from twscrape's `api.py` — without it X returns `(336) The following features cannot be null`. Pass it URL-encoded as the `features` param. ### Where things live - Output CSV: `~/Downloads/utilities/sdand_following.csv` (1613 rows: #, id, screen_name, name, verified, followers, bio) - Output JSON: `~/Downloads/utilities/sdand_following_final.json` (double-encoded JSON string; parse with `json.loads(json.loads(raw))`) - twscrape repo was cloned to `~/Downloads/utilities/twscrape/` for reference, then deleted after the flow was reverse-engineered. Re-clone from https://github.com/vladkens/twscrape.git if needed. ## Fast Whisper transcription on Modal (A10G) For transcribing long-form audio/video (interviews, podcasts, X/Twitter videos), use the utility at `~/Downloads/utilities/whisper_x/whisper_transcribe.py`. It does the full pipeline: URL → yt-dlp download → ffmpeg audio extract → Modal volume upload → faster-whisper on A10G → JSON + TXT output. Validated at **2.3 min wall clock for 65 min of audio** (no caching at any layer). ### Usage Shell alias (defined in `~/.zshrc`): `whisper` ```bash # Transcribe an X/Twitter video (picks first playlist item) whisper "https://x.com/.../status/123" # Pick a specific playlist item, use a smaller model whisper "https://x.com/..." --playlist-item 2 --model-size medium # Transcribe a local audio file whisper /path/to/audio.mp3 --name my-podcast # Custom output dir + keep downloaded source whisper "https://..." --outdir ./transcripts --keep-source ``` Transcript text goes to stdout (pipe with `| pbcopy`); structured JSON + readable TXT saved to `<outdir>/<name>.json` and `<outdir>/<name>.txt`. ### Key optimizations (vs naive T4 run that took 11.7 min) - **A10G GPU** (~8x fp16 throughput vs T4; Modal ~$0.60/hr vs ~$0.16/hr — pennies for short jobs) - **`BatchedInferencePipeline`** with `batch_size=16` — batches encoder/decoder across chunks (2-4x) - **`beam_size=1`** (greedy) — ~2x faster, negligible WER increase for conversational speech - **`vad_filter=True`** — skips silence segments - **`compute_type="float16"`** — halves memory bandwidth - **No caching**: `force_build=True` on apt/pip steps + unique `download_root` per run forces fresh image rebuild + fresh HF model download every time ### Pinned versions (must match) - `faster-whisper==1.1.1` (provides `BatchedInferencePipeline`) - `ctranslate2==4.8.0` - Base image: `nvidia/cuda:12.6.3-cudnn-runtime-ubuntu22.04` (provides `libcublas.so.12`; `debian_slim` fails with `RuntimeError: Library libcublas.so.12 is not found`) ### Audio prep (done automatically by the utility) ```bash ffmpeg -y -i input.mp4 -vn -ac 1 -ar 16000 -c:a aac -b:a 64k audio.m4a ``` Mono 16kHz 64kbps AAC — a 65-min video (151 MB stream) becomes ~35 MB audio. ### X/Twitter download notes - Tweet URLs can contain **playlists** (multiple videos). Use `--playlist-item N` to pick one. - Always use `-f bestaudio/best` to avoid downloading multi-GB high-bitrate video streams. - A 65-min interview's video variant can be 2.8+ GB; audio-only is ~63 MB (128 kbps). ### Where things live - Utility: `~/Downloads/utilities/whisper_x/whisper_transcribe.py` - Strategy doc: `~/Downloads/utilities/whisper_x/STRATEGY.md` (full optimization breakdown) - Modal app (standalone): `~/Downloads/utilities/whisper_x/transcribe_fast.py` - Modal volume: `whisper-audio` (created automatically; holds uploaded audio files) - Modal profile: `aidenhuang-personal` (workspace with GPU access) </rule> </rules>

<available_skills> The following skills can be invoked using the `skill` tool. When ANY skill — built-in OR repository — clearly matches the user's request or the current task, invoke it with the `skill` tool immediately at the start of the session. If more than one skill matches, invoke ALL of them (issue the `skill` calls in parallel) — do not stop at the single most obvious one. - **durable-objects**: Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/durable-objects/SKILL.md) - **wrangler**: Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.claude/skills/wrangler/SKILL.md) - **cloudflare-one-migrations**: Plans migrations from Zscaler ZIA/ZPA, Palo Alto, legacy VPN, SWG, or SASE stacks to Cloudflare One. Use for migration assessments, policy mapping, rollout plans, and parity/gap analysis. (source: /Users/root1/.agents/skills/cloudflare-one-migrations/SKILL.md) - **web-perf**: Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge. (source: /Users/root1/.codeium/windsurf/skills/web-perf/SKILL.md) - **sandbox-sdk**: Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.claude/skills/sandbox-sdk/SKILL.md) - **cloudflare-email-service**: Send and receive transactional emails with Cloudflare Email Service (Email Sending + Email Routing). Use when building email sending (Workers binding or REST API), email routing, Agents SDK email handling, or integrating email into any app — Workers, Node.js, Python, Go, etc. Also use for email deliverability, SPF/DKIM/DMARC, wrangler email setup, MCP email tools, or when a coding agent needs to send emails. Even for simple requests like "add email to my Worker" — this skill has critical config details. (source: /Users/root1/.codeium/windsurf/skills/cloudflare-email-service/SKILL.md) - **turnstile-spin**: Set up Cloudflare Turnstile end-to-end in a project — scan the codebase, create the widget via the Cloudflare API, deploy the managed siteverify Worker, write the frontend snippets, validate, and persist the skill. Load this when a user asks to add Turnstile, set up CAPTCHA, protect a form from bots, or fix a Turnstile integration. Mirrors developers.cloudflare.com/turnstile/spin. (source: /Users/root1/.claude/skills/turnstile-spin/SKILL.md) - **cloudflare**: Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/cloudflare/SKILL.md) - **web-perf**: Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/web-perf/SKILL.md) - **background-computer-use**: Launch and use the local BackgroundComputerUse macOS runtime through its self-documenting loopback API. Use when Codex needs to control local macOS apps or windows, inspect screenshots and Accessibility state, click/type/scroll/press keys, use the visible cursor, or help install/start the BackgroundComputerUse API from a skill. (source: /Users/root1/.devin/skills/background-computer-use/SKILL.md) - **durable-objects**: Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.agents/skills/durable-objects/SKILL.md) - **wrangler**: Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/wrangler/SKILL.md) - **cloudflare**: Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.codeium/windsurf/skills/cloudflare/SKILL.md) - **cloudflare-agent-setup**: (source: /Users/root1/.devin/skills/cloudflare-agent-setup/SKILL.md) - **agents-sdk**: Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, chat applications, voice agents, or browser automation. Covers Agent class, state management, callable RPC, Workflows, durable execution, queues, retries, observability, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.claude/skills/agents-sdk/SKILL.md) - **find-skills**: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill. (source: /Users/root1/.agents/skills/find-skills/SKILL.md) - **workers-best-practices**: Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.claude/skills/workers-best-practices/SKILL.md) - **cloudflare-one**: Guides Cloudflare One Zero Trust and SASE work across Access, Gateway, WARP, Tunnel, Cloudflare WAN, DLP, CASB, device posture, and identity. Use when designing, configuring, troubleshooting, or reviewing Cloudflare One deployments. Retrieval-first: use current Cloudflare docs/API schemas instead of embedded product docs. (source: /Users/root1/.config/devin/skills/cloudflare-one/SKILL.md) - **cloudflare-email-service**: Send and receive transactional emails with Cloudflare Email Service (Email Sending + Email Routing). Use when building email sending (Workers binding or REST API), email routing, Agents SDK email handling, or integrating email into any app — Workers, Node.js, Python, Go, etc. Also use for email deliverability, SPF/DKIM/DMARC, wrangler email setup, MCP email tools, or when a coding agent needs to send emails. Even for simple requests like "add email to my Worker" — this skill has critical config details. (source: /Users/root1/.config/devin/skills/cloudflare-email-service/SKILL.md) - **workers-best-practices**: Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/workers-best-practices/SKILL.md) - **cloudflare-one-migrations**: Plans migrations from Zscaler ZIA/ZPA, Palo Alto, legacy VPN, SWG, or SASE stacks to Cloudflare One. Use for migration assessments, policy mapping, rollout plans, and parity/gap analysis. (source: /Users/root1/.config/devin/skills/cloudflare-one-migrations/SKILL.md) - **sandbox-sdk**: Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/sandbox-sdk/SKILL.md) - **agents-sdk**: Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, chat applications, voice agents, or browser automation. Covers Agent class, state management, callable RPC, Workflows, durable execution, queues, retries, observability, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. (source: /Users/root1/.config/devin/skills/agents-sdk/SKILL.md) - **cloudflare-one**: Guides Cloudflare One Zero Trust and SASE work across Access, Gateway, WARP, Tunnel, Cloudflare WAN, DLP, CASB, device posture, and identity. Use when designing, configuring, troubleshooting, or reviewing Cloudflare One deployments. Retrieval-first: use current Cloudflare docs/API schemas instead of embedded product docs. (source: /Users/root1/.claude/skills/cloudflare-one/SKILL.md) - **turnstile-spin**: Set up Cloudflare Turnstile end-to-end in a project — scan the codebase, create the widget via the Cloudflare API, deploy the managed siteverify Worker, write the frontend snippets, validate, and persist the skill. Load this when a user asks to add Turnstile, set up CAPTCHA, protect a form from bots, or fix a Turnstile integration. Mirrors developers.cloudflare.com/turnstile/spin. (source: /Users/root1/.config/devin/skills/turnstile-spin/SKILL.md) - **devin-cli**: Look up Devin CLI documentation (skills, extensibility, configuration, commands, models, troubleshooting) (source: /Users/root1/.local/share/devin/cli/_versions/3000.1.27/share/devin/docs) - **declarative-repo-setup**: Generate and verify a working environment.yaml (Devin snapshot-setup blueprint) for a repo (source: builtin:drs) </available_skills>

Output from command in shell ffb887: WARNING: Your yt-dlp version (2025.12.08) is older than 90 days! It is strongly recommended to always use the latest version. You installed yt-dlp with pip or using the wheel from PyPi; Use that to update. To suppress this warning, add --no-update to your command/config. [youtube] Extracting URL: https://www.youtube.com/watch?v=t-kXDahZBhk&pp=ygUIcmVpc3NodWI%3D [youtube] t-kXDahZBhk: Downloading webpage [youtube] t-kXDahZBhk: Downloading tv client config [youtube] t-kXDahZBhk: Downloading player 882a803a-main [youtube] t-kXDahZBhk: Downloading tv player API JSON [youtube] t-kXDahZBhk: Downloading android sdkless player API JSON [youtube] [jsc:deno] Solving JS challenges using deno WARNING: [youtube] [jsc] Remote components challenge solver script (deno) and NPM package (deno) were skipped. These may be required to solve JS challenges. You can enable these downloads with --remote-components ejs:github (recommended) or --remote-components ejs:npm , respectively. For more information and alternatives, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS WARNING: [youtube] t-kXDahZBhk: n challenge solving failed: Some formats may be missing. Ensure you have a supported JavaScript runtime and challenge solver script distribution installed. Review any warnings presented before this message. For more details, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS [info] Available automatic captions for t-kXDahZBhk: Language Name Formats ab Abkhazian vtt, srt, ttml, srv3, srv2, srv1, json3 aa Afar vtt, srt, ttml, srv3, srv2, srv1, json3 af Afrikaans vtt, srt, ttml, srv3, srv2, srv1, json3 ak Akan vtt, srt, ttml, srv3, srv2, srv1, json3 sq Albanian vtt, srt, ttml, srv3, srv2, srv1, json3 am Amharic vtt, srt, ttml, srv3, srv2, srv1, json3 ar Arabic vtt, srt, ttml, srv3, srv2, srv1, json3 hy Armenian vtt, srt, ttml, srv3, srv2, srv1, json3 as Assamese vtt, srt, ttml, srv3, srv2, srv1, json3 ay Aymara vtt, srt, ttml, srv3, srv2, srv1, json3 az Azerbaijani vtt, srt, ttml, srv3, srv2, srv1, json3 bn Bangla vtt, srt, ttml, srv3, srv2, srv1, json3 ba Bashkir vtt, srt, ttml, srv3, srv2, srv1, json3 eu Basque vtt, srt, ttml, srv3, srv2, srv1, json3 be Belarusian vtt, srt, ttml, srv3, srv2, srv1, json3 bho Bhojpuri vtt, srt, ttml, srv3, srv2, srv1, json3 bs Bosnian vtt, srt, ttml, srv3, srv2, srv1, json3 br Breton vtt, srt, ttml, srv3, srv2, srv1, json3 bg Bulgarian vtt, srt, ttml, srv3, srv2, srv1, json3 my Burmese vtt, srt, ttml, srv3, srv2, srv1, json3 ca Catalan vtt, srt, ttml, srv3, srv2, srv1, json3 ceb Cebuano vtt, srt, ttml, srv3, srv2, srv1, json3 zh-Hans Chinese (Simplified) vtt, srt, ttml, srv3, srv2, srv1, json3 zh-Hant Chinese (Traditional) vtt, srt, ttml, srv3, srv2, srv1, json3 co Corsican vtt, srt, ttml, srv3, srv2, srv1, json3 hr Croatian vtt, srt, ttml, srv3, srv2, srv1, json3 cs Czech vtt, srt, ttml, srv3, srv2, srv1, json3 da Danish vtt, srt, ttml, srv3, srv2, srv1, json3 dv Divehi vtt, srt, ttml, srv3, srv2, srv1, json3 nl Dutch vtt, srt, ttml, srv3, srv2, srv1, json3 dz Dzongkha vtt, srt, ttml, srv3, srv2, srv1, json3 en-orig English (Original) vtt, srt, ttml, srv3, srv2, srv1, json3 en English vtt, srt, ttml, srv3, srv2, srv1, json3 eo Esperanto vtt, srt, ttml, srv3, srv2, srv1, json3 et Estonian vtt, srt, ttml, srv3, srv2, srv1, json3 ee Ewe vtt, srt, ttml, srv3, srv2, srv1, json3 fo Faroese vtt, srt, ttml, srv3, srv2, srv1, json3 fj Fijian vtt, srt, ttml, srv3, srv2, srv1, json3 fil Filipino vtt, srt, ttml, srv3, srv2, srv1, json3 fi Finnish vtt, srt, ttml, srv3, srv2, srv1, json3 fr French vtt, srt, ttml, srv3, srv2, srv1, json3 gaa Ga vtt, srt, ttml, srv3, srv2, srv1, json3 gl Galician vtt, srt, ttml, srv3, srv2, srv1, json3 lg Ganda vtt, srt, ttml, srv3, srv2, srv1, json3 ka Georgian vtt, srt, ttml, srv3, srv2, srv1, json3 de German vtt, srt, ttml, srv3, srv2, srv1, json3 el Greek vtt, srt, ttml, srv3, srv2, srv1, json3 gn Guarani vtt, srt, ttml, srv3, srv2, srv1, json3 gu Gujarati vtt, srt, ttml, srv3, srv2, srv1, json3 ht Haitian Creole vtt, srt, ttml, srv3, srv2, srv1, json3 ha Hausa vtt, srt, ttml, srv3, srv2, srv1, json3 haw Hawaiian vtt, srt, ttml, srv3, srv2, srv1, json3 iw Hebrew vtt, srt, ttml, srv3, srv2, srv1, json3 hi Hindi vtt, srt, ttml, srv3, srv2, srv1, json3 hmn Hmong vtt, srt, ttml, srv3, srv2, srv1, json3 hu Hungarian vtt, srt, ttml, srv3, srv2, srv1, json3 is Icelandic vtt, srt, ttml, srv3, srv2, srv1, json3 ig Igbo vtt, srt, ttml, srv3, srv2, srv1, json3 id Indonesian vtt, srt, ttml, srv3, srv2, srv1, json3 iu Inuktitut vtt, srt, ttml, srv3, srv2, srv1, json3 ga Irish vtt, srt, ttml, srv3, srv2, srv1, json3 it Italian vtt, srt, ttml, srv3, srv2, srv1, json3 ja Japanese vtt, srt, ttml, srv3, srv2, srv1, json3 jv Javanese vtt, srt, ttml, srv3, srv2, srv1, json3 kl Kalaallisut vtt, srt, ttml, srv3, srv2, srv1, json3 kn Kannada vtt, srt, ttml, srv3, srv2, srv1, json3 kk Kazakh vtt, srt, ttml, srv3, srv2, srv1, json3 kha Khasi vtt, srt, ttml, srv3, srv2, srv1, json3 km Khmer vtt, srt, ttml, srv3, srv2, srv1, json3 rw Kinyarwanda vtt, srt, ttml, srv3, srv2, srv1, json3 ko Korean vtt, srt, ttml, srv3, srv2, srv1, json3 kri Krio vtt, srt, ttml, srv3, srv2, srv1, json3 ku Kurdish vtt, srt, ttml, srv3, srv2, srv1, json3 ky Kyrgyz vtt, srt, ttml, srv3, srv2, srv1, json3 lo Lao vtt, srt, ttml, srv3, srv2, srv1, json3 la Latin vtt, srt, ttml, srv3, srv2, srv1, json3 lv Latvian vtt, srt, ttml, srv3, srv2, srv1, json3 ln Lingala vtt, srt, ttml, srv3, srv2, srv1, json3 lt Lithuanian vtt, srt, ttml, srv3, srv2, srv1, json3 lua Luba-Lulua vtt, srt, ttml, srv3, srv2, srv1, json3 luo Luo vtt, srt, ttml, srv3, srv2, srv1, json3 lb Luxembourgish vtt, srt, ttml, srv3, srv2, srv1, json3 mk Macedonian vtt, srt, ttml, srv3, srv2, srv1, json3 mg Malagasy vtt, srt, ttml, srv3, srv2, srv1, json3 ms Malay vtt, srt, ttml, srv3, srv2, srv1, json3 ml Malayalam vtt, srt, ttml, srv3, srv2, srv1, json3 mt Maltese vtt, srt, ttml, srv3, srv2, srv1, json3 gv Manx vtt, srt, ttml, srv3, srv2, srv1, json3 mi Māori vtt, srt, ttml, srv3, srv2, srv1, json3 mr Marathi vtt, srt, ttml, srv3, srv2, srv1, json3 mn Mongolian vtt, srt, ttml, srv3, srv2, srv1, json3 mfe Morisyen vtt, srt, ttml, srv3, srv2, srv1, json3 ne Nepali vtt, srt, ttml, srv3, srv2, srv1, json3 new Newari vtt, srt, ttml, srv3, srv2, srv1, json3 nso Northern Sotho vtt, srt, ttml, srv3, srv2, srv1, json3 no Norwegian vtt, srt, ttml, srv3, srv2, srv1, json3 ny Nyanja vtt, srt, ttml, srv3, srv2, srv1, json3 oc Occitan vtt, srt, ttml, srv3, srv2, srv1, json3 or Odia vtt, srt, ttml, srv3, srv2, srv1, json3 om Oromo vtt, srt, ttml, srv3, srv2, srv1, json3 os Ossetic vtt, srt, ttml, srv3, srv2, srv1, json3 pam Pampanga vtt, srt, ttml, srv3, srv2, srv1, json3 ps Pashto vtt, srt, ttml, srv3, srv2, srv1, json3 fa Persian vtt, srt, ttml, srv3, srv2, srv1, json3 pl Polish vtt, srt, ttml, srv3, srv2, srv1, json3 pt Portuguese vtt, srt, ttml, srv3, srv2, srv1, json3 pt-PT Portuguese (Portugal) vtt, srt, ttml, srv3, srv2, srv1, json3 pa Punjabi vtt, srt, ttml, srv3, srv2, srv1, json3 qu Quechua vtt, srt, ttml, srv3, srv2, srv1, json3 ro Romanian vtt, srt, ttml, srv3, srv2, srv1, json3 rn Rundi vtt, srt, ttml, srv3, srv2, srv1, json3 ru Russian vtt, srt, ttml, srv3, srv2, srv1, json3 sm Samoan vtt, srt, ttml, srv3, srv2, srv1, json3 sg Sango vtt, srt, ttml, srv3, srv2, srv1, json3 sa Sanskrit vtt, srt, ttml, srv3, srv2, srv1, json3 gd Scottish Gaelic vtt, srt, ttml, srv3, srv2, srv1, json3 sr Serbian vtt, srt, ttml, srv3, srv2, srv1, json3 crs Seselwa Creole French vtt, srt, ttml, srv3, srv2, srv1, json3 sn Shona vtt, srt, ttml, srv3, srv2, srv1, json3 sd Sindhi vtt, srt, ttml, srv3, srv2, srv1, json3 si Sinhala vtt, srt, ttml, srv3, srv2, srv1, json3 sk Slovak vtt, srt, ttml, srv3, srv2, srv1, json3 sl Slovenian vtt, srt, ttml, srv3, srv2, srv1, json3 so Somali vtt, srt, ttml, srv3, srv2, srv1, json3 st Southern Sotho vtt, srt, ttml, srv3, srv2, srv1, json3 es Spanish vtt, srt, ttml, srv3, srv2, srv1, json3 su Sundanese vtt, srt, ttml, srv3, srv2, srv1, json3 sw Swahili vtt, srt, ttml, srv3, srv2, srv1, json3 ss Swati vtt, srt, ttml, srv3, srv2, srv1, json3 sv Swedish vtt, srt, ttml, srv3, srv2, srv1, json3 tg Tajik vtt, srt, ttml, srv3, srv2, srv1, json3 ta Tamil vtt, srt, ttml, srv3, srv2, srv1, json3 tt Tatar vtt, srt, ttml, srv3, srv2, srv1, json3 te Telugu vtt, srt, ttml, srv3, srv2, srv1, json3 th Thai vtt, srt, ttml, srv3, srv2, srv1, json3 bo Tibetan vtt, srt, ttml, srv3, srv2, srv1, json3 ti Tigrinya vtt, srt, ttml, srv3, srv2, srv1, json3 to Tongan vtt, srt, ttml, srv3, srv2, srv1, json3 ts Tsonga vtt, srt, ttml, srv3, srv2, srv1, json3 tn Tswana vtt, srt, ttml, srv3, srv2, srv1, json3 tum Tumbuka vtt, srt, ttml, srv3, srv2, srv1, json3 tr Turkish vtt, srt, ttml, srv3, srv2, srv1, json3 tk Turkmen vtt, srt, ttml, srv3, srv2, srv1, json3 uk Ukrainian vtt, srt, ttml, srv3, srv2, srv1, json3 ur Urdu vtt, srt, ttml, srv3, srv2, srv1, json3 ug Uyghur vtt, srt, ttml, srv3, srv2, srv1, json3 uz Uzbek vtt, srt, ttml, srv3, srv2, srv1, json3 ve Venda vtt, srt, ttml, srv3, srv2, srv1, json3 vi Vietnamese vtt, srt, ttml, srv3, srv2, srv1, json3 war Waray vtt, srt, ttml, srv3, srv2, srv1, json3 cy Welsh vtt, srt, ttml, srv3, srv2, srv1, json3 fy Western Frisian vtt, srt, ttml, srv3, srv2, srv1, json3 wo Wolof vtt, srt, ttml, srv3, srv2, srv1, json3 xh Xhosa vtt, srt, ttml, srv3, srv2, srv1, json3 yi Yiddish vtt, srt, ttml, srv3, srv2, srv1, json3 yo Yoruba vtt, srt, ttml, srv3, srv2, srv1, json3 zu Zulu vtt, srt, ttml, srv3, srv2, srv1, json3 t-kXDahZBhk has no subtitles Exit code: 0

{ "command": "yt-dlp --skip-download --write-auto-subs --sub-langs en-orig --sub-format srt --output \"/tmp/%(id)s.%(ext)s\" \"https://www.youtube.com/watch?v=t-kXDahZBhk&pp=ygUIcmVpc3NodWI%3D\"", "timeout": 60000 }

Output from command in shell c4da3c: WARNING: Your yt-dlp version (2025.12.08) is older than 90 days! It is strongly recommended to always use the latest version. You installed yt-dlp with pip or using the wheel from PyPi; Use that to update. To suppress this warning, add --no-update to your command/config. [youtube] Extracting URL: https://www.youtube.com/watch?v=t-kXDahZBhk&pp=ygUIcmVpc3NodWI%3D [youtube] t-kXDahZBhk: Downloading webpage [youtube] t-kXDahZBhk: Downloading tv client config [youtube] t-kXDahZBhk: Downloading player 882a803a-main [youtube] t-kXDahZBhk: Downloading tv player API JSON [youtube] t-kXDahZBhk: Downloading android sdkless player API JSON WARNING: [youtube] t-kXDahZBhk: Some tv client https formats have been skipped as they are missing a url. YouTube may have enabled the SABR-only or Server-Side Ad Placement experiment for the current session. See https://github.com/yt-dlp/yt-dlp/issues/12482 for more details [youtube] [jsc:deno] Solving JS challenges using deno WARNING: [youtube] [jsc] Remote components challenge solver script (deno) and NPM package (deno) were skipped. These may be required to solve JS challenges. You can enable these downloads with --remote-components ejs:github (recommended) or --remote-components ejs:npm , respectively. For more information and alternatives, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS WARNING: [youtube] t-kXDahZBhk: n challenge solving failed: Some formats may be missing. Ensure you have a supported JavaScript runtime and challenge solver script distribution installed. Review any warnings presented before this message. For more details, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS WARNING: [youtube] t-kXDahZBhk: Some web client https formats have been skipped as they are missing a url. YouTube is forcing SABR streaming for this client. See https://github.com/yt-dlp/yt-dlp/issues/12482 for more details [info] t-kXDahZBhk: Downloading subtitles: en-orig [info] t-kXDahZBhk: Downloading 1 format(s): 399+251 [info] Writing video subtitles to: /tmp/t-kXDahZBhk.en-orig.srt [download] Destination: /tmp/t-kXDahZBhk.en-orig.srt [download] 1.00KiB at Unknown B/s (00:00:00) [download] 3.00KiB at Unknown B/s (00:00:00) [download] 7.00KiB at Unknown B/s (00:00:00) [download] 15.00KiB at 4.66MiB/s (00:00:00) [download] 27.45KiB at 3.01MiB/s (00:00:00) [download] 100% of 27.45KiB in 00:00:00 at 202.91KiB/s Exit code: 0

<file-view path="/tmp/t-kXDahZBhk.en-orig.srt" start_line="1" end_line="1101" total_lines="1544"> 1|1 2|00:00:00,000 --> 00:00:03,120 3|Fortnite's released a ton of broken 4| 5|2 6|00:00:01,520 --> 00:00:04,560 7|pistols over the last 9 years, and if 8| 9|3 10|00:00:03,120 --> 00:00:05,960 11|you played this season at all, it 12| 13|4 14|00:00:04,560 --> 00:00:08,680 15|shouldn't surprise you that the Ranger 16| 17|5 18|00:00:05,960 --> 00:00:10,360 19|pistol is the most used weapon in every 20| 21|6 22|00:00:08,680 --> 00:00:12,560 23|single Fortnite tournament. So, how did 24| 25|7 26|00:00:10,360 --> 00:00:14,320 27|Fortnite's weakest weapon become the 28| 29|8 30|00:00:12,560 --> 00:00:16,280 31|meta? There's two different types of 32| 33|9 34|00:00:14,320 --> 00:00:17,600 35|pistols. There's the main pistols, and 36| 37|10 38|00:00:16,280 --> 00:00:19,400 39|then there's the secondary pistols, 40| 41|11 42|00:00:17,600 --> 00:00:20,680 43|which are not in every single season. 44| 45|12 46|00:00:19,400 --> 00:00:22,320 47|I'm going to cover both in this video 48| 49|13 50|00:00:20,680 --> 00:00:23,960 51|because there's really broken examples 52| 53|14 54|00:00:22,320 --> 00:00:26,000 55|of both of these. The first ever pistol 56| 57|15 58|00:00:23,960 --> 00:00:27,800 59|added to Fortnite was the semi-auto 60| 61|16 62|00:00:26,000 --> 00:00:29,520 63|pistol, and I think Fortnite did a good 64| 65|17 66|00:00:27,800 --> 00:00:31,840 67|job balancing this in the very first 68| 69|18 70|00:00:29,520 --> 00:00:33,440 71|season. It could deal up to 169 damage 72| 73|19 74|00:00:31,840 --> 00:00:34,960 75|per second, but it wasn't auto mag as 76| 77|20 78|00:00:33,440 --> 00:00:36,600 79|you have to spam the shoot button to 80| 81|21 82|00:00:34,960 --> 00:00:38,280 83|actually fire it. If we compare this to 84| 85|22 86|00:00:36,600 --> 00:00:40,000 87|all of the other main pistols across 88| 89|23 90|00:00:38,280 --> 00:00:42,400 91|Fortnite's lifespan, we can see that the 92| 93|24 94|00:00:40,000 --> 00:00:45,040 95|vast majority of these deal around 175 96| 97|25 98|00:00:42,400 --> 00:00:47,280 99|damage per second. So, the 169 of the 100| 101|26 102|00:00:45,040 --> 00:00:49,080 103|first ever pistol was pretty close to 104| 105|27 106|00:00:47,280 --> 00:00:50,640 107|the balance that Fortnite would keep for 108| 109|28 110|00:00:49,080 --> 00:00:52,280 111|many years. In this season, the assault 112| 113|29 114|00:00:50,640 --> 00:00:54,800 115|rifle was better at long ranges dealing 116| 117|30 118|00:00:52,280 --> 00:00:57,520 119|up to 192.5 damage per second, and the 120| 121|31 122|00:00:54,800 --> 00:00:59,520 123|SMGs were insane at close ranges and in 124| 125|32 126|00:00:57,520 --> 00:01:01,960 127|no way balanced with a damage per second 128| 129|33 130|00:00:59,520 --> 00:01:03,120 131|of up to 240. 132| 133|34 134|00:01:01,960 --> 00:01:05,640 135|This meant that the pistol wasn't the 136| 137|35 138|00:01:03,120 --> 00:01:07,720 139|best in any one scenario, but it was 140| 141|36 142|00:01:05,640 --> 00:01:09,440 143|viable and usable in both. This was 144| 145|37 146|00:01:07,720 --> 00:01:11,320 147|probably the weakest pistol ever, mainly 148| 149|38 150|00:01:09,440 --> 00:01:13,360 151|due to the actual meta that surrounded 152| 153|39 154|00:01:11,320 --> 00:01:15,160 155|it. The first actually broken pistol to 156| 157|40 158|00:01:13,360 --> 00:01:17,080 159|be added to Fortnite was the hand 160| 161|41 162|00:01:15,160 --> 00:01:18,600 163|cannon, first added in chapter [music] 1 164| 165|42 166|00:01:17,080 --> 00:01:20,320 167|season 3. Now, I've gone over this 168| 169|43 170|00:01:18,600 --> 00:01:22,040 171|weapon in another video already, so I'll 172| 173|44 174|00:01:20,320 --> 00:01:24,160 175|cover this item kind of quickly. This 176| 177|45 178|00:01:22,040 --> 00:01:26,040 179|gun was insanely busted at long range, 180| 181|46 182|00:01:24,160 --> 00:01:27,760 183|mainly because of legacy aim assist as 184| 185|47 186|00:01:26,040 --> 00:01:29,240 187|it had a snap on feature that dragged 188| 189|48 190|00:01:27,760 --> 00:01:30,600 191|your crosshair towards the opponent. All 192| 193|49 194|00:01:29,240 --> 00:01:32,200 195|you needed to do is put your crosshair 196| 197|50 198|00:01:30,600 --> 00:01:33,800 199|somewhere near another player, aim down 200| 201|51 202|00:01:32,200 --> 00:01:35,520 203|the sights, and the crosshair would snap 204| 205|52 206|00:01:33,800 --> 00:01:37,400 207|onto them, so then you just shoot. Epic 208| 209|53 210|00:01:35,520 --> 00:01:40,400 211|Games also decided to buff the structure 212| 213|54 214|00:01:37,400 --> 00:01:42,720 215|damage of this to 150, so it could break 216| 217|55 218|00:01:40,400 --> 00:01:44,400 219|fully built wood walls in a single shot. 220| 221|56 222|00:01:42,720 --> 00:01:46,200 223|But at this time, people just started to 224| 225|57 226|00:01:44,400 --> 00:01:47,480 227|learn how to defensively box fight, and 228| 229|58 230|00:01:46,200 --> 00:01:49,880 231|this seemed to be something that Epic 232| 233|59 234|00:01:47,480 --> 00:01:51,400 235|Games was trying to actively avoid. So, 236| 237|60 238|00:01:49,880 --> 00:01:52,960 239|they basically created a lot of high 240| 241|61 242|00:01:51,400 --> 00:01:54,200 243|structure damage weapons that canceled 244| 245|62 246|00:01:52,960 --> 00:01:56,280 247|this out. However, they did eventually 248| 249|63 250|00:01:54,200 --> 00:01:58,120 251|nerf this down to 95, making it still 252| 253|64 254|00:01:56,280 --> 00:02:00,200 255|strong but definitely removing one of 256| 257|65 258|00:01:58,120 --> 00:02:01,560 259|the main reasons why you'd pick this up. 260| 261|66 262|00:02:00,200 --> 00:02:03,680 263|Now, chapter two is before Fortnite 264| 265|67 266|00:02:01,560 --> 00:02:05,000 267|started to do a completely new loot pool 268| 269|68 270|00:02:03,680 --> 00:02:07,071 271|and new weapons for every single 272| 273|69 274|00:02:05,000 --> 00:02:08,720 275|chapter. So, the main pistol this 276| 277|70 278|00:02:07,071 --> 00:02:10,360 279|[music] chapter was the semi-auto 280| 281|71 282|00:02:08,720 --> 00:02:11,720 283|pistol, the same one from the previous 284| 285|72 286|00:02:10,360 --> 00:02:13,560 287|season. However, they did add a purple 288| 289|73 290|00:02:11,720 --> 00:02:15,120 291|and gold version and buffed the damage 292| 293|74 294|00:02:13,560 --> 00:02:17,240 295|slightly. Interestingly, this was the 296| 297|75 298|00:02:15,120 --> 00:02:18,959 299|first time that the main pistol actually 300| 301|76 302|00:02:17,240 --> 00:02:20,720 303|got some viability and some use [music] 304| 305|77 306|00:02:18,959 --> 00:02:22,000 307|in a competitive tournament. In chapter 308| 309|78 310|00:02:20,720 --> 00:02:23,959 311|two, season three, the headshot 312| 313|79 314|00:02:22,000 --> 00:02:27,000 315|multiplier for assault rifles and SMGs 316| 317|80 318|00:02:23,959 --> 00:02:28,440 319|was reduced from two times to 1.5 times, 320| 321|81 322|00:02:27,000 --> 00:02:30,200 323|but the pistol headshot multiplier was 324| 325|82 326|00:02:28,440 --> 00:02:31,640 327|still two times, which is still the case 328| 329|83 330|00:02:30,200 --> 00:02:33,320 331|today. So, since chapter two, pistols 332| 333|84 334|00:02:31,640 --> 00:02:34,600 335|have actually been the best weapon at 336| 337|85 338|00:02:33,320 --> 00:02:36,360 339|dealing headshot damage. Now, this 340| 341|86 342|00:02:34,600 --> 00:02:38,360 343|change actually gave people a reason to 344| 345|87 346|00:02:36,360 --> 00:02:40,400 347|carry a pistol in tournaments, and only 348| 349|88 350|00:02:38,360 --> 00:02:42,400 351|one person did. That person was King. 352| 353|89 354|00:02:40,400 --> 00:02:43,920 355|Chapter two, season three was solos, and 356| 357|90 358|00:02:42,400 --> 00:02:45,640 359|he carried the pistol in pretty much 360| 361|91 362|00:02:43,920 --> 00:02:46,800 363|every single game of the finals. I 364| 365|92 366|00:02:45,640 --> 00:02:48,200 367|remember thinking at the time it was 368| 369|93 370|00:02:46,800 --> 00:02:49,959 371|weird that he mained it every single 372| 373|94 374|00:02:48,200 --> 00:02:51,400 375|game because it wasn't an automatic 376| 377|95 378|00:02:49,959 --> 00:02:53,600 379|weapon at this point. However, he did 380| 381|96 382|00:02:51,400 --> 00:02:55,200 383|win FNCS maining it, so it was clearly a 384| 385|97 386|00:02:53,600 --> 00:02:56,680 387|little bit underrated this season. he 388| 389|98 390|00:02:55,200 --> 00:02:58,720 391|was just using a shoot macro to make it 392| 393|99 394|00:02:56,680 --> 00:03:00,560 395|automatic. Now, it took until chapter 396| 397|100 398|00:02:58,720 --> 00:03:02,000 399|four for pistols to become automatic, 400| 401|101 402|00:03:00,560 --> 00:03:03,480 403|and that was with the addition of the 404| 405|102 406|00:03:02,000 --> 00:03:05,440 407|tactical pistol. By the way, if you 408| 409|103 410|00:03:03,480 --> 00:03:08,880 411|wondered why I skipped chapter three 412| 413|104 414|00:03:05,440 --> 00:03:10,480 415|here, this is the wiki for it. 416| 417|105 418|00:03:08,880 --> 00:03:11,560 419|Kind of empty. There's There's not a lot 420| 421|106 422|00:03:10,480 --> 00:03:13,040 423|to talk about, I'll be honest. 424| 425|107 426|00:03:11,560 --> 00:03:15,120 427|Interestingly, chapter four's tactical 428| 429|108 430|00:03:13,040 --> 00:03:17,320 431|pistol had one of the lowest damage per 432| 433|109 434|00:03:15,120 --> 00:03:18,840 435|second of any main pistol released up 436| 437|110 438|00:03:17,320 --> 00:03:20,840 439|until this point, yet it was the first 440| 441|111 442|00:03:18,840 --> 00:03:22,480 443|to actually become viable. Not only was 444| 445|112 446|00:03:20,840 --> 00:03:24,760 447|it automatic, but it also had a really 448| 449|113 450|00:03:22,480 --> 00:03:26,840 451|tight spread and recoil, meaning it was 452| 453|114 454|00:03:24,760 --> 00:03:28,400 455|also very accurate. The main assault 456| 457|115 458|00:03:26,840 --> 00:03:30,480 459|rifle was the red-eye assault rifle, 460| 461|116 462|00:03:28,400 --> 00:03:32,400 463|which was a hitscan scoped weapon, 464| 465|117 466|00:03:30,480 --> 00:03:34,560 467|making it insane long ranges, but 468| 469|118 470|00:03:32,400 --> 00:03:36,720 471|absolutely terrible in close range. And 472| 473|119 474|00:03:34,560 --> 00:03:38,600 475|then the main SMG was the twin mag SMG, 476| 477|120 478|00:03:36,720 --> 00:03:39,720 479|which was insane at close range and 480| 481|121 482|00:03:38,600 --> 00:03:41,560 483|pretty good at medium range, but 484| 485|122 486|00:03:39,720 --> 00:03:43,560 487|terrible at long range. So, the tactical 488| 489|123 490|00:03:41,560 --> 00:03:44,959 491|pistol fit really well into this meta 492| 493|124 494|00:03:43,560 --> 00:03:47,120 495|because it wasn't the best at any 496| 497|125 498|00:03:44,959 --> 00:03:48,560 499|distance, but it was good in all of 500| 501|126 502|00:03:47,120 --> 00:03:50,200 503|them. There was also a mythic version 504| 505|127 506|00:03:48,560 --> 00:03:51,760 507|available through the reality augments, 508| 509|128 510|00:03:50,200 --> 00:03:53,280 511|which boosted up the usage of this gun 512| 513|129 514|00:03:51,760 --> 00:03:55,360 515|even more. Chapter 4 also saw the 516| 517|130 518|00:03:53,280 --> 00:03:57,600 519|release of the Mammoth Pistol. Now, in 520| 521|131 522|00:03:55,360 --> 00:03:59,400 523|blue rarity, the Mammoth Pistol dealt 94 524| 525|132 526|00:03:57,600 --> 00:04:01,600 527|body shot damage and it originally had a 528| 529|133 530|00:03:59,400 --> 00:04:03,720 531|1.85 times headshot multiplier, but this 532| 533|134 534|00:04:01,600 --> 00:04:05,440 535|was nerfed to 1.75 times. The Mammoth 536| 537|135 538|00:04:03,720 --> 00:04:07,320 539|Pistol was close to the Chapter 1 Hand 540| 541|136 542|00:04:05,440 --> 00:04:09,240 543|Cannon in that it was slow, but it fired 544| 545|137 546|00:04:07,320 --> 00:04:11,040 547|one big heavy-hitting shot. And the 548| 549|138 550|00:04:09,240 --> 00:04:12,720 551|downside of only having one shot per 552| 553|139 554|00:04:11,040 --> 00:04:14,040 555|reload, but for tournaments, this didn't 556| 557|140 558|00:04:12,720 --> 00:04:15,680 559|really matter much since you were mainly 560| 561|141 562|00:04:14,040 --> 00:04:17,640 563|just shooting once and then hiding 564| 565|142 566|00:04:15,680 --> 00:04:19,120 567|behind cover anyway as you reloaded. The 568| 569|143 570|00:04:17,640 --> 00:04:20,920 571|biggest issue this gun had is that it 572| 573|144 574|00:04:19,120 --> 00:04:23,160 575|was just incredibly easy to use with 576| 577|145 578|00:04:20,920 --> 00:04:24,960 579|almost no downsides. With a sniper, you 580| 581|146 582|00:04:23,160 --> 00:04:26,720 583|can send distances and ping shots to 584| 585|147 586|00:04:24,960 --> 00:04:28,400 587|other people, which is annoying, but 588| 589|148 590|00:04:26,720 --> 00:04:30,000 591|it's hard to hit those shots since 592| 593|149 594|00:04:28,400 --> 00:04:31,480 595|there's bullet travel time and bullet 596| 597|150 598|00:04:30,000 --> 00:04:33,480 599|drop. So, by taking a sniper, you're 600| 601|151 602|00:04:31,480 --> 00:04:35,320 603|taking up a valuable inventory slot that 604| 605|152 606|00:04:33,480 --> 00:04:37,080 607|doesn't necessarily guarantee you any 608| 609|153 610|00:04:35,320 --> 00:04:38,600 611|damage or eliminations. But since the 612| 613|154 614|00:04:37,080 --> 00:04:40,200 615|Mammoth Pistol was hit scan, it 616| 617|155 618|00:04:38,600 --> 00:04:42,240 619|basically created a meta where people 620| 621|156 622|00:04:40,200 --> 00:04:44,080 623|would just sit far away and ping shots 624| 625|157 626|00:04:42,240 --> 00:04:45,400 627|at you over and over again, and almost 628| 629|158 630|00:04:44,080 --> 00:04:47,200 631|every single one of these was close to 632| 633|159 634|00:04:45,400 --> 00:04:48,680 635|100 damage. In tournaments where you 636| 637|160 638|00:04:47,200 --> 00:04:51,320 639|have players with the best aim in the 640| 641|161 642|00:04:48,680 --> 00:04:53,440 643|world, this are not fun. Thankfully, 644| 645|162 646|00:04:51,320 --> 00:04:55,360 647|Chapter 5 fixed this problem by adding 648| 649|163 650|00:04:53,440 --> 00:04:57,120 651|bullet drop. Now, the main pistol in 652| 653|164 654|00:04:55,360 --> 00:04:58,360 655|this chapter was the Ranger Pistol, 656| 657|165 658|00:04:57,120 --> 00:05:00,080 659|which is currently the one that is 660| 661|166 662|00:04:58,360 --> 00:05:01,520 663|dominating [music] Chapter 7 right now. 664| 665|167 666|00:05:00,080 --> 00:05:03,640 667|However, it wasn't really that powerful 668| 669|168 670|00:05:01,520 --> 00:05:05,440 671|back in Chapter 5. It has been buffed 672| 673|169 674|00:05:03,640 --> 00:05:06,919 675|slightly in the last two chapters. Back 676| 677|170 678|00:05:05,440 --> 00:05:09,000 679|then, it had a very similar damage per 680| 681|171 682|00:05:06,919 --> 00:05:10,640 683|second as most of the main pistols that 684| 685|172 686|00:05:09,000 --> 00:05:12,520 687|came before it. Now, Chapter 5, because 688| 689|173 690|00:05:10,640 --> 00:05:14,480 691|every weapon had bullet drop, the Reaper 692| 693|174 694|00:05:12,520 --> 00:05:16,160 695|Sniper became much stronger in the meta 696| 697|175 698|00:05:14,480 --> 00:05:17,680 699|since every gun was hard to use at long 700| 701|176 702|00:05:16,160 --> 00:05:19,200 703|ranges. The main assault rifle was the 704| 705|177 706|00:05:17,680 --> 00:05:21,480 707|Striker Assault Rifle, which had a 708| 709|178 710|00:05:19,200 --> 00:05:23,200 711|really fast fire rate and tight spread, 712| 713|179 714|00:05:21,480 --> 00:05:25,560 715|making it really good in close and 716| 717|180 718|00:05:23,200 --> 00:05:27,080 719|medium ranges, too. The Thunderburst SMG 720| 721|181 722|00:05:25,560 --> 00:05:29,040 723|could also be modified to have zero 724| 725|182 726|00:05:27,080 --> 00:05:30,800 727|spread when moving and jumping, making 728| 729|183 730|00:05:29,040 --> 00:05:32,080 731|it by far the best weapon to fight with. 732| 733|184 734|00:05:30,800 --> 00:05:34,280 735|So, despite the Ranger Pistol being a 736| 737|185 738|00:05:32,080 --> 00:05:35,600 739|solid weapon and being very viable, it 740| 741|186 742|00:05:34,280 --> 00:05:38,080 743|wasn't the meta because it wasn't the 744| 745|187 746|00:05:35,600 --> 00:05:40,320 747|best in any one scenario, similar to how 748| 749|188 750|00:05:38,080 --> 00:05:41,720 751|the Chapter 1 semi-auto pistol worked. 752| 753|189 754|00:05:40,320 --> 00:05:43,480 755|This chapter also had the Monarch 756| 757|190 758|00:05:41,720 --> 00:05:45,000 759|Pistol, which was basically a toned-down 760| 761|191 762|00:05:43,480 --> 00:05:47,200 763|version of the Mammoth Pistol, but the 764| 765|192 766|00:05:45,000 --> 00:05:49,360 767|The drop made this gun a more skillful 768| 769|193 770|00:05:47,200 --> 00:05:50,960 771|and less frustrating. Prom HD made it to 772| 773|194 774|00:05:49,360 --> 00:05:52,400 775|the FNCS Global Championships where he 776| 777|195 778|00:05:50,960 --> 00:05:54,000 779|and Queasy placed second and their 780| 781|196 782|00:05:52,400 --> 00:05:55,360 783|search strategy was basically a lot of 784| 785|197 786|00:05:54,000 --> 00:05:56,800 787|search trading and a lot of hitting 788| 789|198 790|00:05:55,360 --> 00:05:57,920 791|every shot with a Monarch pistol. If 792| 793|199 794|00:05:56,800 --> 00:05:59,160 795|you're enjoying this video, please like 796| 797|200 798|00:05:57,920 --> 00:06:00,920 799|and subscribe to make sure you get to 800| 801|201 802|00:05:59,160 --> 00:06:02,680 803|see my next upload as well. In Chapter 804| 805|202 806|00:06:00,920 --> 00:06:05,080 807|6, Fortnite unvaulted the Suppressed 808| 809|203 810|00:06:02,680 --> 00:06:06,400 811|Pistol as the main pistol which 812| 813|204 814|00:06:05,080 --> 00:06:08,000 815|unsurprisingly it was basically the same 816| 817|205 818|00:06:06,400 --> 00:06:10,200 819|as every pistol that came before it. But 820| 821|206 822|00:06:08,000 --> 00:06:12,360 823|this chapter they went hard on the wacky 824| 825|207 826|00:06:10,200 --> 00:06:14,040 827|and creative pistols. In season 3 they 828| 829|208 830|00:06:12,360 --> 00:06:16,320 831|added the Hyper Burst Pistol and the 832| 833|209 834|00:06:14,040 --> 00:06:18,240 835|Kill Switch Revolvers. Now I absolutely 836| 837|210 838|00:06:16,320 --> 00:06:20,280 839|loved the Kill Switch Revolvers and I 840| 841|211 842|00:06:18,240 --> 00:06:22,080 843|really wish that I saw more pros come up 844| 845|212 846|00:06:20,280 --> 00:06:23,760 847|with sick tech with them as the slow-mo 848| 849|213 850|00:06:22,080 --> 00:06:25,120 851|jumping mechanic that they had was so 852| 853|214 854|00:06:23,760 --> 00:06:26,520 855|sick. But unfortunately they just 856| 857|215 858|00:06:25,120 --> 00:06:27,800 859|weren't really that good in competitive. 860| 861|216 862|00:06:26,520 --> 00:06:29,480 863|The Hyper Burst Pistol was actually 864| 865|217 866|00:06:27,800 --> 00:06:30,600 867|really solid but similar to previous 868| 869|218 870|00:06:29,480 --> 00:06:31,840 871|pistols it just wasn't really good 872| 873|219 874|00:06:30,600 --> 00:06:33,440 875|enough to be better than the main 876| 877|220 878|00:06:31,840 --> 00:06:35,320 879|assault rifles which were the Spire 880| 881|221 882|00:06:33,440 --> 00:06:37,080 883|Rifle or the Fury Assault Rifle. 884| 885|222 886|00:06:35,320 --> 00:06:38,840 887|However, the exotic version of this 888| 889|223 890|00:06:37,080 --> 00:06:41,040 891|which was the Unstable Voltage Burst 892| 893|224 894|00:06:38,840 --> 00:06:42,160 895|Pistol had a ton of use in tournaments. 896| 897|225 898|00:06:41,040 --> 00:06:44,000 899|The first and final shot in every 900| 901|226 902|00:06:42,160 --> 00:06:46,160 903|magazine shot a small shockwave effect 904| 905|227 906|00:06:44,000 --> 00:06:48,000 907|which could be used as mobility which 908| 909|228 910|00:06:46,160 --> 00:06:50,240 911|became really strong in competitive 912| 913|229 914|00:06:48,000 --> 00:06:52,080 915|Blitz on mobile as the final zone deals 916| 917|230 918|00:06:50,240 --> 00:06:53,760 919|40 damage per second. So people were 920| 921|231 922|00:06:52,080 --> 00:06:55,560 923|just using this gun to fire people out 924| 925|232 926|00:06:53,760 --> 00:06:57,800 927|into the storm. However, the main broken 928| 929|233 930|00:06:55,560 --> 00:07:00,600 931|pistol from Chapter 6 was of course the 932| 933|234 934|00:06:57,800 --> 00:07:02,120 935|Wrecker Revolver. On close range it was 936| 937|235 938|00:07:00,600 --> 00:07:03,600 939|like a tactical shotgun but by aiming 940| 941|236 942|00:07:02,120 --> 00:07:05,240 943|down the sights the crosshair tightened 944| 945|237 946|00:07:03,600 --> 00:07:06,680 947|and it could be used more like a combat 948| 949|238 950|00:07:05,240 --> 00:07:08,480 951|shotgun or you know, more like a 952| 953|239 954|00:07:06,680 --> 00:07:09,600 955|revolver. By itself it wasn't super 956| 957|240 958|00:07:08,480 --> 00:07:11,680 959|overpowered but because it was 960| 961|241 962|00:07:09,600 --> 00:07:13,680 963|classified as a pistol you could double 964| 965|242 966|00:07:11,680 --> 00:07:14,880 967|pump between this and a shotgun. On 968| 969|243 970|00:07:13,680 --> 00:07:16,960 971|release you could actually double pump 972| 973|244 974|00:07:14,880 --> 00:07:18,800 975|between two Wrecker Revolvers so the 976| 977|245 978|00:07:16,960 --> 00:07:20,560 979|meta was just to carry two of them. But 980| 981|246 982|00:07:18,800 --> 00:07:21,840 983|Epic Games fixed this by adding a delay 984| 985|247 986|00:07:20,560 --> 00:07:23,680 987|when you swap between two Wrecker 988| 989|248 990|00:07:21,840 --> 00:07:24,800 991|Revolvers. It actually added a delay 992| 993|249 994|00:07:23,680 --> 00:07:26,760 995|when switching between the Wrecker 996| 997|250 998|00:07:24,800 --> 00:07:28,160 999|Revolver and any other pistol. And most 1000| 1001|251 1002|00:07:26,760 --> 00:07:29,400 1003|players were carrying the Sentinel Pump 1004| 1005|252 1006|00:07:28,160 --> 00:07:31,000 1007|and then the Wrecker Revolver and 1008| 1009|253 1010|00:07:29,400 --> 00:07:32,880 1011|switching between the two of these. The 1012| 1013|254 1014|00:07:31,000 --> 00:07:34,760 1015|Sentinel Pump deals a ton of structure 1016| 1017|255 1018|00:07:32,880 --> 00:07:37,000 1019|damage. So if you make a bad edit they 1020| 1021|256 1022|00:07:34,760 --> 00:07:38,440 1023|would shoot you. If you made a good edit 1024| 1025|257 1026|00:07:37,000 --> 00:07:39,919 1027|they would just shoot the wall and 1028| 1029|258 1030|00:07:38,440 --> 00:07:41,200 1031|replace it due to the high structure 1032| 1033|259 1034|00:07:39,919 --> 00:07:42,800 1035|damage of the Sentinel Pump. If you 1036| 1037|260 1038|00:07:41,200 --> 00:07:44,520 1039|didn't edit they would just pump the 1040| 1041|261 1042|00:07:42,800 --> 00:07:46,120 1043|wall and then switch to the Recon 1044| 1045|262 1046|00:07:44,520 --> 00:07:47,960 1047|Revolver straight away and the cycle 1048| 1049|263 1050|00:07:46,120 --> 00:07:49,640 1051|would repeat. Even worse, if players did 1052| 1053|264 1054|00:07:47,960 --> 00:07:50,920 1055|edit, they would just 50/50 with you all 1056| 1057|265 1058|00:07:49,640 --> 00:07:52,280 1059|the time because they knew if they had 1060| 1061|266 1062|00:07:50,920 --> 00:07:53,800 1063|good aim, they could just wipe you out 1064| 1065|267 1066|00:07:52,280 --> 00:07:54,680 1067|with a couple of shots with the Sentinel 1068| 1069|268 1070|00:07:53,800 --> 00:07:56,880 1071|and then switching to the Recon 1072| 1073|269 1074|00:07:54,680 --> 00:07:59,520 1075|Revolver. Final broken pistol of Chapter 1076| 1077|270 1078|00:07:56,880 --> 00:08:01,360 1079|6 was the Mr. Meowscles, which was in 1080| 1081|271 1082|00:07:59,520 --> 00:08:03,360 1083|the Simpsons season. Now, this wasn't 1084| 1085|272 1086|00:08:01,360 --> 00:08:04,880 1087|quite as powerful as the Manic Pistol, 1088| 1089|273 1090|00:08:03,360 --> 00:08:06,160 1091|but you could still two-shot someone by 1092| 1093|274 1094|00:08:04,880 --> 00:08:07,680 1095|shooting them in the head. And given 1096| 1097|275 1098|00:08:06,160 --> 00:08:09,320 1099|that this was a hitscan weapon, you 1100| 1101|276 </file-view>

<file-view path="/tmp/t-kXDahZBhk.en-orig.srt" start_line="1102" end_line="1544" total_lines="1544"> 1102|00:08:07,680 --> 00:08:11,440 1103|could just sit and third-party every 1104| 1105|277 1106|00:08:09,320 --> 00:08:13,080 1107|fight from 100 meters away. With every 1108| 1109|278 1110|00:08:11,440 --> 00:08:14,919 1111|body shot hitting for over 50 damage, 1112| 1113|279 1114|00:08:13,080 --> 00:08:16,760 1115|this was really annoying. 1116| 1117|280 1118|00:08:14,919 --> 00:08:18,400 1119|Unsurprisingly, this became the fighting 1120| 1121|281 1122|00:08:16,760 --> 00:08:19,720 1123|meta, similar to the Recon Revolver in 1124| 1125|282 1126|00:08:18,400 --> 00:08:20,880 1127|the previous season, and there probably 1128| 1129|283 1130|00:08:19,720 --> 00:08:22,520 1131|would have been more people complaining 1132| 1133|284 1134|00:08:20,880 --> 00:08:24,040 1135|about this weapon if the season had gone 1136| 1137|285 1138|00:08:22,520 --> 00:08:25,840 1139|on for longer than a month. The exotic 1140| 1141|286 1142|00:08:24,040 --> 00:08:27,800 1143|version of this was also the best weapon 1144| 1145|287 1146|00:08:25,840 --> 00:08:29,160 1147|in that meta as it attached a balloon to 1148| 1149|288 1150|00:08:27,800 --> 00:08:30,400 1151|other players when it was shot near 1152| 1153|289 1154|00:08:29,160 --> 00:08:31,840 1155|them. This meant that you could shoot it 1156| 1157|290 1158|00:08:30,400 --> 00:08:33,320 1159|near someone and just send them into the 1160| 1161|291 1162|00:08:31,840 --> 00:08:34,719 1163|sky and then they were just a free 1164| 1165|292 1166|00:08:33,320 --> 00:08:36,680 1167|target. Or you could shoot it in your 1168| 1169|293 1170|00:08:34,719 --> 00:08:38,320 1171|own box and use it to rotate yourself. 1172| 1173|294 1174|00:08:36,680 --> 00:08:40,640 1175|And Chapter 7 is where the main pistol 1176| 1177|295 1178|00:08:38,320 --> 00:08:41,840 1179|has finally just become meta. Season 1 1180| 1181|296 1182|00:08:40,640 --> 00:08:43,880 1183|was the Tactical Pistol, which is the 1184| 1185|297 1186|00:08:41,840 --> 00:08:46,200 1187|same as Chapter 4. Season 2 was the 1188| 1189|298 1190|00:08:43,880 --> 00:08:48,200 1191|creatively named Pistol, a brand new 1192| 1193|299 1194|00:08:46,200 --> 00:08:50,440 1195|weapon. And then in Season 3, you have 1196| 1197|300 1198|00:08:48,200 --> 00:08:52,400 1199|the Ranger Pistol, the Chapter 5 Pistol. 1200| 1201|301 1202|00:08:50,440 --> 00:08:53,560 1203|However, it is now hitscan. Now, looking 1204| 1205|302 1206|00:08:52,400 --> 00:08:55,400 1207|at the damage, you can see that there's 1208| 1209|303 1210|00:08:53,560 --> 00:08:57,040 1211|been an increase in damage per second of 1212| 1213|304 1214|00:08:55,400 --> 00:09:00,560 1215|these weapons, going from averaging 1216| 1217|305 1218|00:08:57,040 --> 00:09:01,839 1219|around 175 now up to 190 damage per 1220| 1221|306 1222|00:09:00,560 --> 00:09:03,640 1223|second. However, increasing the damage 1224| 1225|307 1226|00:09:01,839 --> 00:09:05,360 1227|per second by around 10% doesn't just 1228| 1229|308 1230|00:09:03,640 --> 00:09:06,960 1231|immediately make these weapons broken 1232| 1233|309 1234|00:09:05,360 --> 00:09:08,720 1235|and the meta. There's a lot more that 1236| 1237|310 1238|00:09:06,960 --> 00:09:11,280 1239|actually goes into it, including 1240| 1241|311 1242|00:09:08,720 --> 00:09:12,720 1243|accuracy. The Semi Auto Pistol has a ton 1244| 1245|312 1246|00:09:11,280 --> 00:09:14,400 1247|of randomness. You can see the crosshair 1248| 1249|313 1250|00:09:12,720 --> 00:09:16,320 1251|gets very large when you start spraying. 1252| 1253|314 1254|00:09:14,400 --> 00:09:17,839 1255|The Semi Auto Suppressed Pistol does not 1256| 1257|315 1258|00:09:16,320 --> 00:09:20,040 1259|have this. It's much more accurate. The 1260| 1261|316 1262|00:09:17,839 --> 00:09:22,400 1263|Sidearm Pistol, as you can see, has tons 1264| 1265|317 1266|00:09:20,040 --> 00:09:23,680 1267|of recoil. Same with the Combat Pistol. 1268| 1269|318 1270|00:09:22,400 --> 00:09:25,280 1271|Same with the Tactical Pistol, just a 1272| 1273|319 1274|00:09:23,680 --> 00:09:26,640 1275|little less. Despite having the lowest 1276| 1277|320 1278|00:09:25,280 --> 00:09:28,200 1279|damage per second, the Hyper Burst 1280| 1281|321 1282|00:09:26,640 --> 00:09:29,480 1283|Pistol is actually insanely accurate. 1284| 1285|322 1286|00:09:28,200 --> 00:09:32,160 1287|But then if you look at the Chapter 7 1288| 1289|323 1290|00:09:29,480 --> 00:09:34,120 1291|Season 2 Pistol, it barely has any bloom 1292| 1293|324 1294|00:09:32,160 --> 00:09:35,320 1295|and any randomness, either. And then 1296| 1297|325 1298|00:09:34,120 --> 00:09:36,600 1299|basically the same thing is true with 1300| 1301|326 1302|00:09:35,320 --> 00:09:38,160 1303|the Ranger Pistol. However, the only 1304| 1305|327 1306|00:09:36,600 --> 00:09:39,600 1307|downside is that it doesn't have first 1308| 1309|328 1310|00:09:38,160 --> 00:09:41,080 1311|shot accuracy, but it basically still 1312| 1313|329 1314|00:09:39,600 --> 00:09:42,480 1315|does cuz it's still incredibly accurate. 1316| 1317|330 1318|00:09:41,080 --> 00:09:44,120 1319|So, despite there being some accurate 1320| 1321|331 1322|00:09:42,480 --> 00:09:45,560 1323|pistols throughout Fortnite's lifespan, 1324| 1325|332 1326|00:09:44,120 --> 00:09:48,040 1327|it's clear older pistols had 1328| 1329|333 1330|00:09:45,560 --> 00:09:49,760 1331|significantly more recoil and spread, 1332| 1333|334 1334|00:09:48,040 --> 00:09:51,520 1335|and the modern chapter 7 pistols are 1336| 1337|335 1338|00:09:49,760 --> 00:09:53,320 1339|easier to hit shots with than ever. 1340| 1341|336 1342|00:09:51,520 --> 00:09:55,280 1343|There's also a very odd meta right now, 1344| 1345|337 1346|00:09:53,320 --> 00:09:56,520 1347|which makes the pistol even better. The 1348| 1349|338 1350|00:09:55,280 --> 00:09:58,560 1351|three different assault rifles, the 1352| 1353|339 1354|00:09:56,520 --> 00:10:01,360 1355|Chaos Exploder, the War forged assault 1356| 1357|340 1358|00:09:58,560 --> 00:10:03,960 1359|rifle, and the surgical burst pistol all 1360| 1361|341 1362|00:10:01,360 --> 00:10:06,040 1363|have worse damage per second than the 1364| 1365|342 1366|00:10:03,960 --> 00:10:08,680 1367|pistol. I mean, the Chaos Exploder's 1368| 1369|343 1370|00:10:06,040 --> 00:10:11,040 1371|damage per second is 85 in comparison to 1372| 1373|344 1374|00:10:08,680 --> 00:10:12,680 1375|189 of the tactical pistol. So, the 1376| 1377|345 1378|00:10:11,040 --> 00:10:14,960 1379|Ranger pistol has the highest damage per 1380| 1381|346 1382|00:10:12,680 --> 00:10:16,800 1383|second at range, is the most accurate 1384| 1385|347 1386|00:10:14,960 --> 00:10:18,320 1387|weapon, and the only weapon to have a 1388| 1389|348 1390|00:10:16,800 --> 00:10:20,080 1391|two times headshot multiplier. [music] 1392| 1393|349 1394|00:10:18,320 --> 00:10:22,200 1395|So, it's unsurprising that it's become 1396| 1397|350 1398|00:10:20,080 --> 00:10:23,800 1399|the meta. I was just about to Thank you. 1400| 1401|351 1402|00:10:22,200 --> 00:10:26,320 1403|I was just about to upload this video, 1404| 1405|352 1406|00:10:23,800 --> 00:10:27,600 1407|and then I saw this. Not the cat. 1408| 1409|353 1410|00:10:26,320 --> 00:10:29,480 1411|Uh there's a mythic now, and I'm sure 1412| 1413|354 1414|00:10:27,600 --> 00:10:31,320 1415|that will be super balanced. However, 1416| 1417|355 1418|00:10:29,480 --> 00:10:33,080 1419|there is one other weapon that's better 1420| 1421|356 1422|00:10:31,320 --> 00:10:35,080 1423|than it in every other way, and that is 1424| 1425|357 1426|00:10:33,080 --> 00:10:36,400 1427|the Lance Head pistol. Now, you might 1428| 1429|358 1430|00:10:35,080 --> 00:10:37,440 1431|have seen a lot of pros carrying this 1432| 1433|359 1434|00:10:36,400 --> 00:10:40,360 1435|recently, and that's cuz it actually 1436| 1437|360 1438|00:10:37,440 --> 00:10:42,680 1439|deals 231 damage per second, which is 1440| 1441|361 1442|00:10:40,360 --> 00:10:44,480 1443|22% higher than the Ranger pistol. The 1444| 1445|362 1446|00:10:42,680 --> 00:10:45,720 1447|main downside of this is that it's not 1448| 1449|363 1450|00:10:44,480 --> 00:10:47,080 1451|automatic. So, when you're looking at 1452| 1453|364 1454|00:10:45,720 --> 00:10:48,440 1455|the damage per second, you do have to 1456| 1457|365 1458|00:10:47,080 --> 00:10:49,960 1459|keep in mind that you have to spam your 1460| 1461|366 1462|00:10:48,440 --> 00:10:51,360 1463|fire button over and over again, making 1464| 1465|367 1466|00:10:49,960 --> 00:10:53,000 1467|it much more difficult to use, and in 1468| 1469|368 1470|00:10:51,360 --> 00:10:54,800 1471|particular, more clunky for box 1472| 1473|369 1474|00:10:53,000 --> 00:10:58,240 1475|fighting. The mythic has a damage per 1476| 1477|370 1478|00:10:54,800 --> 00:10:59,839 1479|second of 269.5. 1480| 1481|371 1482|00:10:58,240 --> 00:11:01,360 1483|At off the top of my head, I genuinely 1484| 1485|372 1486|00:10:59,839 --> 00:11:02,600 1487|don't know if I've seen a weapon that 1488| 1489|373 1490|00:11:01,360 --> 00:11:04,280 1491|has a higher damage per second than 1492| 1493|374 1494|00:11:02,600 --> 00:11:06,080 1495|that. I will edit it in as I'm recording 1496| 1497|375 1498|00:11:04,280 --> 00:11:07,920 1499|this. Almost nobody used this in the 1500| 1501|376 1502|00:11:06,080 --> 00:11:10,200 1503|first week, but all of a sudden, two 1504| 1505|377 1506|00:11:07,920 --> 00:11:11,600 1507|weeks later, tons of the best players in 1508| 1509|378 1510|00:11:10,200 --> 00:11:13,160 1511|the world are using the Lance Head 1512| 1513|379 1514|00:11:11,600 --> 00:11:14,480 1515|pistol. And I imagine this is cuz people 1516| 1517|380 1518|00:11:13,160 --> 00:11:15,920 1519|have realized that they don't get banned 1520| 1521|381 1522|00:11:14,480 --> 00:11:17,560 1523|for macroing the fire button. Now, 1524| 1525|382 1526|00:11:15,920 --> 00:11:19,040 1527|personally, I think that is cheating, 1528| 1529|383 1530|00:11:17,560 --> 00:11:20,720 1531|but if you want to see the evolution of 1532| 1533|384 1534|00:11:19,040 --> 00:11:22,200 1535|cheating in competitive Fortnite, 1536| 1537|385 1538|00:11:20,720 --> 00:11:26,640 1539|because there's a lot, you can click on 1540| 1541|386 1542|00:11:22,200 --> 00:11:26,640 1543|that video on screen right now. Bye. </file-view>

Summary

The video traces the history of pistols in Fortnite and explains how the weapon class went from a weak secondary to the dominant meta, particularly the Ranger Pistol in Chapter 7.

Key points

Chapter 1 semi-auto pistol was intentionally weak: not automatic, with ~169 DPS, meaning it was viable at both close and long range but best at neither. The Hand Cannon in Chapter 1 Season 3 was the first broken pistol, thanks to legacy aim-assist snap-on and 150 structure damage, later nerfed to 95.
Chapter 2 kept the semi-auto pistol but added purple/gold versions. In Chapter 2 Season 3, ARs/SMGs got 1.5× headshot multipliers while pistols kept 2×, making pistols the best headshot weapon. Pro player King won FNCS solo finals maining a pistol, largely by using a fire-rate macro.
Chapter 4 introduced the first automatic pistol, the Tactical Pistol, which had low DPS but tight spread and low recoil, making it the first truly viable main pistol. The Mammoth Pistol then became oppressive: a slow, heavy, hitscan weapon that let players ping 100-damage body shots from far away.
Chapter 5 fixed hitscan sniping by adding bullet drop. The Ranger Pistol debuted but wasn't meta because ARs and SMGs outclassed it. The Monarch Pistol was a toned-down, more skillful Mammoth Pistol.
Chapter 6 introduced the Hyper Burst Pistol and Kill Switch Revolvers, plus the Wrecker Revolver, which could be double-pumped with a shotgun, creating a dominant close-range combo. The Mr. Meowscles pistol in the Simpsons season could two-shot headshot at range despite being hitscan.
Chapter 7 is where pistols became meta. Damage per second rose from the historical ~175 to ~190, and modern pistols (Tactical, Season 2 Pistol, Ranger) have far less bloom and recoil than older pistols. Current assault rifles like the Chaos Exploder (85 DPS) and Warforged AR are weaker than the Ranger Pistol, which is also the most accurate weapon and the only one with a 2× headshot multiplier.
The video ends by noting the Lance Head Pistol is technically even stronger, dealing 231 DPS (269.5 DPS for the mythic), but is not automatic. The speaker claims pros are now using it via fire-button macros, which they consider cheating.