TwisteAC is now BaobabAC
TwisteAC is now BaobabAC. Same team, same engine, same panel, same servers: existing customers have nothing to do.
If you are looking for TwisteAC, you are in the right place: the RedM anticheat you know under that name is now called BaobabAC. This is not an acquisition, not a rewrite, and not a new product sold on the ashes of the old one. It is the same software, the same team, the same codebase, and the same production server that has been running since the first customer.
What does not change
Everything, in practice. A rename that breaks something on a customer server is not a rename, it is a migration - and nobody should have to redo their configuration because a logo moved.
- detection engine
- identical, no rule removed
- panel
- same address, same accounts
- server key
- unchanged
- in-game resource
- no reinstall required
- billing
- same subscription, same price
Why this name
"Twiste" came from the team that wrote the first prototype. It was an author's name: it told a newcomer nothing about the product. A server owner comparing three anticheats should not have to guess what yours does from your handle.
A baobab stands for centuries, shelters whatever settles underneath it, and most of its mass is underground. That is roughly the job description: stay in place for years, protect a community you did not build, and do the work in a part of the system nobody looks at. We will stop there - an anticheat is judged on its detections, not on its tree.
The old name stays mentioned everywhere it is useful, including in the site metadata, so that the continuity is readable by a search engine and by a customer alike. BaobabAC, formerly TwisteAC: that is the exact wording, and it will stay on display as long as it helps somebody.
What actually moved in the product, recently
The real work of the last few months is not the name. It is the evidence. Detecting a cheat is not enough: facing a player who disputes it in front of his community, a line in a log file carries no weight. The Black Box answers that: when a detection fires, the telemetry window preceding the incident is frozen and uploaded, and you replay the scene on a 2D map with a timeline.
The buffer the server keeps in memory covers seconds of movement, part of it from BEFORE the alert: you see the cause, not only the consequence. The exact duration and the sampling rate are not published.
Withheld/Detection thresholds are never published: a value that is known is a value a cheat is tuned just underneath.
Two tracks are drawn side by side: what the game client declared, and what the server observed. The gap between them is measured in metres, and that gap is the evidence - not an opaque score. The file is hashed and shareable by link, with no account needed, so the discussion can end on facts.
If you arrived here from a "TwisteAC" search and would rather judge on evidence than on a name, the demo panel is open read-only on real data, the pricing is public, the anticheat RedM overview is the same product under the new name, and how a RedM anticheat works is explained in detail, limits included.