Comitems player_chat event doesn't work properly with cancel-action
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the command item using the PLAYER_CHAT event with cancel-action enabled, including the console /say case described in the report. Trace the PLAYER_CHAT handling and verify that the player's original message is suppressed while the intended command output still appears; confirm behavior against linked Discord chat as well.
Written by the indexing model from the issue text.
Description
Versions
CraftBook version: 3.10.2-SNAPSHOT;4616-21180b0
Bukkit version: git-Spigot-a99063f-fad2494
Describe the bug
When using a command item with the PLAYER_CHAT event and cancel-action turned on, the message sent my the player is still visible in chat, though it is blocked from other plugins.
When using an comitem to send a /say @m command through the console, both the console message and player message are visible despite cancel-action being set to true.
The player message does not show up on my Discord server's linked Minecraft chat however, as intended
To Reproduce
- Create a command item with the PLAYER_CHAT event and cancel-action set to true
- Type something in chat, and notice how the players message is still sent
Expected behavior
Creating a console /say microphone for fun, and expect the chat message sent by the player to be blocked from sending by the cancel-action flag
Screenshots
- Dominant language
- Java
- Stars
- 321
- Forks
- 165
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EngineHub/CraftBook
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
status:pending type:bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
status:pending type:bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
status:pending type:bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
status:accepted type:feature-request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in EngineHub/CraftBook
Similar issues
-
[Bug] AI unread message badge counts a batch of new bubbles as one messagePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
apache/rocketmq-dashboard#5784 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
PCL-Community/PCL-CE#3658 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
apache/skywalking#14127 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Team/Identity Server Core Type/Improvement U2
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
wso2/product-is#28553 ·
Maintainers usually reply within 1 day