Skip to content

Fixed issue regarding stylist ui behavior and restrictions.#3379

Open
MrKeiKun wants to merge 1 commit into
HerculesWS:masterfrom
MrKeiKun:fix-2102-stylist-ui
Open

Fixed issue regarding stylist ui behavior and restrictions.#3379
MrKeiKun wants to merge 1 commit into
HerculesWS:masterfrom
MrKeiKun:fix-2102-stylist-ui

Conversation

@MrKeiKun

Copy link
Copy Markdown
Contributor

Pull Request Prelude

Changes Proposed

Players are properly restricted from movement and item usage when the stylist UI is active.

Issues addressed: #2102

@hemagx hemagx left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall the PR is fine, the commit message however isn't please explain the change of restriction in the commit message, be verbose i need to understand what happened just from reading the commit message not just the code.

@hemagx hemagx added this to the Release v2026.05 milestone May 24, 2026
…t restrictions

Unlike all other interactive UI panels (Refine, Lapine, Grade, Reform, Enchant),
the Stylist UI had no server-side open/close flag, meaning its close handler was
a stub that did nothing, style-change packets were never guarded against being
processed without the UI open, player movement was not blocked while using it,
and it was absent from all pc_cant_act macros. This adds a stylist_ui flag to
map_session_data.state (set on open, cleared on close), guards both style-change
packet handlers to reject requests when the UI is not open server-side, blocks
movement in unit_can_move, adds stylist_ui to all pc_cant_act macros, and
introduces pc_cant_act_except_stylist to match the pattern of the other UIs.

Signed-off-by: Lorenzo Buitizon <the.keikun@gmail.com>
@MrKeiKun MrKeiKun force-pushed the fix-2102-stylist-ui branch from b9ac7fb to 74f1c25 Compare June 7, 2026 06:04
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.

3 participants