Last game update: Fri, Jul 17, 2026 01:39 (CEST) (Read) - Cheat status: possibly not up to date
|
Detection history
|
|
04-May-26, 23:54
|
||
|
||
|
Hey everyone. I’ve been looking into HexUI lately, and while their marketing and common sentiment often lean toward them being "undetected," I’m looking for a bit more transparency regarding the actual track record. We all know that in the world of software like this, "100% undetected since launch" is a heavy claim to make. I’m curious to hear from long-term users or those who follow the scene closely about the nuances of their history. Specifically: Has there ever been a full-scale detection? What about "partial" or "feature-specific" detections? I’ve seen cases with other providers where a specific feature (like a certain glow or a specific aim-assist method) gets flagged, affecting only a subset of users. Did HexUI ever go through a phase like that? Red trust issues: Even if there wasn’t a formal "VAC/Ban" wave, has there been a period where the software was suspected of causing "Red Trust" or lower trust scores for the userbase? Looking forward to some honest insights , I know hexui is a old-school provider, but never tried until now, but since it's one of the providers that pass the test of time I'm really considering giving a go. |
||
|
05-May-26, 01:07
|
||
|
||
|
Yes we had a partial on trial users around 9-years ago, then vac revisited to correct their mistake 2-months later and did a full scale, then we did a lot of corrections to our protection scheme. And have never been detected since. Our builds were unique enough to disperse the detection to only affect partially to begin with, but then they found a pattern in the fact the module connected to an online api, which left the string "hexui.com" in .net clr's memory string interning table, which was shared across all modules. This has been fixed and we have made builds even more unique, honestly our code-rewritter is so cool I'll probably release it on GitHub someday. Anyhow most here will prolly say we have never been detected since few were around back then. Truly though cheats doesn't really get detected nowadays anymore, Valve's sig-based detection era ended 3-5 years ago. When cheat's get detected nowadays it's because they have features which are very volatile security wise and then Valve patch and detect based on that. For the most part they rely on VACNET, old VAC was completely disabled last year around August and we have yet to see it make a come back. |
||
|
05-May-26, 02:36
|
||
|
||
| Thank you for the incredibly thorough answer. Seeing an owner take the time to address historical detections with such technical clarity is a huge green flag. It definitely clarifies the 'undetected' timeline for me and makes me much more comfortable giving the software a shot after all this time. Looking forward to seeing that code-rewriter on GitHub someday! | ||
|
05-May-26, 10:45
|
||
|
||
|
You're welcome. I actually just went through our ban report section (yes we have that for full transparency, ranging all the way back to 2015) So we were detected partially beginning of December 2016, and then fully January 2017. So 8-years and 4-months ago to be exact |
||
|
09-May-26, 03:41
|
||
|
||
(05-May-26 10:45)Menalix Wrote: You're welcome. This type of behavior is the difference between wannabes and real software developers. 
|
||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)