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

Version:11.0.3 Nested Placeholder Issue #2925

Open
Hazbo56 opened this issue Dec 22, 2024 · 3 comments
Open

Version:11.0.3 Nested Placeholder Issue #2925

Hazbo56 opened this issue Dec 22, 2024 · 3 comments

Comments

@Hazbo56
Copy link

Hazbo56 commented Dec 22, 2024

Are you using MySQL?

Yes

Are you using a proxy?

Yes - Velocity

"/version ChatControlRed" - plugin version

11.0.3

Optional: Error log

No response

ZIP of "/chc debug"

debug.zip

Steps to reproduce

Due to the migration to the use of {} syntax for placeholders, it's caused nested placeholders to now not work as intended, as the nested placeholder within another uses the {} syntax already. If there would be an easy resolution to this, that would be greatly appreciated, or if there is a current way that I just don't know to change the formatting to work as intended with PAPI expansions such as ParseOther and ChangeOutput.

@Hazbo56
Copy link
Author

Hazbo56 commented Dec 23, 2024

With parsing variables enabled, it still causes issue when trying to use a Receiver Condition that checks the receiver is in the same Land as the sender '"{lands_land_name_plain}" == "{parseother_{sender_name}_{lands_land_name_plain}}"', there's no error and I don't believe that any formatting is wrong

@kangarko
Copy link
Owner

Can you try using this syntax: {parseother_%some_other_variable%} because as far I checked we should only parse the {} variable but leave the %% to be parsed by PlaceholderAPI, or I am misunderstanding something here?

Regarding the other issue can you try {parseother_%sender_name%_%lands_land_name_plain%} ?

@Hazbo56
Copy link
Author

Hazbo56 commented Dec 23, 2024

Using a placeholder such as {changeoutput_contains_input:{eternaltags_active}_matcher:true_ifmatch:{eternaltags_tag}_else:&8None Active} - which would otherwise be written %changeoutput_contains_input:{eternaltags_active}_matcher:true_ifmatch:{eternaltags_tag}_else:&8None Active% - works fine and as expected.

So using '"{parseother_%sender_name%_%lands_land_name_plain%}" == "{lands_land_name_plain}"' which is checking to make sure the sender is part of land Boop, for the receiver to get the message, it throws this: https://pastebin.com/0WkkkeHw

However, using '"{parseother_{sender_name}_{lands_land_name_plain}}" == "{lands_land_name_plain}"' doesn't throw any errors and allows the message part to be sent but the receiver doesn't receive it, though they should, (to check for my own idiocy) %lands_lands_name_plain% returns "Boop", %parseother_{alt_hhazbo}_{lands_land_name_plain}% returns "Boop", so to me, it should be returning true and letting me see the message part.

As for the second issue, in-game, the placeholder %parseother_{player_name}_{player_name}% returns my player name in-game via papi parse, but putting it into say a hover message of a CC format, it throws: https://pastebin.com/AvK3CgUc

Of course, enjoy your holidays, though if there's any further information I can provide, do let me know, I appreciate your response with trying to help me figure out where I'm going wrong!

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

No branches or pull requests

2 participants