Hood Warfare 2 Settings: Test a Creator Preset on Your PC

Which parts of a creator preset should you copy first?

Start with a reversible baseline and a question you can compare: is aiming too twitchy, is the image hard to read, or does a repeated scene run poorly? A single preset tries to answer several questions at once. Applying it wholesale makes it difficult to identify which change helped.

We reviewed the readable English automatic captions and publisher metadata of IchibanThug Gaming’s October 12, 2026 settings video on October 22. The video is a useful original source for what its author recommends. We did not inspect its frames or reproduce its results in a game client, so this article does not certify current menu labels, factory defaults or measured performance gains.

How should you compare mouse and controller sensitivity?

At approximately 0:17–0:31, IchibanThug Gaming describes his mouse and zoom sensitivity choices as aiming preferences. Around 1:03–1:16 he gives a rough controller suggestion, and at 2:03–2:15 explains that he mainly uses keyboard and mouse and plans to test the controller further. That distinction matters: the controller advice is provisional even within this source.

Our comparison method is to keep mouse DPI, resolution and input device fixed while repeating a simple aiming task, then adjust one sensitivity field. For a controller, keep the same device and compare ordinary movement separately from aiming down sights. Record whether you overshoot or undershoot a target. The source does not provide the complete controlled inputs needed to convert its preference into your ideal value.

Do not treat an unfamiliar feeling after thirty seconds as a benchmark. Restore the baseline if a change makes the task harder, and keep a short note about the same repeat task. The goal is a usable personal setting rather than matching another player’s number.

Reference: IchibanThug Gaming · Hood Warfare 2 settings video ↗

How can you use the graphics advice without promising extra FPS?

At roughly 2:39–2:50 the creator discusses field-of-view preference; around 3:50–4:18 he suggests reducing selected graphics categories on a struggling PC. These are dated recommendations, not an A/B benchmark with a published frame-time dataset. An option named in the recording also needs checking in your installed version.

Choose one repeatable scene and record the baseline before making a graphics change. Keep resolution, camera route and session type fixed as far as practical. Compare both motion and image readability, not just an impression that one screenshot looks sharper. If you use an FPS or frame-time tool, identify it and retain the observations rather than inventing a percentage gain.

Changing field of view also changes how the same scene appears. Compare that choice separately from a quality setting when possible. A scene crowded with different players is a weaker controlled comparison than a repeatable route; record that limitation when online conditions are unavoidable.

Reference: IchibanThug Gaming · Hood Warfare 2 settings video ↗

Should you also copy the creator’s audio choices?

Audio serves a different goal from graphics. A creator who wants a stream without unwanted music or in-game conversation may make choices that are unsuitable for someone trying to hear friends. Treat content-production preferences separately from a microphone fault or missing speaker output.

Before changing everything, ask whether effects and music work, whether Windows records your microphone and whether a friend hears you in the intended channel. Keep one device and one consenting friend for a short comparison. Turning a feature off can hide its symptom without showing that the underlying problem is repaired.

What should a useful personal preset record contain?

Save the game version and date, PC or controller details, the baseline values, the single change and the task you repeated. Add what became easier and what trade-off appeared. That record makes the result useful next session and lets you recognize a meaningful difference after an update.

For a public contribution, separate your observed result from your explanation of its cause. Include an original capture or measurement method when you have one, and redact private information. A reproducible personal comparison contributes more than another unsourced claim that a preset is best for every player.