Skip to content
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

Adding addon items from the Poltergeist Outfit #3847

Merged
merged 3 commits into from
Dec 15, 2021
Merged

Adding addon items from the Poltergeist Outfit #3847

merged 3 commits into from
Dec 15, 2021

Conversation

omarcopires
Copy link
Contributor

Pull Request Prelude

Changes Proposed

Adding possibility to get new outfits
It is necessary to add the #3810

@omarcopires omarcopires changed the title Adding Poltergeist Outfits Adding addon items from the Poltergeist Outfit Dec 15, 2021
@omarcopires omarcopires marked this pull request as ready for review December 15, 2021 19:53
EPuncker
EPuncker previously approved these changes Dec 15, 2021
@EPuncker EPuncker merged commit 21e5bf6 into otland:master Dec 15, 2021
@omarcopires omarcopires deleted the new-outfits branch December 17, 2021 00:47
Znote added a commit to Znote/forgottenserver that referenced this pull request Dec 18, 2021
Followup on otland#3847

* Simplified the code and added comments
* Each conditional operation is unique (etc: does not perform the same checks twice in the code)
* * Such as `player:isPremium()` and `player:hasOutfit(looktype)`
* More granulated feedback (instead of saying 1 of 3 things stopped you from using this item)
* Error messages are sent using CancelMessage instead of MESSAGE_EVENT_ADVANCE
* * Maybe it would be appropriate to also add CONST_ME_POFF effect?
* `useItem` renamed to `outfitConfig` to make it less misleading, since the variable represents a config table, not the used item.
@Znote Znote mentioned this pull request Dec 18, 2021
3 tasks
EPuncker pushed a commit that referenced this pull request Dec 18, 2021
Followup on #3847

* Simplified the code and added comments
* Each conditional operation is unique (etc: does not perform the same checks twice in the code)
* * Such as `player:isPremium()` and `player:hasOutfit(looktype)`
* More granulated feedback (instead of saying 1 of 3 things stopped you from using this item)
* Error messages are sent using CancelMessage instead of MESSAGE_EVENT_ADVANCE
* * Maybe it would be appropriate to also add CONST_ME_POFF effect?
* `useItem` renamed to `outfitConfig` to make it less misleading, since the variable represents a config table, not the used item.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants