Avenger Posted December 12, 2017 Share Posted December 12, 2017 The amount/restriction type field (param2) has the order wrong. The high word (3rd and 4th bytes) affect the restriction type (0, 1, 2) The low word (1st and 2nd bytes) affect the number of usable slots (3 is the maximum by the way, as there are 3 resource fields in eff v2.0). Example in spwi908, which has no restriction (chain contingency) : 00a2h Parameter 2 00000003 That is a WRITE_LONG 3 or WRITE_BYTE 3, so low word, first byte, whatever we call it Also a typo in the 0 type: Contingeny Quote Link to comment
lynx Posted December 12, 2017 Share Posted December 12, 2017 Yep, thanks. Updated. Quote Link to comment
Recommended Posts
Join the conversation
You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.