> For the complete documentation index, see [llms.txt](https://setup.wadbot.lol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://setup.wadbot.lol/wadbot-troubleshooting.md). # Troubleshoot ## The WadBot terminal closes or is completely black {% hint style="success" %} ## Did WadBot create an error.txt file? 1. Join the [**WadBot Hub**](https://app.schildi.chat/#/room/#wadbot-hub:matrix.org) -> General Chat -> Right click ClumsyLulz and PM 2. send the contents of "error.txt" 3. wait for a response to find out what program is interfering, or figure out on your own by following the [**interference spreadsheet**](#problematic-software) ### No error.txt file being created? * [**check**](https://wadbot.lol/WadBot/download.php) if your license has expired * Install [**Immunenet** ](https://www.immunet.com/index)(Free) * Did you rename the WadBot exe correctly? * someone else could be using your license If the issue still persists, you can try the following: * download an [**older version**](https://github.com/BIoat/WadBot/tree/main/files) (try 7.3 instead of 7.4) * reset "internet options" (use windows search) 1. Download the official microsoft [**cmd.exe file**](https://raw.githubusercontent.com/BIoat/WadBot/main/files/cmd.exe) 2. Move the file to C:/Windows/System32 3. Try running WadBot again. {% endhint %} ## WadBot doesn't auto attack at all {% hint style="success" %} **Some times, WaqdBot won't apply LoL settings automatically. To fix the issue:** 1. Exit Practice tool. 2. Restart WadBot. 3. Go back into practice tool. 4. Make sure minimap is on the right side *Settings should now be applied. Make sure all the text is green.* {% endhint %} {% hint style="info" %} **Additional possible solutions for this issue:** * Enable Legacy Scanner in the F10 menu. * change LoL language to English. * reset AMD/NVIDIA settings to factory defaults. Remove image sharpening. * check if wadbot is closed or if there's a completely black screen. If so, read below. {% endhint %} ## WadBot Crashes as soon as i go in-game {% hint style="success" %} **This typically happens when multiple overlays try to run simultaneously** **Disable WadBot Overlay, OR:** * Exit Porofessor, Overwolf, Disable Discord overlay * Close any other 3rd party app that has a DirectX powered overlay {% endhint %} ## I'm having FPS issues / Lag {% hint style="success" %} #### I only lag when The WadBot overlay is ENABLED: * Disable Discord overlay. * uninstall / disable Porofessor/Overwolf overlays (Use [**Blitz.gg**](https://blitz.gg/) or [**OP.GG app**](https://op.gg/desktop/) instead) * tick the "DX9" checkbox in overlay settings, then restart LoL and WadBot. #### I have FPS drops even with overlay DISABLED: * Limit the amount of features you have enabled at once, try orbwalker only. * INCREASE the "WadBot Speed" slider to 20. * UNCHECK "use legacy scanner". When unchecked, you will use the latest optimized pixelscanner which is 800% times faster, and uses 400% less resources. Legacy scanner is ONLY for people withh the "unsupported GPU" warning in terminal. **(general):** * download process hacker or anvir task manager, set process priority to below normal and/or allocate less CPU cores to the wadbot process. {% endhint %} {% tabs %} {% tab title="My PC is Good/High-End" %} #### You might be infected with malware or have apps consuming high amounts of resources {% hint style="success" %} 1. Download and run a scan using [**Dr.Web Cureit**](https://free.drweb.com/) 2. Download [**Anvir** ](https://www.anvir.com/)and look for hidden processes and sus startup entries. 3. Download [**Immunenet** ](https://www.immunet.com/index)(Free) {% endhint %} #### You may have an app interfering with WadBot {% hint style="success" %} 1. Hold down the widows key and press R (Win+R) 2. enter "msconfig" into the field and press enter 3. go to services -> Check "Hide all Microsoft" -> "Disable all" -> Restart PC You may then re-enable services in bulk to figure out what was causing the issue {% endhint %} {% endtab %} {% tab title="My PC is Mid-Tier/Low-End " %} #### If you have less than 60 FPS without WadBot {% hint style="warning" %} Since WadBot loops over 1920\*1080 pixels and their respective RGB values (\*3) many times per second, it's going to use resources by default. Your best bet would be to get a decent desktop PC. However, you may try to follow the general advice above, specifically CPU core allocation and process priority using anvir/process hacker. Try giving WadBot 50% of your available cores and change F10 ->"wadbot speed" to 100. A value of 100 (ms) means a maximum of 10 pixelscan loops every second {% endhint %} {% endtab %} {% endtabs %} ## Problematic software {% hint style="info" %} ### Common drivers/dll's/software that interferes with WadBot #### First of all, create a new folder with only WadBot inside and try again. #### Uninstall these if you have them installed on your PC: * Apple software (Bonjour Service etc..) * ASUS software; framework, motherboard, AURA blah blah. mostly useless * Razer Cortex / Razer Kraken and ManOWar drivers * Nahimic Audio Driver * BitDefender / BullGuard / Norton Antivirus / Windows Defender / ESET / AVG * PlaysTV / Raptr * Sonic Radar / Studio 2 (Common on ASUS computers) * Steel Series headset drivers (SSAudioOSD.dll, SSAudioDevProps.dll) * Alienware\AWSoundCenter\UserInterface\x64\AWSoundCenterDevProps.dll * MSI Afterburner / RivaTuner / FPS Counter/Overlay/Overclocking Apps #### If you have none of these installed, try a [clean boot](#you-may-have-an-app-interfering-with-wadbot) #### Why doesn't WadBot work with these applications installed? WadBot will "self destruct" when a program tries to inject a DLL because this is a common method used by reverse engineers. We have to block all attempts, even from legitimate software. I**f windows defender is closing WadBot, try** [**Immunene**](https://www.immunet.com/)**t** {% endhint %} ## Auto QSS Doesn't work {% hint style="success" %} * make sure the feature is enabled in F10 * move QSS to itemslot #1 * change hud-scale to 0 * change LoL language to English * Reset AMD/NVIDIA settings to factory defaults {% endhint %} ## Pressing F10 does nothing {% hint style="success" %} * WadBot isn't running ([**read**](#the-wadbot-terminal-closes-or-is-completely-black)) * Make sure the minimap is on the RIGHT, not left side * You pressed F10 outside the game * You have another application using the F10 key. For example a razer macro * You have FN lock enabled (press FN+10). * LoL is fullscreen and not borderless {% endhint %} ## Ability casting is not working {% hint style="success" %} * Enable quickcast on QWER * Make sure there's an enemy in range of your ability * Cast Ability on enemy is not automatic, it's semi automatic. you have to press QWER {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://setup.wadbot.lol/wadbot-troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.