Closed Zarkness closed 4 weeks ago
Hi, it's a problem with ItsMyMeta which doesn't parse the Placeholders inside rather than ItsMyConfig
Hi, it's a problem with ItsMyMeta which doesn't parse the Placeholders inside rather than ItsMyConfig
@itsme-to if it was itsmymeta thing would happen the same in any other plugin where I put a placeholder of itsmymeta, but only happens to me with the prefix of itsmyconfig, besides I'm testing by editing the code I added support for parse placeholders that are between %% and then if I parse it, so it is not itsmymeta thing
if it were a itsmymeta thing then the tab would give me the same as with the itsmyconfig prefix and instead as you see in the penultimate image it parses it.
@itsme-to any news about this bug?
Hello, that not really a bug and ItsMyMeta that need improuvement, we removed the default placeholder format for optimisation and because it's create error with some plugin
@itsme-to I added this line of code to test, it still does not support placeholders other than those with the
final String parsedPlaceholder = PlaceholderAPI.setPlaceholders(player, '%' + papiPlaceholder + '%');
// Reparse the placeholder until no more placeholders are found
String previousParsed;
do {
previousParsed = parsedPlaceholder;
parsedPlaceholder = PlaceholderAPI.setPlaceholders(player, previousParsed);
} while (!previousParsed.equals(parsedPlaceholder));
ItsMyConfig supports nested placeholders; you just need to follow ItsMyConfig's format and not use %%. Additionally, it's the job of ItsMyMeta to return the actual value instead of placeholders, so each plugin doesn't have to adapt to it.
ItsMyConfig handles this quite well and normally never returns placeholders.
It should also support nested placeholders with the legacy format since I am not going to create 2 different placeholders for the same result when those lines of code already solve that problem.
You are free to use your own fork, we will normally redev ItsMyMeta soon anyway
Ok and a question about itsmymeta and its new dev, will it continue to have the teams section?
Yes
Describe the bug. when you use the prefix and use and the placeholder returns another placeholder it does not match the placeholder for the second time.
Replay Steps to reproduce the behavior:
Expected behavior as many times as necessary until the final result is returned. Screenshots** the expected result should be hello > but it comes out %itsmymeta_testing_placeholder2% >, instead when I use that placeholder in the tab for example it returns hello > instead if the value of the second placeholder instead of being %% is with if it parses it and I don't want to have 50 placeholders for the same thing but to use each one in a different side.
Software (complete the following information): Spigot: [e.g., Paper