Update Operand enum values, RegistryOp method #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added possible remaining
Operandenum values and cases toRegistryOpmethodbased on functions at addresses
00bc1130,00bc1020,00bc0770,00eb2030.They seem to be used in most of aptitude commands having
regopfields e.g.TargetByHealth,InflictCooldown,HealDamage,TargetFilterByRange,RequireEnergy,MovementTether,MovementSlide, allRegisterLoadFromtypes of commands etc.I'm not sure about
ForcePush,AddPhysics,ConsumeSuperCharge.Most of command instances use regops 0, 1 or 2 and meaning of these
remains unchanged - assignment, addition, multiplication.
Gist file that shows count of each regop value, for all
clientandbothenv commandsis available at https://gist.github.com/SzymonKaminski/e9989bed76ba1dad6c2ede6c09736098.