#(daxz_) block plugin messages
22 messages · Page 1 of 1 (latest)
(daxz_) block plugin messages
Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
!e player receives message
Player
Using this will forcibly sync the chat thread.
player receives message
when a player receives any chat message from the server. This does not normally include *player* chat, instead prefer !event player chats for that.
Always. - this adds switches flagged:<flag name> + permission:<node>, in addition to the <player> link.
<context.message> returns an ElementTag of the message.
<context.raw_json> returns an ElementTag of the raw JSON used for the message.
<context.system_message> returns true if the message is a system message (not player chat).
"MESSAGE:<ElementTag>" to change the message.
"RAW_JSON:<ElementTag>" to change the JSON used for the message.
True - this adds <context.cancelled> and determines cancelled + cancelled:false.
Thread closed as resolved.
nope doesnt work
Thread was manually reopened by @leaden hatch.
on player receives message:
- ratelimit <player> 1s
- narrate <context.message>
ive got this
it doenst trigger when its the minehut message
is apparently a proxy message
^ it's not impossible to skip plugin's packet interception, and wouldn't be surprised if they are doing that
hmm what if i refresh the chat everytime a player runs /hub
resend everything in their chat
except for the message
And either way, as much as I don't think it's the best platform, not sure if trying to remove the messages they specifically added in to their system is the best thing to do - might even be in their TOS or something
Also assuming this is a proxy command as well, you can't listen to it without a proxy plugin
nono uh im writing my own /hub command
w denizen
i think they just listen for /hub because it doesnt do anything without anything