![]() For example: "if GetSpellAbilityId() = 'A000' then", at the time you look at the binary expression you don't know yet what type its operands are, only that the binary expression itself should return boolean (because the operator type is "="). This happens when you decompile the operands of a binary expression. ![]() Looking at the type is not really needed either since the data can be obtained from triggerdata.txt: if the type can be a preset then its key will exist in one of the dictionaries I use to model triggerdata.txt, if it can be a variable it will have the 'UsableAsGlobalVariable' flag, etc.Īnother issue with looking at the type is sometimes you don't know what type it should be. That way instead of looking at the type (of which there are over a hundred) I only look at the expression type (only like 16 types here). ![]() ![]() Decided to refactor the expression->triggerfunctionparameter decompilation. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |