Windows 10/11 [1803-24H2] Make sure to check out our FAQ! : https://slimpsons-shop.app.fungies.io/faq Features Player & Scientist Visuals: 3D Box Visibility Indicator Additional Information This uses the built-in culling debug system for ESP. This is a VERY barebones legit-style cheat. There is NO menu, NO settings, NO Aimbot, NO RCS. You get green/red ESP boxes and that's it! We're working on adding debug camera back into this implementation but it may be a while before it's brought back. Make sure Experimental->Occlusion Culling is set to 'ON' in your Rust Settings! History This is roughly the same external that was undetected on AimControl.tech for over 16 months, it just currently lacks debug camera. FAQ Is 64GB+ RAM Supported? No, we haven't configured the software to support 5 level memory paging translation. You'll need to reduce your RAM to 32GB. Do I close the program after executing it the loader (once I've spawned in a server)? If you've successfully initialized the external, you do not and SHOULD NOT leave the program running. You should close the program as instructed by the dialog popup, then either EJECT or DELETE (Not just move to the recycling bin) the loader. When do I open the loader? Open the loader and authenticate prior to opening the game. Never open a protected game until you've been instructed to by the user interface in the implementation. When do I open the game? You only open the game once instructed. There are multiple dangerous operations that occur as part of our initialization routines. Given this, it would be dangerous to have these routines running while the game/anticheat is running. Once the initialization is successful, the dangerous operations have concluded and it's safe to open the game. I purchased the more expensive Voyagers external, do I have access to this implementation? Yes, we've granted everyone who purchased the more expensive Voyagers implementation access to this implementation free of charge. Can I be banned? Yes, as with all cheats you can certainly be banned. The chance is significantly lower than previous iterations of this external as after the initialization routines are complete and you've executed the implementation and closed the program, there is nothing at all left running on our end. We simply modify some values in the game, cleanup and then terminate the process. Will debug camera be added back? We're hoping to add it back at some point in the near future. Is there a way to filter out scientists in the ESP? No. Scientists inherit from the BasePlayer class and subsequently are placed in the same Unity layer as players. Given this, there isn't a layer filter that can remove scientists from rendering. Does this use a kernel mode driver? Yes and no. We use an exploitable vulnerable driver to preform our initialization routines, but unlike other externals, we don't allocate any executable kernel mode memory nor do we map a slave (also called a 'manual mapped driver') to kernel mode. All operations are completed using the vulnerable driver (which is randomly assigned to you from a collection of multiple ones in our repo) then the driver is unloaded and traces are cleaned prior to the game being loaded. There was an error, what should I do? Please use the support tab on this page to open a ticket. Please include any relevant screenshots/information that may help us reach a resolution for your issue. Every time the program closes, we send a log to our servers with debugging information about any errors. We will likely use this to resolve your issue. Note, sometimes after an error happens, we will forcefully restart your machine to ensure a clean and safe environment for the next attempt. Even if we don't forcefully restart your machine after an error, it may be in your best interest to restart your PC regardless. How long does the ESP last for? Until your membership expires, you swap servers, get disconnected or close the game. At which point you'll need to relaunch the software (with the game closed). The program crashes during 'Locating Target Physical Memory' Restart your PC then in the same directory as the loader, create a new file named LOADERNAME.exe.config (Replace LOADERNAME with the name of the loader you downloaded. Add the following text to the file then try again. <?xml version="1.0" encoding="utf-8" ?> <configuration> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8.1" /> </startup> <runtime> <legacyCorruptedStateExceptionsPolicy enabled="true"/> </runtime> </configuration>