Skip to content

Backstabs#404

Merged
AdamTadeusz merged 5 commits intoNeotokyoRebuild:masterfrom
AdamTadeusz:053_knifeBackstabs
Jun 29, 2024
Merged

Backstabs#404
AdamTadeusz merged 5 commits intoNeotokyoRebuild:masterfrom
AdamTadeusz:053_knifeBackstabs

Conversation

@AdamTadeusz
Copy link
Copy Markdown
Contributor

Description

Toolchain

  • Windows MSVC VS2022

Linked Issues

@AdamTadeusz AdamTadeusz requested a review from a team June 27, 2024 16:09
@AdamTadeusz AdamTadeusz marked this pull request as draft June 27, 2024 16:24
@AdamTadeusz AdamTadeusz marked this pull request as ready for review June 27, 2024 16:54
Rainyan
Rainyan previously approved these changes Jun 28, 2024
@AdamTadeusz
Copy link
Copy Markdown
Contributor Author

@Rainyan do you think the compiler is smart enough to reduce (100 * (1 / NEO_SUPPORT_DAMAGE_MODIFIER)) + 1) to a single value or should that be another constexpr too?

@Rainyan
Copy link
Copy Markdown
Collaborator

Rainyan commented Jun 28, 2024

@Rainyan do you think the compiler is smart enough to reduce (100 * (1 / NEO_SUPPORT_DAMAGE_MODIFIER)) + 1) to a single value or should that be another constexpr too?

Almost certainly the compiler will calculate that at compile time. But doesn't hurt to constexpr it if we can.

@AdamTadeusz
Copy link
Copy Markdown
Contributor Author

@Rainyan do you think the compiler is smart enough to reduce (100 * (1 / NEO_SUPPORT_DAMAGE_MODIFIER)) + 1) to a single value or should that be another constexpr too?

Almost certainly the compiler will calculate that at compile time. But doesn't hurt to constexpr it if we can.

Also it would be easier to understand what thats there for, magic numbers and all that

@Rainyan
Copy link
Copy Markdown
Collaborator

Rainyan commented Jun 28, 2024

@Rainyan do you think the compiler is smart enough to reduce (100 * (1 / NEO_SUPPORT_DAMAGE_MODIFIER)) + 1) to a single value or should that be another constexpr too?

Almost certainly the compiler will calculate that at compile time. But doesn't hurt to constexpr it if we can.

Also it would be easier to understand what thats there for, magic numbers and all that

Yeah, feel free to refactor it if you want.

Rainyan
Rainyan previously approved these changes Jun 28, 2024
@AdamTadeusz
Copy link
Copy Markdown
Contributor Author

I tested again after refactoring, and at 36.87 degrees the bots sometimes die and sometimes not. Im guessing this testing methodology isn't ideal (running setang 0 90 0 multiple times with a different starting orientation each time results in different calculated attack angles, differences in the hundredths of a degree) so Ill just blame it on that and leave it as is

@Rainyan Rainyan requested a review from a team June 28, 2024 13:25
@AdamTadeusz AdamTadeusz merged commit 5fbbbf5 into NeotokyoRebuild:master Jun 29, 2024
Rainyan pushed a commit that referenced this pull request Jul 1, 2024
* all classes die to one backstab, Bodies aren't sent flying due to knife kills

* Increased backstab angle to 36.86 degrees max

* merge master into branch, change backstab max angle to asin(0.6)

* damageToOneShotsupport as a contexpression
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.

Backstabbing with knifes leads to one hit kill

3 participants