Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
setClientDvars
is to be preferred oversetClientDvar
when there is the need to set more than one client dvar. The reason is that only one server command is sent instead of multiples. That may cause issues, especially when other game scripts are causing other server commands to be sent. In short, the fewer server commands are sent the better.getDvarInt
is to be preferred overint( getDvar() )
. The reason is thatgetDvarInt
already fully supports casting variables to the desired type internally. The secondint()
is redundant. Additionally, the IW variant ofgetDvarInt
supports a default value that is returned in case the dvar was not registered or other errors were to arise when callinggetDvarInt
. This can't be done with a regulargetDvar
.getTime()
always returns an integer type andself.lastAttackTime
is always assigned an integer type therefore the casting to int before subtraction is redundant as well.