Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixer sleep(t/2) triggerbot #72

Merged
merged 1 commit into from
Aug 23, 2024
Merged

Conversation

LauraSavall
Copy link
Contributor

trigger_cooldown Logic:

The trigger_cooldown function is returning an int that is a casted result from a floating-point calculation. This calculation might not behave as intended. Specifically: ((rand() % 50) / 100) will always result in 0 because integer division in C++ discards any fractional part. Hence, this expression will always return 0. As a result, your trigger_cooldown function always returns 0.15, which after casting to int, becomes 0. This will affect your sleep and click timing, making it nearly instantaneous.

added a //printf("Cooldown: %d ms\n", t); // Correct printf syntax for int to debug and it's true... old version return 0ms EACH time

trigger_cooldown Logic:

The trigger_cooldown function is returning an int that is a casted result from a floating-point calculation. This calculation might not behave as intended. Specifically: ((rand() % 50) / 100) will always result in 0 because integer division in C++ discards any fractional part.
Hence, this expression will always return 0. As a result, your trigger_cooldown function always returns 0.15, which after casting to int, becomes 0. This will affect your sleep and click timing, making it nearly instantaneous.

added a //printf("Cooldown: %d ms\n", t); // Correct printf syntax for int
to debug and it's true... old version return 0ms EACH time
@LauraSavall
Copy link
Contributor Author

Hm, just saw a weird bug where AFTER the triggerbot delay, Dexterion keep AIMBot to work, so if you triggersomeone, you watch around right after...slowly approach to the enemy and zam your player will "force aim" to enemy... which is quite flagged on replay/spectator
Will dig into it

@wqq-z
Copy link
Contributor

wqq-z commented Aug 23, 2024

Hmm, seems right, but I'm not approving or merging this request right now. I'm busy these weeks. Also, we're thinking of re-coding all of Dexterion with Vulkan graphics support for faster rendering. Additionally an new GUI might be created. All featured that was mentioned will be only applied to Kernel-Dexterion, However usermode will be updated too based in kernel-mode using normal read.mem.

@wqq-z
Copy link
Contributor

wqq-z commented Aug 23, 2024

Well nvm mergin this.

@wqq-z wqq-z merged commit b590252 into Nocture-Insight:master Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants