TECHNICAL GUIDE BY DARK D.

DOGE
Official Discord: https://discord.com/invite/8w4Nbxfm3d

1) Introduction (valid for DogeFree and V4)

This is a fully external and (at the moment) undetected color cheeto. Even if it’s undetected,
you can be banned for manual reports, especially if your teammates report you. If you set an
unlegit/obvious/shaking config, random teammates will report you and you will be banned.
To avoid this, consider playing with trusted friends or people on the server (see chapter 24 of
this guide), and use a legit config. Use it at your own risk, I will not be responsible for any
ban. Also, please remember that “a cheeto undetected today, could be detected tomorrow”
(just maybe because some retards sent it to Riot). To avoid this, consider buying a private
version. To set up cheeto you need to have at least a little bit of brain, if it’s not the case,
please give up before losing your time.

DogeFree: This version is for free, but it was cracked long time ago by an idiot even if it was
free, so you will probably find it on the web. I will not provide any help for this version, if you
have not enough brain to follow this guide and read FAQs, don’t open a ticket and complain
that it doesn’t work.

V4.x.x: These versions are only for VIPs. Please read #vip-rules to know how to become
vip. Being a vip doesn’t mean that you don’t have to use your brain, and doesn’t mean that
I’m your slave. I will help you also if you ask stupid questions, but if the answer is in this
guide or FAQs, I’ll probably just tell you to read it again carefully. FULLY READING THIS
GUIDE IS MANDATORY! I won’t setup for you cheeto through Anydesk, my time is precious
and limited, so that would cost you a lot more than vip role. Just a note: usually helpers and
VIPs of the server are more kind than me.

If everything is clear, you can start with the following steps:

2) Buy devices (valid for DogeFree and V4)

To use cheeto you need to buy the following devices.

Starting from V4.8.7, USB Host Shield is not necessary anymore, but of course you will be
safer from ban with it.

Arduino Leonardo (mandatory for both DogeFree and V4)

https://www.amazon.it/Arduino-A000057-Leonardo-Microcontroller/dp/B008A36R2Y/ref=sr_1
_3?__mk_it_IT=%C3%85M%C3%85%C5%BD%C3%95%C3%91&crid=1AS6W90Z0SQEI&
keywords=arduino+leonardo&qid=1677766914&sprefix=arduino+leonardo%2Caps%2C196
&sr=8-3
USB Host Shield (optional for both DogeFree and V4)
https://www.amazon.it/ARCELI-Shield-Arduino-Supporto-Android/dp/B07J2KKGZ4/ref=sr_1_
5?__mk_it_IT=%C3%85M%C3%85%C5%BD%C3%95%C3%91&crid=3I82CI9N6Z1Z6&key
words=usb+host+shield&qid=1677766966&sprefix=usb+host+shield%2Caps%2C173&sr=8-
5

You can buy them from Amazon or Aliexpress or Ebay etc. You can buy original or clones,
but if you buy clones I can’t guarantee that they will work, just ask a suggestion to VIPs and
free members.

Also, make sure you have a Micro USB working cable (like data phone cable) to connect
Arduino Leonardo to pc. Some cables are buggy and don’t work. I’m using this cable (the
shorter one):
https://www.amazon.it/gp/product/B07VN1GNMK/ref=ppx_yo_dt_b_search_asin_title?ie=UT
F8&psc=1

3) Solder USB Host Shield (valid for DogeFree and V4)

You can decide to buy and use Usb Host Shield or not, it’s up to you! If you don’t have
it, of course you can skip this step. If you want to use it, you have to solder it!

You have to solder Usb Host Shield unless you are very lucky (usually comes not soldered).
You have just to do this 3 little tin dots:
You can also watch this video tutorial:

https://www.youtube.com/watch?v=1dxwU87GQVM

If you are not expert, I suggest to take the Host Shield to experts (like repair shopor similar)
and pay them to do so, there is high risk to broke it !

Then you have to combine Arduino Leonardo and USB Host Shield in the following way (but
don’t connect to the pc yet, wait for next steps):
4) Pre-Setup suggestions (valid for DogeFree and V4)
Cheeto will work for sure on Windows 10. For some vips is also working on Windows 11, but
I can’t assure this. Just try it.

Please make sure you’ll have last winver and no updates to do on Windows Update:

Install these softwares if not already installed (look for last versions if these are old):

Directx: https://www.microsoft.com/it-it/download/details.aspx?id=35
VCRedist:
https://learn.microsoft.com/it-it/cpp/windows/latest-supported-vc-redist?view=msvc-170
.NET Framework: https://dotnet.microsoft.com/en-us/download/dotnet-framework/net481

And update graphic card drivers:

PLEASE NOTE: For some people, to make arduino/cheeto work, it was necessary to fully
format the pc. I don’t know why, maybe it depends if you have shit on the pc or if you treated
it badly during years. Maybe they just did not follow next steps correctly, I don’t know.

5) Arduino IDE Setup (valid for DogeFree and V4)

Go to the following site: https://www.arduino.cc/en/software and download Arduino IDE
1.8.19
With newer versions cheeto will not work, so please don’t be dumb and download only right
version !

Then install it, but please make sure to accept driver installation, or it won’t work !
Don’t change installation folder to avoid any problem !
6) Install USB Host Shield Library 2.0 (valid for
DogeFree and V4)

PLEASE NOTE: THIS STEP IS MANDATORY ALSO IF YOU DON’T HAVE USB HOST
SHIELD !!! IF YOU IGNORE THIS YOU ARE RETARD !!!

Open Arduino IDE and Install USB Host Shield Library 2.0
Type “USB Host Shield Library 2.0” on the search bar and Install:
7) Connect Arduino Leonardo (valid for DogeFree and
V4)

7.1) If you are using USB Host Shield

Connect Arduino Leonardo to pc through Micro USB cable, then select:

Board type: Arduino Leonardo

Port: select the COM number (will be different depending on pc/other factors):
7.2) If you are not using USB Host Shield

Connect Arduino Leonardo to pc through Micro USB cable, then spoof it following chapter 12
of this guide (detailed screenshots will come soon...)

You can just follow this video to complete this step: https://youtu.be/CcfnBOqdLVg

8) Download cheeto (valid for DogeFree and v4)

Downlaod cheeto where you prefer (I suggest Desktop).

DogeFree: You can find it on #free-releases after receiving the free role

V4.x.x: Downloads are on #vip-releases. You can find it here:

Zip password is on file name, but for dumb people is: 1234

9) Optional: Enable mouse side buttons (only for V4)

Please note: this step is not necessary if you are not using USB Host Shield !

For some mice you can enable side buttons following the guide inside this folder:

This doesn’t work for every mouse, so you just need to be lucky 🙂
Please remember to backup files that you are replacing, close arduino ad reboot pc after
following this guide

10) Load a library to make mouse work (valid for

DogeFree and V4)

Please note: if you are not using Usb Host Shield, you can directly go to chapter 10.4 !!

Before connecting the mouse to USB Host Shield, you need to load a library to make your
mouse work. You can find libraries on cheeto folder:

Not every library works with every mouse. It is possible that you have an incompatible
mouse that doesn’t work with any library ! In that case you need to purchase a new mouse,
or find/create a working library for it. If you do so, I will integrate cheeto to work with that
library and publish it inside vip release.

DogeFree: This version has only 2 libraries that you can test. If no one of that works,
consider switching to the vip version. These libraries will also work without usb host shield

V4.x.x: This version at the moment has 8 libraries. no_host library will work without host
shield.
Luna is a very generic library that usually works with every mouse (but scroll wheel will not
work). Animali is the best for Logitech mice.

To know which is the best library for you, the best thing you can do is to test every library !
Please remember that when you load different libraries the COM will automatically change,
so sometimes you’ll need to change it.
Please also note that it’s better to use the mouse wired ! Wireless usually doesn’t work well
(only in some lucky cases)

To load a library there are 2 possible cases:

10.1) Multiple File library

A) In the library folder there is more than one file (animali_mouse_new,

hidmousereport_new, doge_mouse_new)

Select “Add .ZIP Library”:

Then select the whole folder and load it:

Then go to Examples and open it:

Then simply load it on Arduino with Upload button:

10.2) Single File library

B) In the library folder there is only one file (bbsamant_new, doge_mouse_simple_new,

luna_new)

For bbsamant_new library, please read readme.txt and move every file except
bbsamant_new.ino to the indicated folders. To load this library you’ll need to double click on
bbsamant_new.ino and load it:
For other libraries, just go to the library folder, double click on it or click open, and then load
into arduino:
PLEASE NOTE: Arduino has internal memory, so if you loaded a library inside it and it
worked, you don’t need to load it anymore ! You need to reload it only if you need to change
it, try different libraries or if you loaded a different/empty sketch by mistake.
10.3) Working Mouse-Library combinations

You can also refer to libraries that people are using. If a combination is not reported below,
that doesn’t mean your mouse won’t work with any library, so please test it and then report to
me by dm if it works, so I can add the nw combination!

WORKING COMBINATIONS LIST (to be updated, waiting for people answers…):

Logitech G402 Hyperion Fury → animali_mouse_new, hidmousereport_new

Logitech G502 Proteus Spectrum → (side buttons won’t work) animali_mouse_new,
hidmousereport_new
Logitech G502 Hero (side buttons will work) → animali_mouse_new, hidmousereport_new
Logitech G403 → animali_mouse_new, hidmousereport_new
Logitech G403 Hero → animali_mouse_new
Logitech G703 → animali_mouse_new, hidmousereport_new
Logitech G304 → luna_new
Logitech G305 (wired and wireless) → luna_new
Logitech G300s → luna_new
Logitech G102 → animali_mouse_new, hidmousereport_new
Logitech G203 → animali_anomali_new
Logitech G203 Lightsync → animali_anomali_new
Logitech G Pro → luna_new
Logitech G Pro X Superlight (wired or wireless) → animali_mouse_new, luna_new,
bbsamant_new
Glorious Model O → luna_new, bbsamant_new, hidmousereport_new
Glorious Model D → luna_new
Glorious Model D Wireless → animali_mouse_new (with side buttons)
Razer Basilisk V2 → doge_mouse_new
Razer Deathadder 2013 Ver. → luna_new
Razer Deathadder Essential → luna_new, hidmousereport_new (but on both you need to
change mx and my, contact bray#5905 on server), doge_mouse_new
Razer Deathadder V3 (wireless) → hidmousereport_new (but you must invert x and y in
code)
Razer Deathadder Elite → bbsamant_new
Razer Viper → luna_new
Razer Viper Mini → luna_new, bbsamant_new (with side buttons)
Razer Viper Ultimate V2 (wireless and wired) → bbsamant_new
Razer Abyssus 2014 → luna_new
Dell MS116 → luna_new
Cooler Master mm710 → hidmousereport_new (side buttons too)
Cooler Master mm711 → hidmousereport_new (side buttons too)
Huawei GT Wireless → luna_new
Steelseries Prime (wireless or wired) → luna_new
Steelseries Aerox 3 (Onyx) → luna_new, doge_mouse_new
Hyperx Pulsefire Haste Wireless → luna_new, doge_simple
Hyperx Pulsefire Haste Lightweight → luna_new
MSI Interceptor DS B1 Gaming Mouse → luna_new, doge_mouse_new,
hidmousereport_new

10.4) Only if you don’t have USB Host Shield (VIP)

Select your spoofed mouse from boards (remember, you spoofed it on chapter 7.2), and load
no_host.ino library (double click to open with Arduino IDE and then load)
10.5) DogeFree note for retards

FOR RETARDS WHO CAN’T READ #free-releases CHANNEL:

If and only if you are using the free version (Doge Free), you must use the basic library for
no host shield !

11) Connect mouse to Usb Host Shield (valid for

DogeFree and V4)

THIS STEP IS NEEDED ONLY IF YOU ARE USING USB HOST SHIELD !!

After loading a library, disconnect mouse from pc and connect it to USB Host Shield. Then
wait some seconds. If the mouse moves and works, it’s done!

Please note that the mouse will use default DPIs. You can modify it only if the mouse has an
internal memory (like Logitech), connecting mouse to pc and modifying default DPIs with
vendor mouse program (like Logitech G Hub)

If the mouse is not working, just try a different library.

In general, if mouse doesn't work with any library, it could be due to:
- Bad/missing soldering or broken host shield
- Not original Arduino Leonardo
- Windows needs to be rebooted
- Wrong/incompatible library
- Windows needs to be formatted
- USB Host Shield not well connected to Arduino Leonardo
- Shitty Micro USB cable
- You have to try to set CustomResolution = True

A little curiosity:

I have found a very interesting thing: I was testing the new AI cheeto with arduino, but with
logitech G402 connected to arduino and logitech G502 connected directly to pc. And I
figured out that aimbot works also using logitech G502 if cheeto is activated, even if it's not
directly connected to arduino. So, I decided to test DogeFree color aimbot with the same
method (on a valorant image) and it worked (so it's not only a "bug" of the new cheeto). So
this will not work on Valorant, because it will block for sure your second mouse, but it's
interesting for other games, because you could use cheeto and side buttons on the same
time, with a crap mouse connected to arduino and the good one connected to pc.
11.1) Optional: Test Usb Host Shield
This is to test if USB Host Shield is giving 5V power to what is connected to it. Don’t test it if
it is already working fine and cheeto is working fine.

11.1.1) Method 1

OPTIONAL (don’t do that if mouse is working fine): To check if the USB Host Shield board
has power or not, you can run the board_qc sketch on Arduino Ide:

Please remember to open the serial monitor with the following button to see results and
prints !!

Please also remember to change baud to 115200 on bottom right after opening serial
monitor !!
Please remember that after loading this, you need to reload mouse library.

11.1.2) Method 2

You can use some hardware tools to test if USB Host Shield is giving 5V power. An example
(made by the vip Aesy#1119) is:

He used this tool to test the voltage, and his USB Host Shield is giving correctly 5V power.
He discovered that the problem in his case was the Micro USB cable.
12) Swoof Arduino Leonardo (valid for every version)

STARTING FROM 14/06/2023, CAUSE OF VALO PATCH, IT’S MANDATORY TO SWOOF

ARDUINO EVEN IF YOU ARE USING USB HOST SHIELD !!!

The following tutorials basically do all the same thing (with more or less details) and are
inspired by a post on UC (link below). You can follow my video, Gurumi’s one or Gplays’s
one, it’s up to you, they basically all do the same.

12.1) Tutorial 1 (video made by me)

Just follow this video if you don’t have USB Host Shield: https://youtu.be/CcfnBOqdLVg

+ if it’s not working, maybe you could have other boards.txt to swoof::

12.2) Tutorial 2

Alternative videos to spoof Arduino Leonardo:

Get VIP and PID: https://youtu.be/kfgxgva0ueU

Spoof: https://www.youtube.com/watch?v=dewT_i5Ufjw

13) Run cheeto (explained for V4, DogeFree will be

similar)

13.0) VERY IMPORTANT: CHANGE HASH (Only for VIPs)

Before even trying to run the cheeto, please change .exe hash following chapter 25 of this
guide
13.1) Things to remember before loading cheeto
- Key is linked to your HWID, it will work only on a single pc
- Never load cheeto or .ino script if Valorant is already opened: if Valorant is already opened,
close valorant, load cheeto anche then re-open Valorant (some users has been banned for
not following this rule)
- Before loading cheeto/valorant, only Arduino Leonardo must be connected to pc, not other
mice
- Don’t ignore comments written on Config.ini file. To make it more readable, please install
Notepad++ (https://notepad-plus-plus.org/downloads/)
- On config file, boolean parameters are with the first letter uppercase and the others
lowercase (True or False)
- General life pill: "A cheeto undetected today, could become detected tomorrow"

13.2) How to run cheeto

Before running cheeto, please remember to set mandatory parameters on Config.ini file:

License: The license given to you in private on dm (Dark Doge YT#7444)

COM: The COM number of your Arduino (It’s normal if it’s different than mine, it changes
depending on pc/library etc)
MouseType: Every library has a different name. See them in the comment.

Maybe it could be necessary to disable every anti-virus to run cheeto (depends on

anti-virus). Just see if it works with anti-virus on, if not, disable it.

The first time, please try default parameters (because you probably don’t know anything
about the cheeto and you will broke everything if you put weird values on Config file). After
you see cheeto working, then you can try modifying things and clearly see your eventual
errors.

Now, enable Name File Extension on Windows Folder Options:

To run cheeto, open cmd as admin:

Move to cheeto folder: Copy folder path

Paste it on cmd with cd command and press Enter. Then type cheeto name (don’t forget to
copy .exe too ! ) Don’t rename cheeto or it won’t work ! Then press Enter.

If everything is correct, cheeto will print parameters and “READY”:

14) Valorant Setup (explained for V4, DogeFree will be
similar)

Now you can open Valorant: while Valorant is loading, please continue moving the mouse
without stopping, to prevent mouse block.

On Valorant options:

- Valorant should be installed in the same cheeto hard drive (I suggest C)

- If you play on 2k, 4k resolution or others different than 1080p and it doesn’t work, consider
changing custom resolution (chapter 16.2.7)
- Disable blood in game
- Disable mouse buffer row input in game
- Set game to windowed fullscreen (starting from 14/06/2023 there was a patch, for which
some users had to put it back to fullscreen to make it work)
- Set right color of enemies in game (cheeto default color is purple, so if you are using
default, set enemy color to purple)
- (Optional) If possible, set medium/high graphic with anti aliasing to FXAA 16x
- Crosshair should not be so big, otherwise it will interfere with cheeto. An crosshair color
must not be of the same color that cheeto tracks ! For example, my crosshair is:
0;P;o;1;d;1;0t;0;0l;0;0o;0;0a;1;0f;0;1b;0

Cheeto options in case of problems:

- If you notice keyboard lag, put a little PerformanceBoost value (0.001 or less)
- If for some function, mouse will continue shooting, then set a little delay (0.01) for that
function

There some tools that interfere with cheeto in game, like interception:

Please always test it in a clean situation/environment

15) DogeFree parameters

You are using a free version bro. You can learn/test by yourself how it works, and there is
also a video tutorial here: https://link-target.net/507769/valorant-undetected-cheat

Only basic behaviour, pretty easy. Color is a predefined Purple. There is only Aimbot and
you can usit only with RCLICK (right mouse button). No customizations like V4.X and Safety.
16) V4.8.7 and Safety DogeFree parameters
There are different/old releases on #vip-releases channel. Newer versions should be better
and with less bugs than older ones, but you are free to use the version you prefer. For older
versions parameters, please refer to #vip-releases, here it’s only explained the newest
version.

To make Config.ini files a lot more readable, I suggest you to install Notepad++
(https://notepad-plus-plus.org/downloads/) and use that to open it. If you use standard
Windows Notepad, you won’t understand anything and not able to distinguish comments
easily !

16.1) Config Selector

By default, there are 2 .ini files inside cheeto folder:

ConfigSelector.ini simply contains the config file name that we want to use for the cheeto.
Default is of course Config.ini file:
So if you don’t want to create multiple configs, just don’t touch this file.

The aim of this method is to be able to modify on the fly the config, and switch to different
configs depending on the circumstance. For example if you have Astra on opponent team
and you need to quickly change to Yellow, or if enemies are strong and you want to put a
rage config. So, you can prepare how many configs you want and simply modify the
ConfigFile parameter on ConfigSelector.ini.

For example, you can create this:

then if you need to be legit and with purple, just do this:

Then save and load/re-load cheeto pressing the ReloadSettingsKey (explained next)

16.2) General parameters

License, COM and MouseType are mentioned on section 13). Just remember that these
parameters won’t be reloaded with ReloadSettingsKey but you’ll need to close and reopen
cheeto to reload them.

16.2.1) Colors

ColorPurpleMode: → REMOVED STARTING FROM V4.8.6

There are 2 options: STRONG and SOFT. Are just 2 different purple tones. If
SetCustomColor parameter is True, this parameter won’t have any effect on cheeto !

SetCustomColor: → REMOVED STARTING FROM V4.8.6

If this parameter is True (please note, T uppercase and the rest lowercase, or won’t work)
cheeto will use the following 2 parameters to set the color
STARTING FROM V4.8.6 the system will directly using the following parameters:

HSVCustomLower: the lower color range, HSV format

HSVCustomUpper: the upper color range, HSV format

Every HSV color in the middle of these 2 values will be considered as an enemy by cheeto.

Purples (which is also the default):

Default:

HSVCustomLower = [140, 110, 150]

HSVCustomUpper = [150, 195, 255]

Strong (maybe less shaky ?):

HSVCustomLower = [127, 76, 123]

HSVCustomUpper = [162, 197, 255]

Anti-Reyna/Astra (but more shaky):

HSVCustomLower = [140, 110, 160]

HSVCustomUpper = [140, 150, 194]

Another Purple:

HSVCustomLower = [140, 120, 180]

HSVCustomUpper = [160, 200, 255]

Yellows:

Yellow 1:
HSVCustomLower = [30, 125, 150]
HSVCustomUpper = [30, 255, 255]

Yellow 2 (by @INMENR#6434)

HSVCustomLower = [30, 170, 170]
HSVCustomUpper = [30, 255, 255]

Yellow 3 (by @Engin#4782)

HSVCustomLower = [20, 100, 100]
HSVCustomUpper = [30, 255, 255]

Yellow 4
HSVCustomLower = [30, 160, 240]
HSVCustomUpper = [30, 255, 255]

Yellow 5
HSVCustomLower = [30, 150, 200]
HSVCustomUpper = [30, 165, 255]

Yellow 6 (by @doggyum)

HSV_Cust0m_L0w3r = [30, 120, 180]

HSV_Cust0m_Upp3r = [30, 180, 255]

Reds:

Red 1 (Strong):
HSVCustomLower = [0, 80, 240]
HSVCustomUpper = [30, 255, 252]

Red 2 (Soft):
HSVCustomLower = [30, 150, 220]
HSVCustomUpper = [190, 190, 250]

16.2.2) ReloadSettingsKey

Press this button at any time to reload settings. Cheeto will first of all look at
ConfigSelector.ini file and then re-load every parameter (except License, COM,
MouseType and HideCMD) on the indicated .ini file. You can change the default key if you
need.

16.2.3) ExitKey

Press this button at any time to close cheeto. If you do so, you’ll need to re-launch cheeto.
Please don’t do that if Valorant is already opened to avoid ban. Close Valorant, Reopen
cheeto, reopen Valorant.
16.2.4) HideCMD

You can Hide CMD (only at cheeto startup) putting it True. Default is False. This function
was requested by some vips, but I suggest to not use it, just read the comment on the
config:

16.2.5) PerformanceBoost

A value greater than 0 will reduce cpu consumption, but cheeto will be slower in tracking and
activating every function. If your keyboard is lagging (delayed keypress) or you simply want
to reduce cpu usage, please put a low value, like 0.01, 0.001 or 0.0001. Values greater than
0.05 could destroy cheeto performances, so please keep it a low number. If cheeto is slow
after putting a positive value here, just increase function speed (explained later).

16.2.6) HighCPU

This is an old parameter that vips requested to have also on this version. I suggest you to
not use it. This parameter will increase cpu usage at maximum while using cheeto functions
(for example when you are pressing aim assistant button). This was to avoid low cheeto
speed while putting PerformanceBoost greater than 0, but I think it’s better to just increase
speed in that case.

16.2.7) Custom Resolution

Cheeto usually calculates resolution automatically (Windows resolution). However, if you

notice problems on that or for some reason you need a custom resolution, you can set
UseCustomResolution to True and modify values manually.
16.2.8) Print FPS

You can print FPS using the parameter PrintCheetoFPS. Put it True to print FPS. Please
note that with PerformanceBoost = 0 they will be like 2-4000, while with PerformanceBoost
>= 0.0001 around 60. This parameter is not useful as AI cheeto. It’s important to see the
value in the moment you are tracking with aim assistant, rather than when you aren’t doing
anything. Anyway I suggest you to keep it False.

16.2.9) Screen Capture Method

PLEASE NOTE: starting from v4.8.6, options are M, D instead of MSS and DXCAM.

You can change the screen capture method with the ScreenCaptureMethod parameter.
Possible options are MSS (default) and DXCAM (new method). MSS is more compatible, so
you usually won’t have any errors. DXCAM is extremely faster, but has a lot of compatibility
problems, especially if you are using a notebook or a desktop with more than one GPU.
Anyway feel free to try it. If you get errors, just switch back to MSS.
IMPORTANT: With DXCAM you probably can’t use the same speed you are using with MSS,
because it will shake a lot ! So you’ll probably need to reduce it. But just make some tests.

IMPORTANT: I didn’t test DXCAM a lot, so I don’t know if it’s more bannable than MSS.
Theoretically no, but use it at your own risk like every new function.
16.2.10) Quick Settings Updater

You can quickly modify (increase or decrease by a quantity that you can decide) some
settings of Aim Assistant and/or Old Flick pressing specific buttons (that you can change)
without manually modifying config and reloading. Option is disabled by default, so you need
to set it to True if you want to enable it. You can also decide to enable some options and
disable others using the related UPDATER_ parameter.

16.3) Aim Assistant

Let’s start with Aim Assistant Function.

16.3.1) Aim Target

PLEASE NOTE: starting from v4.8.6, options are C, N, H instead of CHEST, NECK, HEAD.
First of all you’ll need to decide where to aim. This usually creates a little bit of confusion.
There is one important thing to remember: If you put low fov (between 25 and 35) you’ll
need to set AimAssistant_Target to CHEST and AimAssistant_HeadOffset_Y = -1 to aim
to head ! (This is because cheeto is made for normal/high fov, so will get mad if you put very
low fov to increase “legitimacy”) Like this example (and default config too):

This will aim to head:

In case of normal/high fov (any value greater or equal to 40) cheeto will act as expected, so
to aim to chest you need to put CHEST, to aim to neck put NECK, to aim to head, HEAD,
and AimAssistant_HeadOffset_Y should be 0. An example:

This will aim to head:

This will aim to chest:

This will aim to neck:

16.3.2) Speed and Smooth

Speed/Smooth effect will be very different depending on pc hardware, monitor, winver,
mouse, dpi, resolution, in game sensitivity and a lot of other parameters.SO
BEGGING/ASKING/BUYING CONFIGS FROM OTHER PEOPLE MEANS BEING A LOT
RETARD. JUST TAKE SOME TIME AND FIND YOUR OPTIMAL VALUES. Seeing configs
of other players could be a good starting point, but you can’t simply take it and use it, it will
probably be shit for your environment. So for example a non-shaking/legit speed for a
person, could be extremely shaking for another one and vice-versa. So the only way to find
yours is to test it with different values. At the beginning keep Smooth = 1 (means no
modifications) and modify only X and Y speed. I suggest to keep X Speed = Y Speed, but
you can try as you prefer. Usually you will find your perfect value between 0.5 and 2, but in
some cases people needed to put it 3 or more, or less than 0.5. Just activate your brain and
try.

Smooth is a parameter to make cheeto smoother. 1 means no effect. A value < 1 means
more legit/smoother, > 1 less smooth/legit
16.3.3) Anti Shaking
This is a new function, to avoid shaking but keeping high cheeto speed. To activate it, put it
True. Speed X and Y are the new speeds that cheeto will use while he is “close” to the target
(the center pixel to which it aims). You can define “nearness” with X and Y parameters. So
the cheeto will slow down when it is close to the target, avoid shaking on the central point.

16.3.4) Aim Assistant In Game Button

You can assign a specific button to use aim assistant in game (or you can have it always on,
explained later). Aim assistant will work only when the button is pressed.

Possible mouse button options: LCLICK, RCLICK, MB1, MB2, MIDDLE

Possible keyboard button: you can assign the keyboard letter or button you prefer
(examples: q, v, b, z, alt, ctrl, etc etc..)

Personally, I deassigned RCLICK in game options, and I use RCLICK, I feel a lot
comfortable playing like that.

16.3.5) Aim Assistant On Off Button

To be able to use Aim Assistant, you’ll need to activate it. To do so, just press the related
button (you can change the key on config file):

Every time you press F1 that will print a log on cmd (to print if you activated or deactivated
it):

16.3.6) Aim Assistant Delay

If you notice strange behavior, keyboard lag, mouse shooting without stopping, you can put
here a low value (like 0.05, 0.01, 0.001, 0.0001). Aim Assistant performances will be
impacted of course. Otherwise, don’t touch it.

16.3.7) Aim Assistant Always Active

Of course you can also set aim assistant always active without pressing any button. But in
this case it will aim to any object with the same color that you set (dead bodies, flowers, etc),
so random teammates will notice that.

You can do that putting this to True:

Of course you’ll need to activate it with On/Off button as always.

16.3.8) New Shitty Legit Function

Asked by Apple and Blaxe. It will basically only moves left or right (horizontally, x axis) and
not up or down, so aim assistant will be more legit, but also more shitty.
Video by Blaxe: https://streamable.com/moblbg

To activate, put AimAssistant_ShittyLegitAimTracking = True. Default of course is False.

16.3.9) Random Target function

This is an option suggested by vips to be more legit. If enabled, every time you press the aim
assistant button (doesn’t work with aim assistant always on), the target will be randomly
chosen from values in upper and lower X and Y ranges. Default values are between chest
and head, but you can also include legs for example, increasing the _Lower_Y value. You
can enable this function just by setting it to True.

Please note: this option enabled will make Triggerbot and No Recoil not working properly
together with Aim Assistant

Please note: with MSS you have to set values different than DXCAM, so for example:

For MSS, will work with this values:

For DXCAM, will work with this values:

Of course these are only examples, feel free to make tests and modify them.
16.3.10) Aim Assistant Always On Stop Button

Added 41m_4ss1st4nt_4lw4ys_0n_St0p_Butt0n button for people using Aim Assistant

always on: auto tracking will stop if the button is pressed, and start again if not pressed.
Please note that this button can't be the same as Aim Assistant Buttons, otherwise it won't
work.

16.4) Old Flick

This is an old function that people asked me to re-introduce on this version.

It uses some of the same parameters of Aim Assistant:

- Color - chapter 16.2.1

- Aim Target - chapter 16.3.1
- Smooth only (not speed) - chapter 16.3.2

Anti-Shaking will not work for Old Flick.

This function is built to work well with left click, so don’t modify the button. It will miss the first
shot, but then it will aim correctly.

16.4.1) Old Flick In Game Button

You can assign a specific button to use Old Flick in game. It will work only when the button is
pressed.

Possible mouse button options: LCLICK, RCLICK, MB1, MB2, MIDDLE

Possible keyboard button: you can assign the keyboard letter or button you prefer
(examples: q, v, b, z, alt, ctrl, etc etc..)
Strongly Suggested Option: LCLICK

16.4.2) Old Flick On Off Button

To be able to use Old Flick, you’ll need to activate it. To do so, just press the related button
(you can change the key on config file):

Every time you press F5 that will print a log on cmd (to print if you activated or deactivated
it)

16.4.3) Old Flick Delay

If you notice strange behavior, keyboard lag, mouse shooting without stopping, you can put
here a low value (like 0.05, 0.01, 0.001, 0.0001). Old Flick performances will be impacted of
course. Otherwise, don’t touch it.

16.4.4) Old Flick Parameters

Same customization as Aim Assistant, so please refer to chapter 16.3.

PLEASE NOTE: starting from v4.8.6, options are C, N, H instead of CHEST, NECK, HEAD.
16.4.5) Random Target function

Similar to Aim Assistant target function, so read chapter 16.3.9

16.5) No Recoil Inside Aim Assistant

This function is made to introduce no recoil only inside aim assistant, to recoil for a certain
amount of time and within a certain distance. Please note that this is a generic recoil, so it
won’t work the same for every weapon, so if you mainly use a certain weapon, try to find
appropriate settings for it. Also, settings depend on a lot of parameters (mouse, pc,
resolution, dpi, in-game sens etc etc), so my default setting won’t probably be good for you.
You need to make some attempts and try to modify them.

No Recoil Inside Aim Assistant doesn’t have a button, will just work if Aim Assistant button is
pressed (or always active) and if left click is pressed

16.5.1) Activate Recoil Inside Aim Assistant → REMOVED STARTING FROM V4.8.6

First of all, if you want to use it, you have to enable it. Due to the fact that it uses a lot of
cpu, it’s disabled by default. Simply put it True if you want it:

When you activate it, cheeto will print the following message:

16.5.2) Recoil Inside Aim Assistant On Off Button

On/Off button for that function is this. You have to activate it if you want to use that.
That will be printed only if the function is active:

16.5.3) Recoil Inside Aim Assistant Function Delay

If you notice strange behavior, keyboard lag, mouse shooting without stopping, you can put
here a low value (like 0.05, 0.01, 0.001, 0.0001). Recoil performances will be impacted of
course. Otherwise, don’t touch it.

16.5.4) Recoil Inside Aim Assistant Functional Parameters

The following parameters will impact recoil inside aim assistant duration, activation, speed
and behavior.

NewRecoilDelay: For how long it will wait before going on with the next loop
RecoilLoops: For how many loops it will iterate recoil
InsideRecoilIncrementalOffsetY: How much he will move on Y axis in every loop (positive
= down, negative = up)
InsideRecoilIncrementalOffsetX: How much he will move on X axis in every loop (positive
= left, negative = right)
NewRecoilInsideAimAssistantTargetDistance: Recoil will stop working or not activate if
the distance from the target is greater than this parameter

This is the default config: So in this particular case it will stop recoiling for 0.001 seconds on
every loop of the 40 loops. It will automatically stop after 40 loops, or if the distance is
greater than 5 or if left click is not pressed or if aim assistant button is not pressed anymore.
On every loop it will add 0.35 to Y movement and 0.06 to X movement.
16.5.5) Pattern Recoil Inside Aim Assistant

Please note: this is an optional no recoil mode, disabled by default. It is for experts, so
activate it only if you understand what it is (if you don’t have enough brain to understand
it, please give up). Anyway, expert users are free to share parameters and help you in
understanding/setting it (I won’t do so, it’s explained below, I can’t explain it better than the
example below).

To activate this different recoil mode, you have to put

UsePatternRecoil_InsideAimAssistant = True:

Before describing it, please remember that the function will be also impacted by the following
parameters:

Please also note that this won’t work if this parameter is not True:

Please note: default values are for my in game sens, mouse type, mouse dpi, mouse
library, resolution, pc, etc. It will be impacted by a lot of things, so you’ll need to find
your values, don’t come to me complaining that it’s not working properly !

The function is composed by the following parameters:

zoom in:

Recoil_Pattern_X: this represents the values of the x coordinates the mouse will move on
each loop
Recoil_Pattern_Y: this represents the values of the y coordinates the mouse will move on
each loop
Recoil_Pattern_Delay: this represents the values of the delays the mouse will wait after
each movement
Recoil_Use_Same_Delay: If True, it will use Recoil_Same_Delay as delay after every
movement, ignoring Recoil_Pattern_Delay
Recoil_Same_Delay: the delay after each movement used only If Recoil_Use_Same_Delay
= True
Recoil_Pattern_Loops: you can decide to repeat the previously behavior for several times
Recoil_Pattern_Loops_Delay: delay after each repetition

The best way to understand it, it’s with an example:

Recoil_Pattern_X = [x1,x2,x3,x4,x5]
Recoil_Pattern_Y = [y1,y2,y3,y4,y5]
Recoil_Pattern_Delay = [d1,d2,d3,d4,d5]
Recoil_Use_Same_Delay = False
Recoil_Same_Delay = dc
Recoil_Pattern_Loops = k
Recoil_Pattern_Loops_Delay = h

In this case the function will perform the following actions (when activated inside aim
assistant):
- move the mouse (relatively, starting from the current position) on X axis by x1 and on
Y axis by y1
- wait d1 seconds
- move the mouse (relatively, starting from the current position) on X axis by x2 and on
Y axis by y2
- wait d2 seconds
- move the mouse (relatively, starting from the current position) on X axis by x3 and on
Y axis by y3
- wait d3 seconds
- move the mouse (relatively, starting from the current position) on X axis by x4 and on
Y axis by y4
- wait d4 seconds
- move the mouse (relatively, starting from the current position) on X axis by x5 and on
Y axis by y5
- wait d5 seconds
- wait h seconds
- start another loop for a maximum of k times (first time included) if k > 1

Recoil_Use_Same_Delay = False. If we put it True, d1,...,d5 will be replaced by dc.

The amount of x, y and d is not fixed, you can put it how many you need. Values are
separated by “,”. It’s important to put the same amount (number of numbers) for these 3
parameters:

Recoil_Pattern_X = [x1,...,xN]
Recoil_Pattern_Y = [y1,...,yN]
Recoil_Pattern_Delay = [d1,...,dN]

If you put something like this:

Recoil_Pattern_X = [x1,...,xK]
Recoil_Pattern_Y = [y1,...,yN]
Recoil_Pattern_Delay = [d1,...,dH]

The function will automatically stop at the lowest value between K, N, H and all other values
will be ignored.

The function will automatically stop if you stop pressing LCLICK or Aim Assistant button or if
there are no enemies near the crosshair.
I won’t answer to any stupid questions about this function. I repeat, this is not for dumb
people.

16.6) No Recoil
This will work in every case, not only if the aim assistant is active. It also will continue
recoiling (moving down) forever if you don’t stop pressing the button. So I suggest you to not
use this function (unless you only want to use no recoil and not aim assistant)

16.6.1) No Recoil In Game Button

You can assign a specific button to use No Recoil in game. It will work only when the button
is pressed.

Possible mouse button options: LCLICK, RCLICK, MB1, MB2, MIDDLE

Possible keyboard button: you can assign the keyboard letter or button you prefer
(examples: q, v, b, z, alt, ctrl, etc etc..)

Strongly Suggested Option: LCLICK

16.6.2) No Recoil On Off Button

To be able to use No Recoil, you’ll need to activate it. To do so, just press the related button
(you can change the key on config file):

Every time you press F7 that will print a log on cmd (to print if you activated or deactivated
it)

16.6.3) No Recoil Function Delay

If you notice strange behavior, keyboard lag, mouse shooting without stopping, you can put
here a low value (like 0.05, 0.01, 0.001, 0.0001). Recoil performances will be impacted of
course. Otherwise, don’t touch it.
16.6.4) No Recoil Parameters

These parameters determine the recoil strength:

NewRecoilDelay: For how long it will wait before going on with the “next iteration” while the
no recoil button is pressed
NewRecoilOffsetY: How much he will move on Y axis in “every iteration” (positive = down,
negative = up) while the no recoil button is pressed

16.6.5) Pattern Recoil Inside Aim Assistant

Please note: this is an optional no recoil mode, disabled by default. It is for experts, so
activate it only if you understand what it is (if you don’t have enough brain to understand
it, please give up). Anyway, expert users are free to share parameters and help you in
understanding/setting it (I won’t do so, it’s explained below, I can’t explain it better than the
example below).

To activate this different recoil mode, you have to put UsePatternRecoil = True:

Before describing it, please remember that the function will be also impacted by the following
parameters:

Please note: default values are for my in game sens, mouse type, mouse dpi, mouse
library, resolution, pc, etc. It will be impacted by a lot of things, so you’ll need to find
your values, don’t come to me complaining that it’s not working properly !

The function is composed by the following parameters:

zoom in:

Recoil_Pattern_X: this represents the values of the x coordinates the mouse will move on
each loop
Recoil_Pattern_Y: this represents the values of the y coordinates the mouse will move on
each loop
Recoil_Pattern_Delay: this represents the values of the delays the mouse will wait after
each movement
Recoil_Use_Same_Delay: If True, it will use Recoil_Same_Delay as delay after every
movement, ignoring Recoil_Pattern_Delay
Recoil_Same_Delay: the delay after each movement used only If Recoil_Use_Same_Delay
= True
Recoil_Pattern_Loops: you can decide to repeat the previously behavior for several times
Recoil_Pattern_Loops_Delay: delay after each repetition

The best way to understand it, it’s with an example:

Recoil_Pattern_X = [x1,x2,x3,x4,x5]
Recoil_Pattern_Y = [y1,y2,y3,y4,y5]
Recoil_Pattern_Delay = [d1,d2,d3,d4,d5]
Recoil_Use_Same_Delay = False
Recoil_Same_Delay = dc
Recoil_Pattern_Loops = k
Recoil_Pattern_Loops_Delay = h

In this case the function will perform the following actions:

- move the mouse (relatively, starting from the current position) on X axis by x1 and on
Y axis by y1
- wait d1 seconds
- move the mouse (relatively, starting from the current position) on X axis by x2 and on
Y axis by y2
- wait d2 seconds
- move the mouse (relatively, starting from the current position) on X axis by x3 and on
Y axis by y3
- wait d3 seconds
- move the mouse (relatively, starting from the current position) on X axis by x4 and on
Y axis by y4
- wait d4 seconds
- move the mouse (relatively, starting from the current position) on X axis by x5 and on
Y axis by y5
- wait d5 seconds
- wait h seconds
- start another loop for a maximum of k times (first time included) if k > 1

Recoil_Use_Same_Delay = False. If we put it True, d1,...,d5 will be replaced by dc.

The amount of x, y and d is not fixed, you can put it how many you need. Values are
separated by “,”. It’s important to put the same amount (number of numbers) for these 3
parameters:

Recoil_Pattern_X = [x1,...,xN]
Recoil_Pattern_Y = [y1,...,yN]
Recoil_Pattern_Delay = [d1,...,dN]

If you put something like this:

Recoil_Pattern_X = [x1,...,xK]
Recoil_Pattern_Y = [y1,...,yN]
Recoil_Pattern_Delay = [d1,...,dH]

The function will automatically stop at the lowest value between K, N, H and all other values
will be ignored.

The function will automatically stop if you stop pressing recoil button.

I won’t answer to any stupid questions about this function. I repeat, this is not for dumb
people.
16.7) New Flick
Thi is the new powerful flick! When you press the flick button, it will automatically move the
crosshair to the target and shoot ! So you can get insta-kill, but of course random teammates
will report you, so please be careful using it.

16.7.1) New Flick In Game Button

You can assign a specific button to use New Flick in game. New Flick will work only when
the button is pressed.

Possible mouse button options: LCLICK, RCLICK, MB1, MB2, MIDDLE

Possible keyboard button: you can assign the keyboard letter or button you prefer
(examples: q, v, b, z, alt, ctrl, etc etc..)

Personally, I deassigned RCLICK in game options, and I use RCLICK, I feel a lot
comfortable playing like that.

16.7.2) New Flick Delay

If you notice strange behavior, keyboard lag, mouse shooting without stopping, you can put
here a low value (like 0.05, 0.01, 0.001, 0.0001). New Flick performances will be impacted of
course. Otherwise, don’t touch it.

16.7.3) New Flick On Off Button

To be able to use New Flick, you’ll need to activate it. To do so, just press the related button
(you can change the key on config file):

Every time you press F3 that will print a log on cmd (to print if you activated or deactivated it)
16.7.4) New Flick Parameters

These are very similar to aim assistant parameters, but instead of having a precise target,
you have only Y and X offset. That’s because the high speed of this function needs a lot of
manual adjustment, so it’s better to just set manual offsets depending on your configuration
and FOV. Please note that FOV can’t be less than 50, or it won’t work as expected.

Speed must be very high ! Otherwise it won’t be able to flick to the target instantly ! If you
set it too low or too high, you won’t be able to move to the target (you will shoot before
arriving or you will pass the target), you need to find right values for you ! Just modify speed
and try !

16.8) Silent Aimbot

Thi is the new powerful silent aimbot! When you press the silent button, it will automatically
move the crosshair to the target, shoot and come back to the starting position, and you won't
even appear to have moved ! So you can get insta-kill, but of course random teammates will
report you, so please be careful using it.

16.8.1) Silent In Game Button

You can assign a specific button to use Silent in game. Silent will work only when the button
is pressed.

Possible mouse button options: LCLICK, RCLICK, MB1, MB2, MIDDLE

Possible keyboard button: you can assign the keyboard letter or button you prefer
(examples: q, v, b, z, alt, ctrl, etc etc..)

Personally, I deassigned RCLICK in game options, and I use RCLICK, I feel a lot
comfortable playing like that.
16.8.2) Silent Delay

If you notice strange behavior, keyboard lag, mouse shooting without stopping, you can put
here a low value (like 0.05, 0.01, 0.001, 0.0001). Silent performances will be impacted of
course. Otherwise, don’t touch it.

16.8.3) Silent On Off Button

To be able to use Silent, you’ll need to activate it. To do so, just press the related button (you
can change the key on config file):

Every time you press F4 that will print a log on cmd (to print if you activated or deactivated it)

16.8.4) Silent Parameters

These are very similar to aim assistant parameters, but instead of having a precise target,
you have only Y and X offset. That’s because the high speed of this function needs a lot of
manual adjustment, so it’s better to just set manual offsets depending on your configuration
and FOV. Please note that FOV can’t be less than 70, or it won’t work as expected.

Speed must be very high ! Otherwise it won’t be able to flick to the target instantly and then
come back to the original position without that movement to be noticeable! If you set it too
low or too high, you won’t be able to move to the target (you will shoot before near the target
but not on the target), you need to find right values for you ! Just modify speed and try !
16.9) Triggerbot
Arduino has a big problem with Triggerbot and shooting functions in general: after shooting
automatically, everything will stop for some seconds, and functions won’t work anymore,
unless you press again the button function. This doesn’t happen when you emulate left click
in another way or if you use a keyboard letter as an alternative primary fire key, but these
workarounds will be easily detectable by Vanguard, so that’s why I did not implement it. Also
New Flick and Silent Aimbot has the same problem, but it’s not an huge problem, you can
just press the button again and it will be strong enough.

Anyway, I still implemented it, but if you use it, sometimes it will not shoot to the enemy,
that’s a fact, it’s buggy. I think I can’t do anything at the moment, so please think about
before using it.

16.9.1) Triggerbot On Off Button

To be able to use Triggerbot, you’ll need to activate it. To do so, just press the related button
(you can change the key on config file):

Every time you press F6 that will print a log on cmd (to print if you activated or deactivated
it)

16.9.2) Triggerbot Delay

If you notice strange behavior, keyboard lag, mouse shooting without stopping, you can put
here a low value (like 0.05, 0.01, 0.001, 0.0001). Triggerbot performances will be impacted
of course. Otherwise, don’t touch it.
16.9.3) Triggerbot Always On

Of course you can also set triggerbot always active without pressing any button. But in this
case it will shoot to any object with the same color that you set (dead bodies, flowers, etc),
so random teammates will notice that.

You can do that putting this to True:

Of course you’ll need to activate it with On/Off button as always.

16.9.4) Triggerbot In Game Button

If you put TriggerbotAlwaysOn = False, you can set a specific button for Triggerbot (I suggest
RCLICK to use it with snipers):

You can assign a specific button to use triggerbot in game (or you can have it always on,
explained on chapter 16.9.3). Triggerbot will work only when the button is pressed.

Possible mouse button options: LCLICK, RCLICK, MB1, MB2, MIDDLE

Possible keyboard button: you can assign the keyboard letter or button you prefer
(examples: q, v, b, z, alt, ctrl, etc etc..)

16.9.5) Triggerbot Custom Parameters

Triggerbot has its own FOV X and Y. It uses RGB color (instead of HSV), please see color
codes and descriptions below and on config file comments.

TriggerbotColorTolerance: tolerance factor for color ranges, the more is high, the more it
will shoot, but the risk is to shoot also to unwanted things
TrigSingleShoot: if True, it will shoot only one time, if False, it will shoot for
TrigShootNumber times, waiting TrigShootsDelay after every shot.
16.10) Useful Materials
You can also refer to this old videos, some of the explained functions are still valid for latest
version:

DogeFree video: https://youtu.be/I-VJtkGc4bQ

V4.7 video: https://youtu.be/4ZcKo4mGw0w
V4.8 video: https://youtu.be/Dusmy9OOcd0

17) Optional: V4 Available and Downloadable Releases

I will not support anymore older versions, but you can still see changelogs and download
them on #vip-releases channel.

17.1) V4.2.2
Changelog:
- Added possibility to set a custom button for triggerbot (a keyboard letter, LCLICK, RCLICK)
- Added possibility to have Triggerbot always on (if you don't want to press a button)
- Added BBSAMANT library (to use also side buttons for some mouse tipes like razer, please
read istruction in READ ME file)
- Fixed LUNA library for triggerbot (but need to be tested)
17.2) V4.3

Changelog:
- Added recoil delay parameter to customize recoil (to make it going down slower or faster)
- Added possibility to use aim assistant with LCLICK

In progress:
- Added Silent Aimbot with parameters (but it's not working properly on my testing pc (I need
to investigate) you can try it if you want)
- I still need to understand why some fantastic parameters combinations make cheeto crash

17.3) V4.4

Changelog:
- Fixed random crash with custom settings (triggerbot fov, etc..)
- Added possibility to use MB1, MB2, MIDDLE mouse buttons
- Added possibility to use Custom Resolution (manually setting paramiters on Config.ini)
- Added general instructions to enable mouse side buttons (not working for every mouse).
Need to restart pc and reload library after substitution.

In progress:
- Silent Aimbot stil need to be fixed

17.4) V4.5

RELEASE NOTES:
- There were huge modifications on this update, cheeto structure has been dramatically
changed (inside)
- PLEASE read carefully Config.ini file, I've wrote there very useful information
- Every library was modified, so you must to reload the "_new" library version
- Added parameters at the end of the Config to disable unused features before starting
cheeto and incredibly boost performances
- Added Silent aimbot with custom parameters
- Added a New Customizable Recoil: by default it will work only with aim assistant, but you
can change it. There is also a function (activable/deactivable with f10 and active by default)
to make it work only when tracking, so normal gameplay won't be affected (and no need to
press any key except LCLICK and aimbot key).
- Both basic and new custom recoils will work even with aim assistant
- Please remember that settings for New Customizable Recoil and Silent aimbot are for MY

🎬 🤓
PC/MOUSE, so it's possible that you need to change parameters to make it work like on my
clips (or better )
17.5) V4.6

RELEASE NOTES:
- Please refer to V4.5 release notes

Changelog:
- Aim assistant + new custom recoil (only on "inside" option) a little bit improved: it will recoil
only if near head/neck
- Minor bug fixes
- BBSAMANT lbrary fixed

17.6) V4.7

HOW TO USE:
1) Remember to use new v4.7 libraries because everything changed (so v4.5 and v4.6
libraries are not supported)
2) Remember to not activate more than one function at a time (except for integrated recoil
and triggerbot that you can use inside aim assistant, but not together)
3) Watch the full video tutorial: (sorry for my english) https://youtu.be/4ZcKo4mGw0w
4) I know that are like 30 mins and you just want to play, but take a breath and watch the full
video! If you ask me questions for which the answer is in the video, I won't answer you!

17.7) V4.7.1

HOW TO USE:
Follow steps of v4.7

Changelog:
- Fixed Inside Aim Assistant Triggerbot for weapons like vandal

17.8) V4.8

PLEASE NOTE:
- Read V4.7 release notes and watch V4.7 video (https://youtu.be/4ZcKo4mGw0w). They
are stil valid for v4.8 (except for functions modified/deleted and new functions).
- If you never use Recoil Inside Aim Assistant, please set
NeverUseCustomRecoilInsideAimAssistant = True to improve performances
- Please open Config.ini file with Notepad++, it will be more readable and you could easily
read comments

Changelog:
- New Recoil Inside Aim Assistant completely refactored and now extremely powerful with a
lot of customizations. Please watch related tutorial: https://youtu.be/Dusmy9OOcd0. Note: If
you have AimAssistantAlwaysOn = True, to make racoil work set
AimAssistantInGameButton = LCLICK and NewRecoilInGameButton = LCLICK.
- Old Flick re-added as a further option (and New Flick is still present)
- Triggerbot completely modified. Now it will work well alone and with snipers.
- Removed Triggerbot inside Aim Assistant
- Fixed the problem of RCLICK as Aim Assistan button: now you don't need to repress it
again to track after a kill, it will track automatically next enemy (if present in the fov)

17.9) V4.8.1

PLEASE NOTE:
- Read V4.7 and V4.8 release notes and watch videos!

Changelog (based on what you requested):

- Added HideCMD. This function will use different Windows APIs, so I don't know if cheeto is
more sus with that, use at your own risk. Putting it True you can hide cmd, but you need to
do it before running cheeto, and to see cmd again you'll need to close and reopen cheeto
(and modify the value). Also, when you stop cheeto with F9, youl'll need to kill the empty
cmd on Task Manager (not difficult to find, not a big issue if it stays open, he will close
automatically when you restart/shut down pc).
- Added ConfigSelector.ini file. Just put there the config that you want and cheeto will use
that to load (or re-load) parameters. So you can keep more .ini files and easily swap them
without adjusting parameters
- Re-added HighCPU parameter. Don't use that if you did not use on previous versions
- Added the possibility to Activate/Deactivate recoil inside aim assistant without reloading
cheeto. Added log message. Please note that ActivateRecoil parameter is False by default,
so you need to put it True if you want to use recoil
- Fixed error when closing cheeto

TO DO:
- Try to fix triggerbot (very difficult due to arduino)

17.10) V4.8.2
PLEASE NOTE:
- Read V4.7, V4.8 and V4.8.1 release notes and watch videos!

Changelog (based on what you requested):

- Added Anti-Shaking function suggested by @DALIX. Default is False, so you need to
enable it if you want. This function will reduce speed when you are "near" the enemy. "Near"
is defined by distance parameters, while the new reduced speed is defined by new speed
parameters. It works better on shot/mid range. What's the purpuse of that ? You can
increase a little bit your aim assistan speed even if it makes you shake, because with this
function it will decrease near the target, so stop shaking while shooting. Example: my
optimal aim assistant speed is 0.5 (no shaking), while 1 makes me shake a lot. Now I can
use 1 as main aim assistant speed and 0.5 as anti-shaking speed. Remember to not
increase speed too much or it won't well.

TO DO:
- Try to fix triggerbot (very difficult due to arduino)

17.11) V4.8.3
Changelog:
- Increased delay on functions activation/deactivation, to avoid infinite bugged print that
sometimes happens
- Added the possibility to print FPS. See chapter 16.2.8 of the guide. Default is False.
- Added the possibility to choose a new (more performant) screen capture method. Could not
work for everyone, so by default is not active. See chapter 16.2.9 of the guide. Also, use at
your own risk.

TO DO (on next release because I forgot):

- Add Old Flick custom parameters (fov, speed x and y, target, correction x and y)

17.12) V4.8.4

Changelog:
- Added a new option (requested by Apple and Blaxe) so that Aim Assistant will be more
legit (but also less powerful). Default is False (and I suggest you to not use it). See chapter
16.3.8 of the guide.
- Added Custom parameters for Old Flick (Fov X and Y, Speed X and Y, Aim Correction X
and Y, Aim Target, Smooth), so that could be set differently than Aim Assistant. See chapter
16.4.4 of the guide.
- Please remember the new optional and more performant screen capture method
introduced on V4.8.3. See chapter 16.2.9 of the guide.

17.13) V4.8.5

Changelog:
- Added New Pattern Recoil fully customizable. By default it’s disabled, so you need to
enable it if you want. See chapter 16.6.5 of the guide.
- Added New Pattern Recoil Inside Aim Assistant. fully customizable. By default it’s
disabled, so you need to enable it if you want. See chapter 16.5.5 of the guide.
- Please remember the new optional and more performant screen capture method
introduced on V4.8.3. See chapter 16.2.9 of the guide.

17.14) Safety

Changelog:
- The base is v4.8.5, just removed/modified things
- Possibility to rename the exe with what you prefer
- New icon
- New builder
- Functions and variables renamed
- New protection packer (antivirus will flag it, so please disable it)
- Removed Triggerbot, No Recoil (every), New Flick and Silent
- Removed settings prints and re-load prints
- Removed option to hide cmd
- Removed Shitty Legit option
- removed Print FPS function
- You can only use Aim Assistant or Old Flick
- Remaining options are the same as V4.8.5, no need to update guide

17.15) V4.8.5.1
Changelog:
- Same as V4.8.5
- Different builder, packer, protector, icon, name, hash
- Possibility to change cheeto name
- Removed HideCMD option
- Added random prints

17.16) V4.8.6
Changelog:
- The base is V4.8.5.1
- Added Random Target function to Aim Assistant: if enabled it will automatically choose a
random target (chest, neck, head and intermediate points) every time you press the aim
assistant button. See chapter 16.2.9 of this guide. By default it is disabled
- Removed “ActivateRecoilInsideAimAssistant” parameter (mainly because of retards not
reading the guide), so now it’s not necessary anymore, you just need to wait some seconds
more when activating that function, but then it will work as before
- Removed “ColorPurpleMode” and “SetCustomColor” parameters, cheeto will directly use
lower and upper color ranges
- Modified speed for New Flick and Silent: now you can set different speed for X and Y
- Possibility to rename the exe with the name you prefer
- Updated icon, hash, builder, packer, libraries
- Added gpu/monitor parameters for DXCAM
- Added smurfed_new library
- Removed/substituted sussy prints
- For some errors, cheeto will create a dump.err file. In that case send it to me to know what
you missed.
- All sussy variable and function names renamed
- All Config.ini parameters renamed to be less sussy (4 = A, 3 = E, 0 = O, 1 = I)
- Modified Scr33n_C4ptur3_M3th0d, 41m_4ss1st4nt_T4rg3t and 0ld_Fl1k_T4rg3t option
names to be less sussy (M instead of MSS, D for DXCAM, H for HEAD, C for CHEST, N for
NECK )
- Guide updated

17.17) V4.8.7 and Safety

Changelog:
- POSSIBILITY TO USE IT WITHOUT USB HOST SHIELD !!
- Added no_host library, which allows you to use it without USB Host Shield, connecting the
mouse directly to the pc. To do that you must spoof arduino following chapter 25 of the guide
or this video: https://www.youtube.com/watch?v=CcfnBOqdLVg
- Added Random Target function to Old Flick (chapter 16.4.5)
- Added Quick Settings Updater (chapter 16.2.10)
- Guide updated, every step reports if it is mandatory or not for host/no-host shield users

To do:
- I have huge problems implementing humanized movement, so I'll keep it for next releases.

17.18) Safety V3.1

Changelog:
- Now it is possible to use 3 different buttons for Aim Assistant. If you only need 1, just set all
the 3 buttons the same
- Now it is possible to use 3 different buttons for Old Flick. If you only need 1, just set all the
3 buttons the same
- Added 41m_4ss1st4nt_4lw4ys_0n_St0p_Butt0n button for people using Aim Assistant
always on: auto tracking will stop if the button is pressed, and start again if not pressed.
Please note that this button can't be the same as Aim Assistant Buttons, otherwise it won't
work.

To do:
- I have huge problems implementing humanized movement, so I'll keep it for next releases.
17.18) V4.8.8

TEST IT AT YOUR OWN RISK: I don't know if Recoil, New Flick and Silent are safe.

Changelog:
- Different builder
- Removed Triggerbot (because it's detected for sure)
- Re-added HideCMD option
- Now it is possible to use 3 different buttons for Aim Assistant. If you only need 1, just set all
the 3 buttons the same
- Now it is possible to use 3 different buttons for Old Flick. If you only need 1, just set all the
3 buttons the same
- Added 41m_4ss1st4nt_4lw4ys_0n_St0p_Butt0n button for people using Aim Assistant
always on: auto tracking will stop if the button is pressed, and start again if not pressed.
Please note that this button can't be the same as Aim Assistant Buttons, otherwise it won't
work.

To do:
- I have huge problems implementing humanized movement, so I'll keep it for next releases.

17.19) V4.8.9

REALLY IMPORTANT:
- Before using it, please change hash using the tool on #vip-tools channel (explained at
chapter 25 of the guide)

Changelog:
- Different builder
- Possibility to change hash
- Re-Added auto-shoot option inside aim assistant

To do:
- I have huge problems implementing humanized movement, so I'll keep it for next releases.

18) FAQ (V4 only)

BEFORE OPENING ANY TICKET AND ASKING ANY QUESTION, PLEASE HAVE A
LOOK ON THIS LIST !

18.1) COM error

Q) I have a similar COM error:

A) You put the wrong COM port on Config file. Please read the guide again carefully and use
your brain.

—---------------------------------------------------------------------------------------------------------------------

18.2) Arduino Uno

Q) Can I use Arduino Uno ?

A) No !

—---------------------------------------------------------------------------------------------------------------------

18.3) Without Host Shield

Q) Can I use Arduino Leonardo without USB Host Shield ?

A) Yes! It’s explained in the guide how to do it in that case !

—---------------------------------------------------------------------------------------------------------------------

18.4) Become VIP

Q) How to become Vip ?

A) Everything is explained on #vip-rules channel !

—---------------------------------------------------------------------------------------------------------------------

18.5) Free version

Q) Is there a free version ?

A) Please don’t ignore bot welcome message and read #valorant channel from the top !
—---------------------------------------------------------------------------------------------------------------------
18.6) Mouse not moving

Q) My mouse is not moving, what can I do ?

A) Did you follow every step of this guide and try every library ? If not, do it.

If yes:In general, if mouse does’t work, it could be due to:

- Bad/missing soldering or broken host shield
- Not original Arduino Leonardo
- Windows needs to be rebooted
- Wrong/incompatible library
- Windows needs to be formatted
- USB Host Shield not well connected to Arduino Leonardo
- Shitty Micro USB cable
- You have to try to set CustomResolution = True

—---------------------------------------------------------------------------------------------------------------------

18.7) Anydesk help

Q) Can you install everything for me through Anydesk ?

A) No ! I suggest you to use your brain. But maybe if you pay my time I can do it.

—---------------------------------------------------------------------------------------------------------------------

18.8) HWID Doesn’t match

Q) HWID Doesn’t match. Ask for key reset.

A) It means that you spoofed/formatted your pc, so you need a key reset. Please see
chapter 23 of the this guide.

—---------------------------------------------------------------------------------------------------------------------

18.9) Can I be banned ?

Q) Is it detected/bannable ?
A) Read the Introduction ! Anyway, I’m playing from August 2022 and no ban

—---------------------------------------------------------------------------------------------------------------------

18.10) Which version of cheeto is better ?

Q) Which cheeto version should I use ?

A) I suggest the last, but use the version you prefer

—---------------------------------------------------------------------------------------------------------------------

18.11) Is my Host Shield broken ?

Q) How can I know if I broke USB Host Shield ?

A) Please refer to optional part on chapter 11

—---------------------------------------------------------------------------------------------------------------------

18.12) Cheeto shaking

Q) Cheeto works but it’s shaking so much !

A) Carefully read chapters 16.3.2 and 16.3.3

—---------------------------------------------------------------------------------------------------------------------

18.13) No recoil not working

Q) No recoil inside aim assistant is not working !

A) I guess you missed chapter 16.5.1

—---------------------------------------------------------------------------------------------------------------------

18.14) Cheeto/Aim Assistant not working

Q) I’ve activated Aim assistant, but it doeasn’t work !

A) Please read chapters 12, 13 and 14. You probably missed something there. You can also
try setting your resolution manually with CustomResolution = True.
Another common error is forgetting to set MouseType according to the library that you are
using.

—---------------------------------------------------------------------------------------------------------------------

18.15) Aims outside enemy (sky, ground, etc)

Q) I’ve activated Aim assistant, but it aims outside the enemy !

A) This will probably fixed setting your resolution manually and activate CustomResolution =
True. If not, the problem could be the library: doge_simple_new usually has this problem for
some mice. In this case, try using luna_new instead.

—---------------------------------------------------------------------------------------------------------------------

18.16) Formatted pc and mouse still working

Q) I formatted my pc but mouse is still working on Arduino/USB Host Shield, why ?

A) It’s normal if you previously loaded a library, because arduino has internal memory, read
chapter 10.

—---------------------------------------------------------------------------------------------------------------------

18.17) Key not working on zip file

Q) The given key is not working to unzip cheeto.

A) You are dumb. It’s not the zip password, is the key for cheeto. Unzip password is written
on file name (and is 1234). Also written on chapter 8.

—---------------------------------------------------------------------------------------------------------------------

18.18) COM different than yours

Q) My COM is different than yours, it’s normal ?

A) Of course. Read carefully chapters 10 and 13 to know why.

—---------------------------------------------------------------------------------------------------------------------
18.19) Legit config

Q) Which is a legit config ?

A) It depends. You can reduce speed, set smooth, add a delay, change the aim target, add
anti-shaking, reduce fov. It’s up to you, you can customize it as you prefer. Please also have
a look on #clips and #vip-configs.

—---------------------------------------------------------------------------------------------------------------------

18.20) Port grayed on Arduino IDE

Q) Why is my Port grayed?

A) If you followed correctly every step, it’s something related to Micro USB cable or Arduino
Leonardo Board. If previously it worked, maybe try just rebooting pc, sometimes happens.

—---------------------------------------------------------------------------------------------------------------------

18.21) GetItem/KeyError in config

Q) I have an error like this:

A) Please use your brain. When you see a message like this, it means that something is
missing on the Config.ini file. So, you cancelled something, or you are using the wrong
config file. Please note that different versions have different config files !

—---------------------------------------------------------------------------------------------------------------------

18.22) Enable side buttons

Q) What should I install to make all the buttons on the mouse work ?

A) Answer is on chapter 9. If you use bbsamant see also chapter 10.2

—---------------------------------------------------------------------------------------------------------------------

18.23) Aims over the head

Q) Aim Assistant aims over the head !

A) You probably increased fov without putting AimAssistant_HeadOffset_Y = 0. Please read

chapter 16.3.1

—---------------------------------------------------------------------------------------------------------------------

18.23) Aims on dead bodies

Q) How to make Aim Assistant not aim to dead bodies ?

A) There is no solution for that, since they have the same color as enemies. You can remove
dead bodies but you’ll still have a colored marker. The only way is to reduce fov to reduce
dead bodies aim rate. I play with 30 fov.

—---------------------------------------------------------------------------------------------------------------------

18.24) Hwid reset registration - license already used

Q) I tried to register to hwid reset and it says “License already used” !

A) I don’t know why it’s so difficult to understand. Carefully read chapter 23. It says to NOT
REGISTER. BUT TO LOGIN WITH USERNAME AND PASSWORD (THAT ARE YOUR
KEY)

—---------------------------------------------------------------------------------------------------------------------

18.25) Couldn’t find board on the selected port

Q) I have this error while loading a library:

A) A possible cause could be a bad Micro Usb cable or a broken Arduino Leonardo. But
more often it is just a random problem: in that case, to fix it just try changing port or
disconnect and reconnect arduino or reboot pc.

—---------------------------------------------------------------------------------------------------------------------
18.26) Library loaded from IDE without errors

Q) Library loaded from IDE to Arduino Leonardo without errors means that USB Host Shield
is working well ?

A) No. It only means that Arduino Leonardo is working and COM is recognized. You loaded
inside Arduino memory, not Host Shield, so it could still be broken.

—---------------------------------------------------------------------------------------------------------------------

18.27) Are my settings legit ?

Q) Are my settings legit ?

A) How could I know ? You must provide a gameplay video to know that. Why ? Read
chapter 16.3.2, it’s extremely important that you understand the basic concept inside.

—---------------------------------------------------------------------------------------------------------------------

18.28) Multiple enemies in FOV issue

Q) Why is cheeto aiming in the middle if there are 2 or more enemies in FOV ? Is it possible
to solve it ? FIX IT PLEAAAASEEEEEEE

A) Generally, it’s possible to fix this issue, but not on V4.X and Safety versions. To fix it I
should change the tracking algorithm, and I won’t do that. This problem is “solved” on New
Private Aim Assistant Method, because the algorithm is different.

Let’s see in details:

For V4.X and Safety, this is what cheeto is seeing with 300 FOV:
He sees one big enemy ! So it goes crazy !

This is with 50 FOV:

He will probably fail as well in this situation too.

For New Private Aim Tracking Method:

This is with 50 FOV:

As you can see, every enemy is perfectly highlighted with a precise contour, so cheeto will
be able to distinguish every enemy. But, the game is not static, players are moving, so
cheeto will probably keep switching between different targets in game, even if the first target
is not dead.

CONCLUSION:

To fix both problems you need different algorithms and/or different cheetos, and at the
moment I don’t have time to develop it, maybe in future.

—---------------------------------------------------------------------------------------------------------------------

18.29) Mouse if drifting

Q) Mouse is drifting to the bottom right of the screen if I spam move it in a circle. How to
solve ?

A) Just add this in code:

—---------------------------------------------------------------------------------------------------------------------

—---------------------------------------------------------------------------------------------------------------------

—---------------------------------------------------------------------------------------------------------------------

—---------------------------------------------------------------------------------------------------------------------

19) Feedbacks and Suggestions

For DogeFree, you can leave your feedback on the following server channel:

For V4, you can leave your feedback on the following server channel:

You can write your suggestions and requests here:

20) Custom Private Cheeto Implementations
Starting from 16/07/2023, every vip user can use a new tool to randomly change the hash of
vip and vip-plus cheeto’s exe, so it will become an unique cheeto: if a the released exe or an
user exe will be sent to anti-cheet devs and detected, you will be safe if you changed the
hash. Due to this, I decided to suspend the current private options. You can still request
custom implementations, but there won’t be fixed prices and you can just discuss about that
with me in a private message on discord.

20.1) New Private Aim Assistant Tracking method

This is a short video of it: https://youtu.be/p27SKTimwJA

Starting from 16/07/2023 it will be available for every private user for Arduino Leonardo and
for every raspberry users Raspberry Pi Pico W.

If you are vip (to become vip the cost is 30), you can purchase raspberry cheetos for 30 or
private cheetos for 30 (to have both you must pay 60)

21) Overwatch 2

Everything like valorant, simply change color according to game color and adjust Y and X
offset according to enemies:

Colors:

HSVCustomLower = [139, 96, 139]

HSVCustomUpper = [157, 255, 255]

HSVCustomLower = [139, 96, 129]

HSVCustomUpper = [169, 255, 255]

HSVCustomLower = [139, 95, 154]

HSVCustomUpper = [153, 255, 255]

HSVCustomLower = [139, 96, 129]

HSVCustomUpper = [169, 255, 255]

HSVCustomLower = [140, 110, 150]

HSVCustomUpper = [150, 195, 255]

22) Modern Warfare 2

To be able to use aimbot on MW2, just set the following parameters:

You have to turn off hit markers in game settings, so it can see the purple!

AimAssistant_FOVx = 100
AimAssistant_FOVy = 100

Video example (it aims below the point): https://streamable.com/7viajx

Other video examples on #clips

23) Reset HWID

BEFORE STARTING, PLEASE REMEMBER: IF YOU CHANGE USERNAME AND

PASSWORD YOU ARE RETARD, BECAUSE YOUR KEY WON’T WORK ANYMORE
(AND YOU WILL GET “ALREADY USED” MESSAGE). NO MORE EXCUSES, IF YOU
IGNORE THAT YOU WILL CAUSE ME TO LOSE MY TIME TO FIX IT, SO I WILL FORCE
YOU TO WAIT 7 DAYS BEFORE FIXING. IF YOU COME ON DM COMPLAINING ABOUT
THAT, THE PUNISHMENT WILL BE INCREASED. PRESSING SAVE BUTTON IT’S AN
INTENTIONAL ACTION, IF YOU DO THAT IT’S NOT “BY MISTAKE”.

SO:
VERY IMPORTANT: DON’T MODIFY YOUR USER OR PASSWORD (I can’t disable that
function unfortunately) AND DON’T CLICK SAVE FOR ANY REASON, OR YOU’LL
MESS UP EVERYTHING AND KEY WON’T WORK ANYMORE !! IF YOU DO THAT YOU
ARE DUMB AND I’LL FORCE YOU TO WAIT 7 DAYS BEFORE DELETING YOUR KEY
AND CREATING A NEW ONE TO FIX !!

Now, if it’s clear, you can follow this procedure to reset HWID:

Before resetting HWID you need to log out/close cheeto and close cmd, or won’t work.

You can reset the HWID by your own 1 time per day if you are VIP, while 1 time per week if
you are using the free version.

Log in (do not register !!) to the site related to the cheeto that you want to reset. User and
password are your key (XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX). Please
remember that you can’t login if you are logged in with cheeto, and to log out after resetting,
or you can’t use it on cheeto !

DogeFree: due to some retarded free users who broke the rules, now is not possible
anymore to reset HWID for free users

V4 and New Safety: https://keyauth.cc/panel/DogeOscuro/AnimaliV4

Old Safety (only private versions): https://keyauth.cc/panel/DogeOscuro/DogeV4Safety

AI cheeto V2: https://keyauth.cc/panel/DogeOscuro/AnimaLoide

Animali C++: https://keyauth.cc/panel/DogeOscuro/AnimaliCPP

New Private Tracking method: https://keyauth.cc/panel/DogeOscuro/DoggePrivate

LOGIN CREDENTIALS ARE username = YOUR CHEETO KEY AND password = YOUR
CHEETO KEY, why is it so difficult to understand ? Are you really so retard ? You did
more complicated things before arriving at this point, and now you are so retard that
you can't even access a site with username and password ?

And simply click on the Reset HWID button.

IMPORTANT: If I notice that you are doing weird things with your key, I’ll insta ban you !!

24) Full Stack with cheeto

REMEMBER:
The best way to not be reported is to play full stack with friends and/or cheeters.
So, I've created different private servers for different regions to play full stack with colorbot
cheeters, other cheeters or people without cheeto but that know everything and won't report
us. Feel free to join and invite trusted friends:

AP: https://discord.gg/GQJr2HraWC
BR: https://discord.gg/YeHZhegyCB
EU: https://discord.gg/MnDWGa2rqA
KR: https://discord.gg/k26BrcAwrx
NA: https://discord.gg/hMzWEqMq6c
LATM: https://discord.gg/HwV4cuzesS

Servers are almost empty for now because they are just new, so please don't leave them.

25) Change Hash

If you are a VIP user, you have also access to #vip-tools channel. Here you can find the
Doge Hash Changer tool. You can use it to change the hash of the exe with a random one,
so it will be very similar to a “private/custom” exe, and you won’t be banned if someone
sends it to Riot.

To do it, follow these steps:

1) Unzip the cheeto you want to modify and open the unzipped folder. Unzip the Doge Hash
Changer where you prefer.

2) Copy the cheeto exe from the cheeto folder inside the Doge Hash Changer folder:
3) Open the change_hash.ini config file and insert your Arduino Colorbot V4 key and the
name of the exe. Then of course save it.

4) Open cmd as admin, move to the Doge Hash Changer folder and run change_hash.exe :
5) Now the exe hash has been successfully modified. Move the modified exe inside the
cheeto folder (substituting the original one of course). And that’s it!
26) Ban Report Rules

IF YOU DON’T PROVIDE THESE INFO (OR LIE OR PROVIDE INCOMPLETE INFO) AND
JUST SPAM VALO BAN SCREEN OR SAY YOU WERE BANNED, YOU ARE RETARD,
AND YOU WILL BE MUTED FOR A WEEK !!!

So guys, when someone is banned, he is usually just spamming val ban messages
complaining about it. That’s not good and not constructive. It does not provide any help, only
contributes to creating panic. Let’s see which information you need to send on public chat
after getting a ban. If you don’t want to waste your time and don’t have time to report
complete information, just don’t complain about the ban !

I’ve also created a #vip-ban-report channel on which you can write this information.

PLEASE NOTE:
- IF YOU WANT TO WRITE IN THIS CHANNEL, YOU'LL NEED TO SEND A SINGLE
MESSAGE WITH EVERY OF THE POINT BELOW COMPLETED !!
- IF YOU DON'T WANT TO FILL ONE OF THESE POINTS, JUST REPORT IT EMPTY OR
WITH THE MOTIVATION, EXAMPLE: 9) I don't remember
- IF YOU DO IT WRONG (MISSING POINTS OR MULTIPLE MESSAGES) OR IF YOU LIE,
YOU WILL BE MUTED FOR A WEEK
- IF YOU USE THIS CHANNEL TO DISCUSS ABOUT ANYTHING OR ASK QUESTIONS,
YOU WILL BE MUTED FOR A WEEK

So, you need to provide:

1) Cheeto version
2) Cheeto config
3) If you are playing legit, semi-legit or un-legit, but you need to provide proofs about that,
like a video of your gameplay, cause some retards thought to play legit but actually they
were too sussy/blatant/shaky !
4) The function/s that you used
5) If you are using host shield or not
6) If your arduino is swoofed or not
7) If you play fullstack or with random teammates
8) If random teammates or opponents reported you (because they wrote that on chat etc)
9) Stats like HS%, average kills per match, k/d etc
10) Rank on which you played while you got ban
11) If you play comp or normal
12) How long have you been playing with cheeto
13) If you loaded cheeto while valo is opened
14) If you were previously banned, and in case yes, how did you swoof, if you are playing on
the same connection/ip of the ban
15) If you got VAL5, 152 or 61
16) If it’s account or HWID ban
17) If you used/tested other cheetos/programs
18) If you used/tested other cheetos/swoofers for other games
19) If the account on which you are playing is shared
20) If the account on which you are playing is a NFA or FA purchased on some shops
21) Day of the ban. Was it near a new Valo update?
22) Banned Valorant account/s ID

IF YOU DON’T PROVIDE THESE INFO (OR LIE OR PROVIDE INCOMPLETE INFO) AND
JUST SPAM VALO BAN SCREEN OR SAY YOU WERE BANNED, YOU ARE RETARD,
AND YOU WILL BE MUTED FOR A WEEK !!!