-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
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
Add tableId to getItemEntry #3064
Add tableId to getItemEntry #3064
Conversation
So if I understand these changes correctly, with the new tableId, the normal GET_ITEM macro uses the modIndex, but the new macro allows setting both separately? Otherwise the functionality is all the same? |
ce7ebf8
to
fde5c3d
Compare
fde5c3d
to
c9ad725
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left a comment with an idea to possibly make it easier to read the GET_ITEM_CUSTOM_TABLE
usages, not sure if it would make things overall better or worse though
c9ad725
to
1273abd
Compare
So I guess whether we merge this would depend on whether we wanted to maintain the rando item table or not going forward. |
The rando item table is staying (at least I think?), it's the weird "in between" table that is the issue, it's stored in the randomzier table but has a vanilla mod ID |
e134c12
to
24be50e
Compare
24be50e
to
2b88620
Compare
2b88620
to
87165b1
Compare
I don't love it, but these comments explain why:
My use case is I need to serialize a getItemEntry and send it across the wire, and sending over the getItemID + modIndex does not suffice because the modIndex is not 1:1 with the table the entry is stored in.
Build Artifacts