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

Implemented damage sum #46

Merged
merged 1 commit into from
Mar 21, 2023
Merged

Implemented damage sum #46

merged 1 commit into from
Mar 21, 2023

Conversation

em92
Copy link
Contributor

@em92 em92 commented Jan 29, 2023

Included readme with note.

Example: https://www.youtube.com/watch?v=rCPH63uQCKQ

@@ -3313,3 +3313,16 @@ void CG_ClearFxExternalForces (void)
}
}
#endif


void CG_HideDamagePlums (int client, int weapon) {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Is CG_HideDamagePlums() just used to hide self damage? Why not just avoid adding them at all?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is CG_HideDamagePlums() just used to hide self damage?

No. It used for different case. For example we have 3 plasma hits. Without using CG_HideDamagePlums() and enabled damage sum hack it will show 3 damage plums. 20, 40 and 60. When all these damage plums are shown, it is hardly readable how many damage dealt.

When usin CG_HideDamagePlums, on second hit it will show damage plum with "40" and hide previous damage plum "20". On third hit it will show damage plum "60" and hide previous damage plum "40".

@brugal
Copy link
Owner

brugal commented Mar 21, 2023

thank you!

@brugal brugal merged commit 89b5d4b into brugal:master Mar 21, 2023
@em92 em92 deleted the damage-sum-hack branch March 21, 2023 17:05
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