"&l" at the end of a prefix display player's name "&f&l" (white and bold)
Izanaagii opened this issue · 1 comments
Bug Report
Type /ver NametagEdit and post the output.
[12:24:18 INFO]: NametagEdit version 4.5.16
[12:24:18 INFO]: Authors: sgtcaze, Cory, Lorenzo0111 and Aurelien30000
What version of Bukkit/Spigot/PaperSpigot are you using? Type /ver
[12:24:34 INFO]: Checking version, please wait...
[12:24:34 INFO]: Current: git-Purpur-1972 (MC: 1.19.4)*
Previous: git-Purpur-1952 (MC: 1.19.4)
- You are 4 version(s) behind
Download the new version at: https://purpurmc.org/downloads
What plugins are you using? Type /plugins
plugins
[12:24:53 INFO]: Bukkit Plugins: (65):
[12:24:53 INFO]: - AdvancedBan, AdvancedPortals, ajLeaderboards, AltDetector, AnimatedScoreboard, AntiPopup, AutoSmelt, AzLink, BankPlus, BetterRTP
[12:24:53 INFO]: BossShopPro, ChatManager, ChunkSpawnerLimiter, Citizens, CommandCooldown, ConditionalTextPlaceholders, CoreProtect, CrazyAuctions, DecentHolograms, Essentials
[12:24:53 INFO]: ExcellentCrates, FastAsyncWorldEdit, GriefPrevention, HeadBlocks, HeadDatabase, IllegalStack, Images, InventorySaver, LuckPerms, Maintenance
[12:24:53 INFO]: *MoneyWithoutDecimals, Multiverse-Core, NametagEdit, nAntiBot, NexEngine, nLogin, PlaceholderAPI, PlayerPoints, *PlayTime, PlugManX
[12:24:53 INFO]: ProtocolLib, PvPManager, *ServerListPlus, SetSpawn, SimpleRename, *SimpleTpa, SkinsRestorer, SkQuery, Skript, *skript-placeholders
[12:24:53 INFO]: spark, SpawnerMeta, SuperVanish, TabCompleteFilter, TabList, Vault, ViaBackwards, ViaVersion, VillagerTradeLimiter, *VirtualTag
[12:24:53 INFO]: VoidGen, VotingPlugin, WildStacker, WorldGuard, zVoteParty
Please explain your issue. How do you trigger it?
Once I put "&l" at the end of a prefix in configuration (group or players), it display the player name bold and white :
But once I get rid of "&l" code in my configurations files, my name display perfectly like in the configuration
Are there any errors in the console? Please use: https://pastebin.com
Absolutely not
I think it's a direct bug from NTE, and have to patch it
thanks <3
hey did u fix it? bc i have the same error