Peterbot Settings 2026: Fortnite Sensitivity, Binds and Gear

Peterbot settings get searched every time Falcons Esports takes the stage, and for good reason. As one of Fortnite’s most mechanically consistent players, his configuration reflects years of refinement around building speed, editing precision and clean aim tracking.

Peterbot plays on 800 DPI with 6.4% x/y sensitivity, giving him an eDPI of roughly 51.2, paired with a 240 FPS cap and windowed fullscreen display mode. Every part of his setup, from his SteelSeries Apex Pro TKL Gen 3 keyboard to his DX11 performance rendering mode, is built around minimizing input delay while keeping his edits and builds fast under pressure.

Here’s a quick snapshot of his core settings before the full breakdown:

Setting Value
DPI 800
X/Y Sensitivity 6.4%
eDPI ~51.2
Targeting/Scope Sensitivity 45%
Build/Edit Sensitivity 100%
Polling Rate 1000 Hz
Resolution 1920×1080
Frame Rate Cap 240 FPS
Rendering Mode DX11 Performance (Legacy)

Pro settings shift often as players patch-test new metas and gear, so treat this as a current snapshot rather than a permanent config.

What Mouse Sensitivity Does Peterbot Use?

Peterbot runs 800 DPI with 6.4% x-axis and y-axis sensitivity in Fortnite, which works out to an eDPI near 51.2. That number sits in the middle of the range most competitive Fortnite players use, and it gives him enough precision for close-range fights without sacrificing the fast flick speed needed for editing and building.

DPI, Polling Rate and X/Y Sensitivity

His mouse DPI is set to 800, confirmed through his mouse software across multiple gear updates. Polling rate stays at 1000 Hz even on mice that support up to 8000 Hz, since a lower polling rate reduces CPU load and keeps input timing more consistent during intense fights. Both x-axis sensitivity and y-axis sensitivity are locked at 6.4%, matched exactly rather than offset between axes.

Targeting, Scope

Targeting sensitivity and scope sensitivity are both set to 45%. This lower value compared to his base sensitivity gives him steadier tracking while aiming down sights or looking through a sniper scope, which matters for holding angles during endgame fights.

Build and Edit Sensitivity

Build sensitivity and edit sensitivity are both left at the default 100%. Many players push edit sensitivity far higher, expecting faster edits, but Peterbot keeps it at default because a jump in sensitivity breaks muscle memory built over years of repetition.

How to Calculate His 51.2 eDPI

eDPI is calculated by multiplying DPI by in-game sensitivity: 800 DPI times 6.4% (0.064) equals 51.2 eDPI. This figure lets players on different DPI settings match his exact mouse feel. Someone running 400 DPI, for example, would need a 12.8% in-game sensitivity to reach the same 51.2 eDPI and replicate his aim speed.

Peterbot’s Video and Graphics Settings

Peterbot plays on windowed fullscreen at 1920×1080 with a 240 FPS cap, DX11 legacy performance rendering, and Nvidia Reflex Low Latency enabled. His graphics settings prioritize frame stability and visibility over visual fidelity, a common pattern among top-tier competitive players.

Display Mode

He runs windowed fullscreen rather than exclusive fullscreen, since it allows faster alt-tabbing to check Discord or stream chat between matches. He pairs this with the windowed-mode optimization setting in Windows graphics settings, which keeps input latency nearly identical to true fullscreen.

Resolution and 240 FPS Cap

His native resolution is 1920×1080 at a 16:9 aspect ratio. His frame rate cap sits at 240 FPS to mirror the FPS cap enforced at LAN events, even when his hardware could push higher.

Rendering Mode

Peterbot uses Legacy Performance Mode with DX11 rather than DX12. This rendering mode consistently delivers higher FPS and lower latency on his Nvidia-based system compared to the newer DirectX 12 performance path.

3D Resolution and Graphics Quality

3D resolution is set to 100% to avoid the pixelation that comes from scaling it down. Textures and meshes are both set to low, which boosts FPS and gives builds a cleaner break animation. View distance has varied between near and far depending on the season, since it affects how far items and structures render without a meaningful FPS cost.

Visibility, HUD and NVIDIA Settings

Brightness is maxed at 150% to improve visibility through builds and in darker areas of the map. HUD scale sits at 90%, and Nvidia Reflex Low Latency is turned on to cut the delay between mouse input and the frame appearing on screen. Digital vibrance and monitor settings on his Zowie display are tuned toward reduced motion blur and ghosting rather than color saturation.

Which Keybinds Does Peterbot Use?

Peterbot’s keybinds are built around a claw-style grip that keeps his fingers close to WASD while giving constant scroll-wheel access for building and looting. He plays on a SteelSeries Apex Pro TKL Gen 3, using its adjustable actuation to fine-tune key response on a per-key basis.

Movement and Combat Binds

Crouch is bound to C, jump to Spacebar, and sprint is on the backtick (`) key. Pickaxe is on Mouse Button 4, and interact/pickup is bound to both E and scroll wheel up, which lets him win close chest and loot races.

Building, Editing and Scroll-Wheel Binds

His building binds use T for wall, F for stairs, Y for floor, V for roof, and R for trap. Edit is bound to G, and scroll wheel down is mapped to reset edit, a technique known as scroll wheel reset that lets him cancel and reconfirm edits mid-fight without pressing a separate key. Auto Confirm Edits is set to “Edit,” which functions as edit-on-release and speeds up his overall edit speed considerably.

Peterbot’s Mouse, Keyboard and PC Gear

Peterbot’s gear centers on the Logitech G Pro X2 Superstrike Lunar Eclipse mouse, a SteelSeries Apex Pro TKL Gen 3 keyboard, and a Zowie XL2566K monitor, backed by a high-end PC built around an AMD Ryzen 7 9800X3D and Nvidia GeForce RTX 4090. This combination reflects a setup tuned for minimal input latency and maximum frame stability rather than raw visual horsepower.

Mouse, Mousepad and Keyboard

His mouse has shifted between the Logitech G Pro X Superlight 2 and the Logitech G Pro X2 Superstrike Lunar Eclipse depending on the season, both configured at 800 DPI with stock skates and no added grip tape. He uses the Gamesense Radar Benjyfishy 2 mousepad. His keyboard is the SteelSeries Apex Pro TKL Gen 3 (Black), chosen partly because its TKL layout preserves his sprint bind position relative to a full-size or 60% layout. Readers exploring similar low-latency mice can compare options in a broader gaming mouse guide before committing to a specific model.

Monitor, Headset and PC Components

His monitor is the Zowie XL2566K, a competitive-grade display used at recent FNCS LAN events. For audio, he runs the HyperX Cloud III, with sound quality set to high to make footsteps easier to isolate. His PC is built around an AMD Ryzen 7 9800X3D processor and an Nvidia GeForce RTX 4090 graphics card, a pairing capable of holding a stable 240 FPS cap with headroom to spare.

How to Adapt Peterbot Settings to Your Setup

Peterbot settings work best as a reference point rather than a copy-paste solution, since eDPI, refresh rate and polling rate all need to align with the gear already on a reader’s desk. The goal is matching his mouse feel and responsiveness within the limits of your own hardware, not replicating every value exactly.

Match Mouse Feel Without Changing Your DPI

Keep your mouse at whatever DPI it performs best at and adjust in-game sensitivity to land near the same 51.2 eDPI. If your mouse is set to 400 DPI, a 12.8% sensitivity produces the same cm/360 as Peterbot’s 800 DPI and 6.4% combination. This avoids the tracking inconsistency that comes from changing DPI on a mouse sensor that wasn’t tuned for it.

Prioritize Stable Frames and Comfortable Binds

Cap your frame rate at whatever your monitor’s refresh rate supports rather than blindly copying 240 FPS, since an uncapped or mismatched frame rate can introduce screen tearing without Vsync. For binds, copy the logic (scroll wheel for pickup and reset, dedicated single-press building keys) rather than his exact key choices, since hand size and keyboard layout affect what’s comfortable to reach.

Use His Setup as a Starting Point

Peterbot’s setup reflects a build focused on low latency, consistent tracking and fast editing rather than raw specs for their own sake. His 800 DPI and 6.4% sensitivity, 240 FPS cap, and Apex Pro TKL Gen 3 keybinds all serve a competitive playstyle built around beating opponents to loot and resetting builds instantly mid-fight.

Copying his exact Fortnite settings won’t replicate his mechanical consistency on its own, since years of repetition built that muscle memory. Testing his sensitivity and rendering choices against your own gear, then adjusting keybinds to your hand size and grip, gets you closer to a setup that actually performs well in your matches.

Frequently Asked Questions

What settings does Peterbot use in Fortnite?

Peterbot plays at 800 DPI with 6.4% x/y sensitivity, 45% targeting and scope sensitivity, and 100% build and edit sensitivity. His video settings include windowed fullscreen, a 240 FPS cap, and DX11 Legacy Performance rendering mode.

What is Peterbot’s sensitivity at 800 DPI?

At 800 DPI, Peterbot runs 6.4% in-game sensitivity, producing an eDPI of approximately 51.2. That gives him a balance between precise aim and fast turning speed.

How does Peterbot edit so fast?

His fast editing comes from a combination of Auto Confirm Edits set to “Edit” (edit-on-release), scroll wheel reset bound to scroll down, and a light keyboard actuation point on his edit key. Disable Pre-Edits is also turned on, which keeps his edits clean during fast-paced fights.

What refresh rate does Peterbot use?

Peterbot caps his frame rate at 240 FPS to match his monitor and to mirror the frame rate limits enforced at LAN tournaments. His Zowie XL2566K monitor supports refresh rates well above this, but he sticks to 240 FPS for consistency between practice and competition.

Does Peterbot use a custom crosshair in Fortnite?

Peterbot does not use a custom crosshair overlay in Fortnite itself, relying on the game’s default reticle with ammo indicator and spread display enabled. Any crosshair-style overlay associated with him has been used for inventory organization rather than in actual gunfights.

Browse every documented setup in our pro player settings library.

Setting up Fortnite yourself? Start with our Fortnite settings and gear guide.


About the Author

Artistic eye within a triangle symbol, representing creativity and focus.

Dan was initially only focused around gaming reviews and other content back in 2019ish on this platform. Since then he has decided to focus on the hardware and software side of things instead of just the games themselves. He has been focused on PC gaming and wants to give back to his community as much as possible.