-
Notifications
You must be signed in to change notification settings - Fork 21
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
Comments
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 |
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%} ? |
Using a placeholder such as So using However, using As for the second issue, in-game, the placeholder 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! |
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.
The text was updated successfully, but these errors were encountered: