The trigger bot doesn't work when the target is far away

[johnnygodsa]

The current trigger bot seems to be using InCross for tracking, which causes it to malfunction at long distances, such as between CT and T on Dust2. Is there a good way to improve this?

[github-actions[bot]]

Thanks for using our software! We will look into and fix your issue asap.

[Chuck1488]

Another constant problem is the visible mod. When it’s enabled, the cheat only reacts to a target that’s peeking out from behind a wall, and it won’t shoot when the enemy is fully behind cover. But it works much worse compared to when the visible mod is disabled.

There’s also an issue with pistols, or more specifically with single-shot weapons. It’s especially noticeable with the Desert Eagle — hitting a headshot, even from close range, is almost impossible. And if you try to shoot with it by aiming at the hitbox (for example, with the Deagle), the crosshair shakes all over the model, but very rarely actually lands on the head

[estdae]

To fix the trigger, you can use bones, but that's not very accurate, which will cause the trigger to shoot at the walls, which I think is worse than not shooting at all.. a good way to use hitboxes

it seems quite obvious that with the visible check enabled ‘it won't shoot when the enemy is fully behind cover.’ In general, using spottedbymask is very slow. It's worth using ray cast, but I don't have time to dig into ida pro to get the map geo, and using vpk files is rather ridiculous

the main problem is time.