11.6.2 [item]/[i] not parsing correctly with Gradient plugin

[therealaqz]

Are you using MySQL?

No

Are you using a proxy?

No

"/version ChatControlRed" - plugin version

11.6.2

Optional: Error log

No response

ZIP of "/chc debug"

Sent to email

Steps to reproduce

Hi there. I am having an issue with ChatControl.

I'm experiencing integration issues between GradientPlus and ChatControl Pro, and I'm hoping you can help clarify the best approach.

The Issues

Issue 1: ChatControl Variables Not Working with Gradient Placeholders

I'm trying to use ChatControl's Parse_Variables: true feature (which allows players to use [item] or [i] to display items in chat), but it's conflicting with GradientPlus.

My ChatControl format:

yamlcandygod:
  Message: "%katsu_avatar_SMALL% &8{tag}{player_prefix} <gradient:#FFA6F7:#FFCFFB><bold>%gradientdisplayname%</bold></gradient> &8»&r %gradientchat%"
  Parse_Variables: true

The problem: When I use %gradientchat%, ChatControl's [item] variable doesn't work - it just shows the literal text [item] instead of displaying the held item.

What I've tried:

1. Using %gradient_{message}% instead - this shows {message} literally
2. Using %gradient_message% instead - same issue or doesn't apply gradient
3. Adding [item] and [i] to GradientPlus's ignored_words list - doesn't help

My question: What is the correct placeholder syntax to use in ChatControl formats that will:

1. Allow ChatControl to parse [item] variables first
2. Then apply GradientPlus gradients to the message
3. Still respect the player's selected gradient color from /gradient

[devpedrobarbosa]

Hey @therealaqz

Currently we don't support Gradient+.

I can't even test because it's a premium resource.

What I can say for now is: we do parse custom message variables created with ChatControl in our {message} placeholder.

Since you've completely removed it in favor of %gradientchat%, we can no longer guarantee that ChatControl's functionalities will keep working.

You can try changing listener priorities, but I doubt this is going to work (https://docs.mineacademy.org/chatcontrol/listener-priorities.html#understanding-bukkit-priorities).

By the way, just so you know: we do natively support gradient colors everywhere.

Thanks for reaching out.

[therealaqz]

Hey @therealaqz

Currently we don't support Gradient+.

I can't even test because it's a premium resource.

What I can say for now is: we do parse custom message variables created with ChatControl in our {message} placeholder.

Since you've completely removed it in favor of %gradientchat%, we can no longer guarantee that ChatControl's functionalities will keep working.

You can try changing listener priorities, but I doubt this is going to work (https://docs.mineacademy.org/chatcontrol/listener-priorities.html#understanding-bukkit-priorities).

By the way, just so you know: we do natively support gradient colors everywhere.

Thanks for reaching out.

Hi there. If I can send you the resource, would you be able to look into testing it?

[kangarko]

@therealaqz unfortunately not a priority right now because we already have a [item] placeholder plus support configurable event priority to interact with other plugins.

[therealaqz]

@therealaqz unfortunately not a priority right now because we already have a [item] placeholder plus support configurable event priority to interact with other plugins.

Is that a option that is configurable in ChatControl settings already or is it hard coded?

[devpedrobarbosa]

@therealaqz

What do you mean? The [item] variable is configurable (ChatControl/variables/item.yml). You can even create new variables.

The event listener priority is also configurable under settings.yml.

If you need any further help, feel free to reach out. Thanks.

[kangarko]

We already support changing event priorities so that if a plugin wants to alter chat they can do so before us. The problem is that many plugins use their own way to do that which is incompatible with the common chat event we listen to. For years that event didn't support interactive chat. So if changing our priorities won't fix it then unfortunately it's incompatible.