DEV Community: ALVIRAN

A Technical VALORANT Anti Flash Workflow Checklist for Ranked Play

ALVIRAN — Mon, 20 Jul 2026 23:02:20 +0000

A flash does not create an automatic loss. Most failed anti-flash reactions happen because the player has not decided what information should trigger a turn, a hold, or a teammate call. Treating every audio cue the same creates random movement and exposes the team to the second player behind the utility.

This technical workflow keeps the response consistent: use the same settings, record the pattern, and review it after a ranked session instead of changing the reaction every round.

Practical checklist before the fight

Before a round starts, identify the locations where a flash is most likely to arrive and agree on the response. The rule should be specific enough to execute under pressure. For example, one player holds the swing while the other turns, or both players fall back to a known crossfire.

A useful routine includes:

Identify the likely flash path before contact.
Decide which player keeps vision on the angle.
Turn only when the cue and position make sense together.
Call whether the enemy can follow the flash immediately.
Reset the crossfire before taking another duel.

Separate the cue from the decision

A flash sound is information, not an instruction. Some flashes are used to force attention, while others are paired with an instant swing. The difference is usually visible in spacing, timing, and the amount of map control the attacking team already owns. A quick verbal call makes the response much more reliable than two players reacting independently.

Review the mistake after the round

When a flash leads to a lost duel, review the sequence instead of blaming the reaction speed. Did the team give up an angle for free? Did both players turn? Was the follow-up player already expected? These questions produce repeatable corrections.

ALVIRAN's VALORANT anti-flash guide breaks down the common flash situations, practical counterplay, and the calls that keep a defense connected. The goal is not to avoid every blind. It is to make the next decision predictable.

How to Build a Reliable VALORANT Performance Baseline on Windows

ALVIRAN — Sun, 19 Jul 2026 22:09:49 +0000

A PC can satisfy the published requirements for VALORANT and still produce an inconsistent match. Hardware tiers answer whether a system belongs in a broad performance class. They do not account for thermal throttling, power limits, background software, driver state, resolution, or the moments when several abilities appear on screen together.

A useful setup process therefore needs two stages: verify compatibility, then measure stability.

What should you verify before testing FPS?

Start with the complete system rather than comparing only the graphics card. Check:

The exact CPU and GPU models, not just their product families.
The installed RAM and whether Windows has enough headroom for other applications.
A supported 64-bit Windows version and the required security configuration.
DirectX, graphics drivers, available storage, and current power settings.
Laptop charging state, cooling behavior, and performance mode where applicable.

ALVIRAN's VALORANT PC requirements guide lists the current minimum, recommended, and high-end tiers and separates official requirements from practical planning advice. Use that table as the compatibility reference before changing graphics settings.

How to create a repeatable test

Randomly changing several settings after one bad round does not produce useful data. Build a small technical workflow:

Restart the PC and close applications that are not part of the normal play session.
Record the Windows version, driver version, resolution, display mode, and graphics preset.
Set a consistent FPS cap or test target that matches the monitor and hardware goal.
Play the same type of scenario for a fixed period instead of comparing unrelated matches.
Record average FPS, visible frame drops, temperature behavior, and any background task spikes.
Change one variable, repeat the test, and compare the result.

The goal is not to produce the largest number in an empty scene. The goal is to keep input and frame delivery predictable when a real round becomes busy.

Why average FPS is not enough

Two systems can report the same average while feeling completely different. Short frame-time spikes can create visible stutter even when the average remains high. Monitor the moments when performance drops: the start of a fight, heavy utility, a new area loading, or a background application becoming active.

If the issue appears after several minutes, inspect temperatures and clock behavior. If it appears only while streaming or using voice software, test memory, CPU, and encoder load with those applications enabled. The baseline should represent how the PC is actually used.

Common performance mistakes

Avoid these shortcuts:

Comparing a laptop GPU directly with a desktop part that has the same name.
Assuming more RAM automatically fixes a CPU or thermal bottleneck.
Updating every driver and setting at once, then losing the ability to identify the useful change.
Treating peak FPS as proof of a stable competitive setup.
Ignoring Windows security requirements because the hardware appears fast enough.

A reliable baseline is deliberately boring: documented settings, one controlled change, and a repeatable test. Once the system is stable, optimization becomes measurable instead of guesswork.

A Practical Privacy Audit for VALORANT Players and Streamers

ALVIRAN — Sun, 19 Jul 2026 11:12:11 +0000

Privacy in an online game is not a single switch. A display-name setting can reduce what other players see during a match, while a tracker connection, stream overlay, friend list, or recovery detail can expose information through a completely different surface. A useful privacy setup starts by separating presentation controls from account security.

What should a VALORANT privacy audit check?

The audit should answer four questions:

What identity information appears to players outside the party?
What information appears on the local screen during a stream or recording?
Which profile details remain visible through connected services?
Which sensitive details are being shared manually in screenshots or chat?

ALVIRAN's VALORANT privacy settings guide maps the current in-game controls and explains their limits. The important word is limits: hiding a Riot ID in a match does not rename the account, remove tracker data, or protect credentials.

Step 1: reduce unnecessary in-match exposure

Review the privacy controls that affect names and incoming requests. For many players, the useful baseline is to hide their name from players outside the party, display generic names locally, and reject unwanted friend requests automatically. Account Level visibility is controlled separately, so inspect the Player Card and Level Border settings instead of assuming the name controls cover it.

After changing a setting, test it in the context that matters. A streamer should record a short private test and inspect the resulting video. A normal player can check what appears before, during, and after a match. Verification is more reliable than trusting a label.

Step 2: audit connected services

Third-party statistics sites and approved sign-in connections may have their own visibility controls. Check each service directly:

List the services connected to the account.
Confirm which profile or match data each service displays.
Use the service's privacy or deletion controls where necessary.
Remove connections that are no longer used.
Recheck the public profile after the change propagates.

This is a technical workflow, not a one-time checkbox. The game client and an external service control different data surfaces.

Step 3: protect the stream itself

A privacy setting cannot hide information placed in an overlay, browser tab, desktop notification, voice call, or screenshot. Before streaming, close unnecessary applications, disable notification previews, inspect overlays, and avoid opening account pages on screen. Use a separate scene for transitions that might expose the desktop.

Common privacy mistakes

The most common mistake is confusing privacy with security. Privacy controls reduce visibility. Security controls protect access. Unique credentials, multi-factor authentication, protected recovery details, and careful handling of backup codes remain separate requirements.

A second mistake is assuming the setup is permanent. Game interfaces, connected services, and streaming tools change. Repeat the audit after a major client update, a new tracker connection, or any change to the broadcast setup.

The goal is not to become invisible. It is to understand which system reveals each piece of information and remove exposure that serves no useful purpose.

A Technical Workflow for Vertical Destruction in Rainbow Six Siege

ALVIRAN — Sat, 18 Jul 2026 21:55:53 +0000

Soft destruction in Rainbow Six Siege is easy to misunderstand. More holes do not automatically create more pressure. Every opening changes the map for both teams, reveals information, and can expose the attacker who made it. The useful question is not how much floor can be destroyed. It is what the team can do after one specific opening exists. This technical workflow turns that question into a repeatable setup.

How to define the breach objective

Before opening a floor or wall, identify the exact outcome the breach should create. A controlled Sledge route normally has one of four jobs:

Remove a defender gadget that blocks the execute.
Force an anchor away from a protected position.
Create a crossfire for a teammate on the lower floor.
Deny a plant or rotation line that defenders need later.

If none of those outcomes is available, the breach is probably noise rather than progress. ALVIRAN's R6 Sledge route guide covers the operator, loadout choices, vertical routes, rappel openings, and the practical risks around each swing.

Practical workflow: use the smallest useful opening

Large sections of destroyed floor look powerful, but they also create more angles to watch. A smaller opening is easier to understand and easier for a teammate to use. Start with the line that exposes the known position or utility item. Expand only when the defender moves and the new information justifies another opening.

A repeatable sequence looks like this:

Drone the room below and name the target.
Secure the staircase, doorway, or flank that reaches the vertical player.
Open the minimum amount of surface needed for the first line.
Assign a teammate to use or trade the pressure immediately.
Reassess instead of continuing the old pattern automatically.

Why sound is part of the system

The hammer announces the attacker's location. Defenders can leave the target position, challenge the route above, or wait for the breach animation. This makes timing important. Vertical play is strongest when the lower-floor player is already prepared to move as the opening appears. A hole made too early gives the defense time to adapt; a hole made without cover can turn the Sledge player into an isolated target.

How to measure execution performance

After the round, review whether the breach produced a useful action. Did it clear utility? Did the defender move? Did a teammate gain a safer entry or plant line? If the answer is no, change the target or timing next round instead of creating more destruction.

The core principle is simple: controlled destruction should reduce uncertainty. One deliberate opening that creates a playable next step is more valuable than an entire floor of angles nobody owns.

A Reproducible Workflow for VALORANT Custom Game Testing

ALVIRAN — Fri, 17 Jul 2026 23:32:37 +0000

Custom games are one of the most useful testing environments in VALORANT, but only when the session has a clear purpose. Opening a lobby and changing random options rarely produces knowledge that transfers into a real match. A repeatable setup is more valuable: define the question, control the conditions, record the result, and test it again.

Start with one testable question

A useful session begins with a narrow goal. You might want to confirm a lineup, compare two movement routes, measure an ability timing, or understand how an angle changes from a different elevation. Test one variable at a time. If the agent, position, ability, and route all change together, the result is difficult to trust.

ALVIRAN's VALORANT custom game commands and setup guide explains the available practice controls and how to prepare a private testing lobby. These are custom-game tools for controlled practice, not shortcuts for live matches.

Build a repeatable baseline

Before each test, keep the important conditions consistent:

Use the same map and starting position.
Reset the round state before a new attempt.
Change only one setting or action at a time.
Repeat successful results instead of trusting a single attempt.
Write down the setup if another player should reproduce it.

This turns a vague practice session into a small experiment. The result becomes easier to explain, share, and verify.

Separate discovery from execution

The first phase is discovery: explore the map, test timing windows, and find a setup that appears useful. The second phase is execution: repeat the same setup without assistance until it feels natural. Mixing both phases can create false confidence. A lineup that works once in a relaxed practice lobby is not automatically usable during a pressured round.

Test the real constraint

A good practice setup should include the limitation that matters in a match. If a lineup requires perfect positioning, test how quickly that position can be reached. If a route depends on utility, test the economy and timing around it. If an angle works only against a stationary target, add realistic movement to the test.

Why reproducibility matters

Reliable practice saves time. It also makes team communication clearer because every player can follow the same steps and compare the same result. The value of custom-game controls is not that they remove difficulty. Their value is that they make learning measurable.

A Technical Checklist Workflow for R6 Voice Chat Issues

ALVIRAN — Fri, 17 Jul 2026 08:31:52 +0000

Voice chat issues in Rainbow Six Siege are frustrating because they look simple from the outside. The mic is either working or it is not. In practice, the problem can sit in the input device, platform permissions, party channel, game channel, privacy settings, or a stale client state.

Problem: random fixes make audio bugs harder to debug

The common mistake is changing every setting at once. A player toggles Windows input, console privacy, push-to-talk, Discord, party chat, and in-game voice settings in one session. If the mic starts working, they still do not know what fixed it. If it does not work, the setup is now harder to understand.

ALVIRAN's technical R6 voice chat and mic troubleshooting checklist gives players a cleaner order before they start changing settings.

Checklist: isolate the audio path

A useful review should move in this order:

Confirm the correct input device is selected.
Check platform privacy and voice permissions.
Separate party chat from in-game team chat.
Restart after one meaningful change, not after every guess.

This keeps the test readable. If one step works, the player knows what mattered. If it fails, they can move forward without creating more confusion.

Workflow: keep communication ready before ranked

Voice chat is not just a comfort feature in R6. It affects rotates, droning, flank calls, utility timing, and late-round trades. A broken mic can make a good player look disconnected from the team. That is why audio checks belong before ranked, not after the first lost match.

FAQ: why this matters for ALVIRAN readers

ALVIRAN readers often care about account quality, ranked readiness, and long-term progression. Communication is part of that experience. A clean technical setup makes every account feel more reliable because the player can focus on decisions instead of fighting basic audio problems.

A Technical Checklist Workflow for VALORANT Ranked Progress

ALVIRAN — Thu, 16 Jul 2026 11:41:49 +0000

Ranked improvement gets messy when players only look at the last result. A win can hide bad habits, and a loss can still contain a good process. The better workflow is to review what the match actually changed: decisions, economy, role discipline, account consistency, and the kind of rounds that keep repeating.

Problem: ranked feels random when the data is vague

Before changing your aim routine or agent pool, make sure you understand what the ranked screen is telling you. RR movement, visible rank, hidden performance signals, party rules, and streaks can all make progress feel less linear than it really is. That is why a simple review should begin with the system itself, not with blame.

Use ALVIRAN's technical VALORANT ranked guide for RR, MMR, and rank review as the baseline before changing your routine.

Checklist: review the match in four layers

Use the same order every time so the review stays objective:

Did the team enter rounds with a clear buy plan?
Did your role create value before the first duel?
Did deaths happen while trading, gathering information, or taking isolated fights?
Did post-plant or retake decisions match the numbers advantage?

This structure keeps the review focused on repeatable causes. If the same issue appears across several games, it becomes a training target. If it happens once, it is probably just noise.

Workflow: turn the review into one next action

The mistake most players make is trying to fix five things at once. Pick one ranked habit for the next session: cleaner bonus rounds, fewer dry peeks, better utility timing, stronger anti-eco discipline, or more patient post-plant positioning. One change is easier to measure, and measurement is what makes ranked progress feel less random.

FAQ: what should ALVIRAN readers measure first?

Start with the ranked system, then the round pattern, then the account context. A ranked account, a skin collection, or a long-term main account is easier to evaluate when the surrounding game systems are explained in plain language. For ALVIRAN, this kind of content builds trust because it helps competitive players and buyers make calmer decisions instead of reacting to one frustrating match.

A Data Integrity Workflow for Reviewing VALORANT Purchase History

ALVIRAN — Wed, 15 Jul 2026 12:49:51 +0000

Purchase history is useful when it is treated as one input in an account review, not as automatic proof of ownership or security. A receipt can explain a transaction. It cannot prove that the current email, recovery path, connected services, and login sessions are clean.

This workflow separates billing evidence from account-control evidence and keeps sensitive data out of public screenshots.

Checklist: collect the minimum useful data

Start with the account's own Riot and payment records. Do not use random purchase-history checkers or send credentials to someone offering to inspect the account.

Confirm that you are signed into the intended Riot account.
Record the item, date, VP amount, and payment route relevant to the question.
Keep full transaction IDs, email addresses, and payment details private.
Compare the record with the visible inventory only when that comparison is necessary.
Save the original receipt privately if a support case may be required.

The goal is not to collect every possible field. It is to preserve enough evidence to explain a purchase without creating a second security problem.

What purchase history can validate

A consistent record can help explain where VP came from, when an eligible skin was purchased, which payment route handled the transaction, and what evidence may be available for a refund or support request. It can also reveal obvious inconsistencies between a claimed purchase story and the account state.

That makes purchase history valuable as a data-consistency check. It is not a security verdict. Screenshots can be old, cropped, or detached from the account currently being reviewed.

Keep billing and account security separate

Review billing evidence on one track and access control on another. The security track should cover the current email, unique password, MFA, recovery options, connected accounts, trusted devices, and unexpected login notifications. Passing the billing track does not compensate for failing the security track.

This separation also improves support requests. Instead of sending a large bundle of unrelated screenshots, describe the transaction problem, include only the relevant record, and use Riot's own support route.

Decision workflow

Identify the exact question: refund, missing VP, unknown charge, or ownership context.
Open the relevant first-party account or payment record.
Redact information that is not required for the decision.
Compare the record with the current inventory and account state.
Escalate through Riot Support when the evidence does not explain the issue.

The ALVIRAN VALORANT purchase-history and receipts guide expands this workflow with privacy boundaries, consistency checks, and common receipt mistakes.

A State Based Workflow for Responding to VALORANT At Risk Alerts

ALVIRAN — Tue, 14 Jul 2026 21:00:46 +0000

A VALORANT At-Risk indicator should be treated as a state that needs investigation, not as proof of an automatic game ban. The useful response is to read the live client, classify the displayed status, and correct the underlying behavior without trying to bypass enforcement.

Checklist: inspect the current account state

Before queueing again, perform a short review:

Open the Social Panel and locate the Behavior Standing indicator.
Expand the indicator instead of relying on an old screenshot.
Record whether it shows a warning, active restriction, or game ban.
Check which queues or communication features are currently available.
Review account security separately from behavior standing.

This keeps three different problems from being collapsed into one vague label.

What each state means

An At-Risk Alert warns that a future behavior penalty is close. It calls for an immediate change in play and communication, but it is not automatically a suspension.

An active restriction means a specific feature is already limited. Voice, text, team queues, Competitive, or another feature may be unavailable for the duration displayed by the client.

A game ban is a more serious enforcement state that blocks play. It should never be described as a routine warning.

How to respond without making the situation worse

Stop the behavior connected to the warning. Finish matches, avoid AFK activity and unnecessary dodges, keep communication clean, and do not attempt to evade a restriction through another account or unofficial tool. Anyone promising instant alert removal is selling a shortcut that cannot replace Riot's displayed status.

If the indicator is unclear, capture the exact wording and time before contacting Riot Support. Specific evidence is more useful than saying the account is simply broken.

Keep behavior and security as separate checks

A clean Behavior Standing does not prove that email access, recovery settings, region, or login security are healthy. Likewise, a warning does not automatically mean the account is compromised. Treat enforcement state and account security as separate diagnostic tracks.

The complete ALVIRAN VALORANT At-Risk Alert workflow includes the status ladder, buyer checklist, and escalation guidance.

A Risk Based Checklist for Evaluating VALORANT Trackers and Overlays

ALVIRAN — Tue, 14 Jul 2026 07:08:05 +0000

Third-party VALORANT tools are often grouped under one label, but a public statistics page, a desktop overlay, a shop checker, and a private executable do not carry the same risk. A useful review starts with behavior, not branding.

Checklist: evaluate a VALORANT tracker before installing it

Before installing a tracker or overlay, verify all five points:

The download comes from the developer's official source.
The service does not request your Riot password directly.
Its data access is public, authorized, or clearly explained.
It supports review instead of automating live decisions.
You know how to remove it if Vanguard or Windows behaves differently.

1. Identify what the tool actually does

Post-match statistics, long-term trends, agent performance, and VOD notes are fundamentally different from live tactical prompts. The closer a tool gets to changing decisions during a round, exposing hidden information, automating inputs, or reading game memory, the more cautious you should be.

2. Check how it handles identity

A normal analytics service should not need your Riot password. Prefer transparent opt-in account linking and public or authorized data. Treat any random website, Discord bot, or private checker that directly requests login credentials as a hard stop.

3. Inspect the source and distribution path

Download desktop software only from the developer's official page or a trusted platform. Re-uploaded installers, private builds, macros, spoofers, and tools advertised as undetectable remove the trust signals needed for a sensible review.

4. Separate review from live assistance

A clean use case helps you understand a match after it ends. A risky use case provides live timers, enemy scouting, hidden data, or automatic calls while the round is active. An informational overlay can still become a problem when it blocks important UI or turns into decision automation.

5. Define an exit condition before installing

If the app triggers Vanguard errors, behaves differently from its documentation, adds unexplained background processes, or makes you unsure about account safety, remove it through normal Windows settings and restart before playing ranked again. Do not solve one questionable installation by downloading another unofficial fix.

The practical rule is simple: use reputable tools for review, protect credentials, avoid live advantages, and judge every feature by the access it requires. Continue with the full ALVIRAN VALORANT tracker safety checklist for the detailed risk table and installation checks.

A Controlled Workflow for Testing VALORANT HRTF and Footstep Clarity

ALVIRAN — Mon, 13 Jul 2026 18:06:57 +0000

A Controlled Workflow for Testing VALORANT HRTF and Footstep Clarity

VALORANT audio settings are easy to overcomplicate. A player enables HRTF, adds headset surround, boosts an EQ preset, raises voice chat, and then has no idea which layer made footsteps clearer or worse. The useful approach is a small controlled test, not a copied magic volume number.

ALVIRAN uses this workflow to separate output problems from processing choices and actual in-game awareness. The goal is directional clarity without masking footsteps behind abilities, music, or team comms.

Why stacked audio processing fails

HRTF is designed to support positional audio with a stereo configuration. Adding another virtual-surround layer can widen or smear the same cues. Different headsets also react differently, so a setting that feels precise for one player may sound hollow or doubled for another.

Start from a known baseline. Confirm that VALORANT uses the intended output device and that Windows has not switched to another headset profile. Only then should you compare HRTF states.

How to run a repeatable HRTF test

Select the correct output device in Windows and VALORANT.
Disable extra virtual surround and begin with clean stereo.
Balance voice chat so calls remain clear without masking movement.
Enable HRTF while keeping every other setting unchanged.
Repeat the same route in a custom game or several deathmatches.
Record whether front, rear, vertical, and diagonal cues become easier to place.

Use the same headset position and a comfortable fixed volume. Do not judge the result from one chaotic round. A repeatable route gives you comparable information; a random team fight does not.

Common failure signs

Muddy or doubled footsteps usually suggest stacked processing. Missing sound can come from the wrong output device or Windows mixer. Clear direction but poor awareness may instead be a gameplay problem: late reactions, loud comms, or attention locked on the crosshair. Audio settings cannot solve every missed cue.

Practical decision checklist

Keep HRTF when direction feels more consistent across repeated tests. Return to clean stereo when cues feel smeared. Lower voice chat when flank information disappears during calls. Change only one variable before testing again.

For the baseline checks, comparison method, and troubleshooting order, use ALVIRAN's measured VALORANT audio settings and HRTF reference.

A Safe Windows Repair Workflow for VALORANT VAN 9002

ALVIRAN — Mon, 13 Jul 2026 08:58:00 +0000

A Safe Windows Repair Workflow for VALORANT VAN 9002

VALORANT error VAN 9002 points to Windows Exploit Protection, not a generic network failure or an automatic reason to change BIOS settings. Riot support describes the error as a state where Exploit Protection is disabled or no longer uses the required defaults. Vanguard needs that Windows security layer active before the game can run.

A safe repair is narrow and reversible: confirm the exact code, record the current Exploit Protection configuration, restore the affected system controls to their Windows defaults, remove only Riot-related program overrides, restart once and test before touching anything else.

What VAN 9002 means

Windows Exploit Protection contains system-wide mitigations and optional per-program rules. A program rule can override the broader system configuration. This is why changing only one visible toggle may not solve the error if Riot or Vanguard executables still have custom entries.

Do not reuse this workflow for a different VAN code. Secure Boot warnings, TPM requirements, HVCI restrictions and connection errors have different causes. Capture the complete message and confirm that the client specifically reports VAN 9002.

How to create a safe baseline

Before editing the configuration:

take a screenshot of the complete VAN 9002 message
install normal pending Windows and Riot Client updates
restart once if an update is waiting
open Windows Security through the Start menu
record any Exploit Protection settings that show a custom override
avoid importing configuration files from another PC

The record provides a rollback reference and prevents a managed or intentionally configured system from being changed blindly. On a work or school device, local settings may be controlled by organizational policy. Contact the administrator instead of fighting a policy that Windows will reapply.

How to restore Exploit Protection defaults

Open Windows Security, choose App & browser control, then open Exploit protection settings. Under System settings, compare the relevant mitigations with Riot's current VAN 9002 instructions and select Use default where required.

The important choice is Use default, not manually forcing every mitigation on. Windows displays the intended default state beside each option. A manual configuration that looks stricter can still differ from the baseline Vanguard expects.

Finish the System settings review before restarting. This keeps the repair in one controlled cycle and lets you check the program-specific layer next.

How to remove only Riot program overrides

Switch to the Program settings tab and inspect the list. Look only for custom entries connected to Riot Games, Riot Client, Riot Vanguard or Riot game executables. Remove the custom program rule as directed by Riot's support workflow so the normal system defaults can apply.

Use these boundaries:

do not remove rules for unrelated applications
do not disable Exploit Protection globally
do not delete Riot or Windows executables manually
do not download replacement DLL files
do not paste registry commands from an unknown source
do not turn off antivirus or firewall protection as a guess

After the System and Program settings checks are complete, restart Windows once. Launch the Riot Client normally and test VALORANT before making another change.

How to diagnose a failed first repair

If VAN 9002 returns, verify that the code is unchanged. Then reopen Exploit Protection and check whether the defaults stayed applied. If the settings reverted, device-management policy or security software may control them. Record the time of the test and whether Windows displayed an organization-management notice.

Do not escalate directly to firmware settings or a complete reinstall. Those actions do not target the Exploit Protection configuration identified by the code. Open a Riot support request with the exact error, Windows version, screenshots and a concise list of the changes already tested.

A useful test log looks like this:

Error: VAN 9002
System settings: restored to documented defaults
Program overrides: Riot-related custom entries removed
Restart: completed once
Result: same code / resolved
Policy notice: present / absent

Common repair mistakes

following instructions for VAN 9003 or another code
forcing every Exploit Protection control on manually
deleting unrelated per-program security rules
changing BIOS, TPM or Secure Boot without evidence
combining Windows, driver and game reinstalls in one test
skipping the restart before evaluating the result
applying a corporate-policy workaround on a managed PC

Complete checklist

The ALVIRAN VALORANT VAN 9002 Exploit Protection repair guide includes the exact Windows navigation, system-default checklist, program-override cleanup, managed-device boundary and safe escalation path.