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.

Sign up for GitHub

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

Jump to bottom

Standing on the "heavy_core" can cause false alarms and prevent movement. #1622

Closed
CatBang opened this issue Jul 29, 2024 · 8 comments
Closed

Standing on the "heavy_core" can cause false alarms and prevent movement. #1622

CatBang opened this issue Jul 29, 2024 · 8 comments
Labels
false positive False positive

Comments

@CatBang
Copy link
Contributor

CatBang commented Jul 29, 2024

Describe the false positive and how to replicate it

Standing on the "heavy_core" can cause false alarms and prevent movement.

Grim version

grimac2.3.66
https://github.com/GrimAnticheat/Grim/actions/runs/10062651758
https://github.com/GrimAnticheat/Grim/actions/runs/10011478006

Server version

This server is running Paper version 1.21-119-master@100d75a (2024-07-29T16:00:13Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21-111-66165f7 (MC: 1.21)

Plugins

Only Grimac
@CatBang CatBang added the false positive False positive label Jul 29, 2024
@Anthony01M
Copy link
Contributor

Please confirm if it still falses on this too: #1587

@CatBang
Copy link
Contributor Author

CatBang commented Jul 29, 2024

Please confirm if it still falses on this too: #1587

The second link above includes the latest build version of attribute-rework, which still has false positives.

@Anthony01M
Copy link
Contributor

Please confirm if it still falses on this too: #1587

The second link above includes the latest build version of attribute-rework, which still has false positives.

Ah yes, my bad, I more or less missed the branch name.
You might get asked for Client Version & a video on how to reproduce (which is basically standing so don't think you need that part) just the client would be enough ig since you didn't mention it anywhere

@SamB440
Copy link
Collaborator

SamB440 commented Jul 29, 2024

Try the latest commit

@CatBang
Copy link
Contributor Author

CatBang commented Jul 29, 2024

Please confirm if it still falses on this too: #1587

The second link above includes the latest build version of attribute-rework, which still has false positives.

Ah yes, my bad, I more or less missed the branch name. You might get asked for Client Version & a video on how to reproduce (which is basically standing so don't think you need that part) just the client would be enough ig since you didn't mention it anywhere

Yes, just standing on it can reproduce the false alarm, Vanilla client.

@CatBang
Copy link
Contributor Author

CatBang commented Jul 29, 2024

Try the latest commit

There are still false positives.
6cde87cf-e142-4b7b-afe8-b6516671506d
https://github.com/GrimAnticheat/Grim/actions/runs/10151981829

@SamB440
Copy link
Collaborator

SamB440 commented Jul 30, 2024

Try again

@CatBang
Copy link
Contributor Author

CatBang commented Jul 30, 2024

Try again

https://github.com/GrimAnticheat/Grim/actions/runs/10161478590
The latest build version has resolved this issue after testing, can you sync the submission to 'attribute-rework'?

@SamB440 SamB440 closed this as completed Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
false positive False positive
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@SamB440 @Anthony01M @CatBang