OT giving red trust factor

Fappyboi

Member
I just bought a brand new account 3 days ago and today it got red tf, in those 3 days i've played legit(semi 2 or 3 games but the other team was also cheating) and did not get reported i've been using ot for almost a year and have never faced this issue before until recently. Also how can i inform then owners and developers so maybe they can fix these issues.
 
ot isn't affecting the account either so i dont see the problem?
Are you sure bro? Its not like i am talking only about one account , i am talking of 2 and one of them i made was like 3 days back. I am pretty sure its cheat issue. I used nixware few months back and it also gave red tf.
 
Are you sure bro? Its not like i am talking only about one account , i am talking of 2 and one of them i made was like 3 days back. I am pretty sure its cheat issue. I used nixware few months back and it also gave red tf.
it's the way you are playing if you are being reported too much u will have a red trust factor
 
Are you sure bro? Its not like i am talking only about one account , i am talking of 2 and one of them i made was like 3 days back. I am pretty sure its cheat issue. I used nixware few months back and it also gave red tf.
it means you dont know how to play legit, and you got lot reports
 
OT gives your account red trust that's not a news mate. It started from July this year. Just look up for tip in the forum, there are many of them reporting this issue and the developer never made any progress to solve this isssue.
 
no cheat can ruin the trust factor of an account, only the amount of reports you get. if your semiraging / raging in mm or playing blatent in casual or deathmatch, then that could also be why
 
Believe me OT is giving RED TRUST. Played with new csgo account with only walling turn on and get red trust immediately after one match.

Using Neverlose and sk for 3 month and my account is still green till now.
 
A cheat itself doesn't cause you to get a red trust factor, only the way you play with it
If you are not an active member stop comment like this. OT used to be good before June this year. After that, giving red trust for every game you injected. Obviously VAC had some internal detection on it but just not confirmed, otherwise will be VACed. More interestingly, VAC sometimes revoke the red trust given by OT (may think this was a false detection), and will give you red trust back after like 2 days. I checked with multiple account played only with OT and the trust factor is in most time red but sometimes suddenly turning green and turning red after 2 days, provided that no match played and have not injected OT on these accout recently. This is more than clear that OT had made its detection in VAC but just not been confirmed. This kind of red trust cannot be alleviated by purchasing and funding your account. Better to pray for VAC make OT detection false.
 
Last edited:
If you are not an active member stop comment like this. OT used to be good before June this year. After that, giving red trust for every game you injected. Obviously VAC had some internal detection on it but just not confirmed, otherwise will be VACed. More interestingly, VAC sometimes remoke the red trust given by OT (may think this was a false detection), and will give you red trust back after like 2 days. I checked with multiple account played only with OT and the trust factor is in most time red but sometimes suddenly turning green and turning red after 2 days, provided that no match played and have not injected OT on these accout recently. This is more than clear that OT had made its detection in VAC but just not been confirmed. This kind of red trust cannot be alleviated by purchasing and funding your account. Better to pray for VAC make OT detection false.
 
Semi-raging (or even fully raging) in no way causes your account to be automatically placed in red trust.
The loader, however, seems to be causing this, if you inject with -insecure in loader parameter (which allows you to inject while in-game), your account won't be flagged by VACnet and won't decrease your trust factor. This might have to do with the VAC bypass which onetap is using (restarting Steam as admin to inject the bypass), I've seen this happen on some public bypasses before, while it didn't happen with other bypasses, so to avoid this, just add "-insecure" parameter in your loader and wait for llama to update the loader with a better bypass
 
If you are not an active member stop comment like this. OT used to be good before June this year. After that, giving red trust for every game you injected. Obviously VAC had some internal detection on it but just not confirmed, otherwise will be VACed. More interestingly, VAC sometimes revoke the red trust given by OT (may think this was a false detection), and will give you red trust back after like 2 days. I checked with multiple account played only with OT and the trust factor is in most time red but sometimes suddenly turning green and turning red after 2 days, provided that no match played and have not injected OT on these accout recently. This is more than clear that OT had made its detection in VAC but just not been confirmed. This kind of red trust cannot be alleviated by purchasing and funding your account. Better to pray for VAC make OT detection false.
lol no
I used it after June this year and was playing legit with it a lot as well, not using any exploits and was always fine, seems like cfg issue to me
if OT was VAC detected you would get banned, no reason for them to just give you a red TF if it's already detected
whatev tho idc lol
 
Semi-raging (or even fully raging) in no way causes your account to be automatically placed in red trust.
The loader, however, seems to be causing this, if you inject with -insecure in loader parameter (which allows you to inject while in-game), your account won't be flagged by VACnet and won't decrease your trust factor. This might have to do with the VAC bypass which onetap is using (restarting Steam as admin to inject the bypass), I've seen this happen on some public bypasses before, while it didn't happen with other bypasses, so to avoid this, just add "-insecure" parameter in your loader and wait for llama to update the loader with a better bypass
that could actually be the case but hasn't been like that for a long time afaik
you could just use your own vac bypass as well
 
Back
Top