-
Notifications
You must be signed in to change notification settings - Fork 1
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
AGIP135: add batch equip functions for wearables and wearable configs #3
base: master
Are you sure you want to change the base?
Conversation
…arables and upgrade script for ItemsFacet
|
||
// if the sender is not the owner and the gotchi has been bridged | ||
// then they need to pay a fee to the owner | ||
if (sender != owner) { |
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.
It seems like it's possible for someone other than the owner to update an existing config ID, is that the intended behavior? @pgendreau
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.
It's so it can be delegated but I see how this could be used maliciously when updating someone else configuration without a proper permission system. We could remove it for update and leave it for createWearablesConfig as it is not as problematic
No description provided.