You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Versions:
Server Version: 3243-Spigot-6c1c1b2-d3cc412 (MC: 1.17.1)
Skript Version: 2.6-beta3
Installed Skript Addons:
skript-yaml v1.4.1
Of course, in this case, I has registered a uncolored string with &, so it can be said that it is the my fault in some way. But in this situation, uncolored string(with &) should not be converted to colored(with §), because it was registered as a uncolored string.
Receiving the command argument as colored can solve this problem. so I rewritten my scripts with colored command arguments. Now it seems to be working fine.
I couldn't find exactly where in my script was causing the problem because of #35, but now I think I finally found it. Thank you for your help. :D
The text was updated successfully, but these errors were encountered:
qsef1256
changed the title
Color conversion for string can cause yaml path conflict
Always convert strings containing & to §
Oct 8, 2021
Description:
Code:
Reproduce:
/yaml addparty &atest
/yaml addplayer
Expecting Result:
Player's uuid will be added to yaml list "data.&atest.chat", not "data.§atest.chat".
Result:
Versions:
Server Version: 3243-Spigot-6c1c1b2-d3cc412 (MC: 1.17.1)
Skript Version: 2.6-beta3
Installed Skript Addons:
skript-yaml v1.4.1
Of course, in this case, I has registered a uncolored string with &, so it can be said that it is the my fault in some way. But in this situation, uncolored string(with &) should not be converted to colored(with §), because it was registered as a uncolored string.
Receiving the command argument as colored can solve this problem. so I rewritten my scripts with colored command arguments. Now it seems to be working fine.
I couldn't find exactly where in my script was causing the problem because of #35, but now I think I finally found it. Thank you for your help. :D
The text was updated successfully, but these errors were encountered: