We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ReGameDLL_CS/regamedll/dlls/weapons.h
Line 436 in a94c7bd
bool m_bDirection;
BOOL m_bDirection;
Line 421 in a94c7bd
bool m_bFireOnEmpty;
Line 420 in a94c7bd
bool m_bPlayEmptySound;
ReGameDLL_CS/regamedll/dlls/training_gamerules.h
Lines 85 to 86 in a94c7bd
bool m_bSmokeTouching;
bool m_bFlashTouched;
ReGameDLL_CS/regamedll/dlls/training_gamerules.cpp
Line 324 in a94c7bd
bool m_bSmokeTouchingLastFrame
The text was updated successfully, but these errors were encountered:
No branches or pull requests
ReGameDLL_CS/regamedll/dlls/weapons.h
Line 436 in a94c7bd
does it make sense to switch from BOOL to bool? and using
bool m_bDirection;
ORBOOL m_bDirection;
?ReGameDLL_CS/regamedll/dlls/weapons.h
Line 421 in a94c7bd
It is only used to define true and false. Using
bool m_bFireOnEmpty;
ReGameDLL_CS/regamedll/dlls/weapons.h
Line 420 in a94c7bd
in general, there are no errors here, then we use only 1 and 0. It would be clearer if it were bool. Using
bool m_bPlayEmptySound;
ReGameDLL_CS/regamedll/dlls/training_gamerules.h
Lines 85 to 86 in a94c7bd
bool m_bSmokeTouching;
andbool m_bFlashTouched;
ReGameDLL_CS/regamedll/dlls/training_gamerules.cpp
Line 324 in a94c7bd
bool m_bSmokeTouchingLastFrame
The text was updated successfully, but these errors were encountered: