CzenScripts field guide

Best King V2 Values for Fortnite Cronus Zen

King V2 combines Aim++, Assist and Enhancement systems with Bloom Negator, configurable recoil correction, Quick Fire and Fortnite edit macros. Here are the best source-based values to start with from the current King V2 GPC.

Shane T 10 min read
Best King V2 Values for Fortnite Cronus Zen
Before you begin

Start with the recommended baseline, change one value at a time, and test each adjustment under consistent conditions.

If you're setting up King V2 for Fortnite, the current script has a very different structure from a simple Aim Assist Size and Speed GPC.

King V2 combines three main programmed aim systems labeled Aim++, Assist and Enhancement with additional features such as Bloom Negator, Recoil Negator, Quick Fire, Crouch Shot and several Fortnite edit/build macros.

We analyzed the current King V2 GPC and used the values actually stored in its source for the recommendations below.

These are recommended starting values rather than guaranteed universal settings. Your Fortnite sensitivity, response curve, deadzones and controller setup can all affect how programmed stick movement behaves.

Best King V2 Values: Quick Setup

Setting Recommended Starting Value
Aim++ On for initial aim testing
Assist Off initially
Enhancement Off initially
Bloom Negator On
Bloom Negator Power 80
Recoil Negator Off initially
Recoil Negator Power 17 if enabled
Quick Fire Off initially
Quick Fire Delay 80 ms
Crouch Shot Off initially
Crouch Shot Hip Fire Off
Crouch Shot Delay 60 ms
Edit Assist Off initially
Edit Assist Delay 20 ms
Edit Hold Off initially
Edit Hold Time 100 ms
Button Time 11 ms
No Vibration Optional

Understanding King V2's Three Aim Systems

The King V2 OLED interface identifies three separate systems:

  • Aim++
  • Assist
  • Enhancement

These systems apply different programmed controller-stick routines.

They should not be interpreted as Fortnite screen recognition or visual target tracking. The GPC works with controller inputs and outputs rather than identifying opponents from the game image.

Should You Enable All Three?

Not immediately.

King V2 can apply several different right-stick calculations, random movement adjustments and polar movement patterns.

If you activate every system before testing the script, it becomes much harder to identify which part of the GPC is responsible for the result.

A cleaner setup is:

  1. Enable Aim++.
  2. Leave Assist off initially.
  3. Leave Enhancement off initially.
  4. Test the script.
  5. Add one additional system at a time.

Why We Aren't Giving Fake Aim++ Slider Names

The current King V2 source contains numerous internal Aim++ parameters, but many of them are stored under obfuscated variable names rather than readable menu labels such as “Radius” or “Speed”.

We therefore do not recommend publishing invented names for those values.

What can be verified is that the GPC contains configurable programmed polar movement, movement shape calculations, activation thresholds and separate behavior while aiming or firing.

The safest source-based approach is to start from the values already compiled into King V2 and tune the clearly exposed options around them.

Bloom Negator: On

The current King V2 source starts with Bloom Negator enabled.

Its starting Power value is:

Bloom Negator Power: 80

This makes 80 the most appropriate source-based starting value.

Bloom Negator Power: 80

The Bloom Negator routine alternates programmed horizontal left-stick output while active.

The Power value in this feature acts as timing rather than a traditional aim-strength percentage.

The source starts at 80 and changes its delay as the routine runs.

For that reason, do not interpret “80” as an 80% aim-assist strength.

Best Recoil Negator Value: 17

King V2 stores:

Recoil Negator Power: 17

The Recoil Negator feature itself starts disabled.

If you want to test the programmed recoil correction, begin at 17.

How Recoil Negator Works

When enabled while aiming and firing, King V2 adds its Recoil Negator value to the programmed right-stick vertical output.

This means the same value can feel different depending on:

  • Your Fortnite sensitivity
  • ADS sensitivity
  • Response curve
  • Weapon
  • Stick deadzone

Use 17 as a baseline rather than assuming it will perfectly match every Fortnite weapon.

If Recoil Correction Is Too Strong

Reduce the Recoil Negator value gradually.

For example:

  • 17
  • 15
  • 13

Test each value under the same conditions before changing anything else.

If Recoil Correction Is Too Weak

Increase it in similarly small steps.

Avoid making very large jumps because you can quickly move from insufficient correction to excessive downward stick output.

Quick Fire Delay: 80 ms

The current GPC stores:

Quick Fire Delay: 80 milliseconds

Quick Fire itself starts disabled.

If you enable the feature, keep 80 ms as the initial timing rather than changing it before testing.

Quick Fire Controls

The current source assigns:

  • Quick Fire Toggle — RB / R1 equivalent
  • Quick Fire Off — LB / L1 equivalent

These are part of the script's programmable controller behavior and can interact with your normal Fortnite button setup.

Crouch Shot Delay: 60 ms

King V2 supports both:

  • Crouch Shot
  • Crouch Shot Hip Fire

The current source stores:

Crouch Shot Delay: 60 ms

Both crouch-shot modes start disabled.

For a clean baseline, leave them off until the aim configuration has been tested.

Should You Enable Crouch Shot?

Only if you actually want the script to add repeated crouch input during the relevant firing condition.

It is not necessary for King V2's aim systems to run.

If enabled, start at the existing 60 ms timing.

Edit Assist Delay: 20 ms

King V2 also contains Fortnite-specific edit automation.

The current source stores:

Edit Assist Delay: 20 milliseconds

Edit Assist starts disabled.

If you use the feature, 20 ms is the correct source-based starting point.

Edit Hold Time: 100 ms

The script also provides an Edit Hold option with:

Edit Hold Time: 100 ms

This feature changes when the script treats the edit input as being held long enough to run its associated sequence.

Again, leave it disabled until you specifically want to test that edit workflow.

Button Time: 11 ms

King V2 contains a general:

Button Time: 11 ms

This is used in some of the script's automated button sequences.

Because those sequences were authored around that value, we recommend leaving it at 11 initially.

Other King V2 Macro Settings

The current source contains several additional Fortnite macro options:

  • Pickup Macro
  • Instant Full Reset
  • Auto Confirm Macro
  • Edit Assist
  • Edit Hold
  • Pre-Fire Macro
  • Wall Replace Macro
  • Build Tracker

These all start disabled in the current GPC.

Recommended Macro Setup

Macro Starting Recommendation
Pickup Macro Off
Instant Full Reset Off
Auto Confirm Macro Off
Edit Assist Off
Edit Hold Off
Pre-Fire Macro Off
Wall Replace Macro Off
Build Tracker Off

This keeps your first King V2 test focused on the aim-related behavior rather than combining aim, firing, building and editing automation simultaneously.

Build Tracker Time

The current script stores:

Build Time: 11500

This belongs to the Build Tracker system rather than being an aim-assist value.

Build Tracker starts disabled, so there is no reason to change this when you are only tuning King V2's aim configuration.

Perfect Accuracy

King V2 contains a feature labeled Perfect Accuracy.

It starts disabled in the current source.

The assigned activation button is RB / R1 equivalent.

For a values-focused setup, leave this off initially so that you are not adding another firing-input routine while judging the core aim systems.

Best King V2 Baseline for Aim Testing

For the cleanest initial test, use:

  • Aim++: On
  • Assist: Off
  • Enhancement: Off
  • Bloom Negator: On
  • Bloom Negator Power: 80
  • Recoil Negator: Off
  • Quick Fire: Off
  • Crouch Shot: Off
  • Edit/build macros: Off

This gives you a reference configuration before layering in additional King V2 features.

Testing Assist Separately

Once your Aim++ baseline is established:

  1. Keep your Fortnite sensitivity unchanged.
  2. Enable Assist.
  3. Test the same aiming situations.
  4. Compare the controller feel.
  5. Disable it again if you prefer the original configuration.

Because the current source does not expose all Assist parameters with readable names, this is more reliable than publishing arbitrary “best strength” numbers that the GPC itself does not label.

Testing Enhancement Separately

Use the same process with Enhancement.

The Enhancement engine contains numerous internal variables controlling its programmed polar movement, movement shape, thresholds and firing behavior.

Rather than replacing those internal values without clear labels, test the compiled source configuration first.

King V2 Aim++ Is Not Visual Tracking

Names such as Aim++, Assist and Enhancement describe GPC controller-processing systems.

King V2 does not provide evidence of:

  • Screen recognition
  • Computer vision
  • Enemy detection
  • Game-memory reading

Its calculations operate from controller input and programmed controller output.

Fortnite Sensitivity Matters

The same King V2 configuration can feel different on two Fortnite setups.

Important differences include:

  • Look sensitivity
  • ADS sensitivity
  • Linear vs Exponential
  • Left-stick deadzone
  • Right-stick deadzone

Choose your preferred Fortnite controller settings first, keep them stable and then tune King V2 around them.

Linear vs Exponential

Fortnite response curve can significantly change how programmed stick movement translates into camera movement.

If you switch between Linear and Exponential, retest King V2 rather than assuming the same setup will feel identical.

Read our Fortnite Cronus Zen Aim Assist Settings Explained guide for more detail on how these types of values interact.

Best Way to Tune King V2

  1. Keep your normal Fortnite settings unchanged.
  2. Start with Aim++ only.
  3. Keep Bloom Negator at 80.
  4. Leave optional macros off.
  5. Test the script.
  6. Enable Assist separately.
  7. Then test Enhancement separately.
  8. If needed, test Recoil Negator at 17.
  9. Only then add Crouch Shot or edit/build features.

Why Change One System at a Time?

King V2 contains many routines capable of altering controller input.

If you simultaneously enable Aim++, Assist, Enhancement, Recoil Negator, Crouch Shot, Quick Fire and multiple macros, it becomes difficult to determine which feature caused a change.

Controlled testing is much more useful than simply enabling everything.

Recommended Recoil Test

If you specifically want to test the Recoil Negator:

  • Use the same weapon.
  • Keep Fortnite sensitivity unchanged.
  • Enable Recoil Negator.
  • Start at 17.
  • Test repeated firing.
  • Adjust in small steps.

Recommended Bloom Negator Test

Bloom Negator already starts enabled with Power 80.

Use that configuration as your reference point before changing its timing.

If you do experiment, remember that this number functions as timing inside the combo rather than a simple percentage strength.

Recommended Editing Test

If you want to test King V2's editing features after finishing your aim setup:

  • Edit Assist Delay: 20 ms
  • Edit Hold Time: 100 ms
  • Button Time: 11 ms

Keep the source values first and only change them if your own button layout or timing requires adjustment.

Final Recommended King V2 Values

The most useful readable source values to remember are:

  • Bloom Negator: On
  • Bloom Negator Power: 80
  • Recoil Negator: Off initially
  • Recoil Negator Power: 17 if enabled
  • Quick Fire Delay: 80 ms
  • Crouch Shot Delay: 60 ms
  • Edit Assist Delay: 20 ms
  • Edit Hold Time: 100 ms
  • Button Time: 11 ms
  • Aim++: Test first
  • Assist: Add separately
  • Enhancement: Add separately

Final Thoughts

King V2 is better approached as a multi-system Fortnite GPC than a script with one universal “aim strength” value.

The current source gives us clear starting values for Bloom Negator, Recoil Negator, Quick Fire, Crouch Shot and its edit timing, while much of the deeper Aim++ engine is deliberately stored under obfuscated internal variables.

For that reason, the most reliable setup is to keep the compiled Aim++ configuration intact, start with Bloom Negator 80, and add Assist, Enhancement and optional features one at a time.

Get King V2 for Fortnite, browse the Fortnite Cronus Zen script collection, or read our Best Fortnite Cronus Zen Script for Aim Assist guide.

You can also follow the Fortnite Cronus Zen setup guide or use the CzenScripts Best Settings Generator.

CzenScripts updates

Get new settings guides first

Receive new script guides, setup updates and CzenScripts releases directly in your inbox.