So, after following those steps, you will notice this results: One of them will need to have OP so that way you can "Spy" the messages sent by the other account when it is out of the chat-radius. And after you do, you will need to join the server with two differrent accounts for obviously reasons. There are a lot more reasons about this, but I won't be splashing much more on this, as it's not the topic. On the "format:" you must change it from " " and here it comes the big question, "Why would you change the displayname variable with player_name?" Well, first of all, remember this is the fastest way to reproduce the bug, but on my detailed server I use it for avoiding players who used to be Vip group with their nickname changed, to show their realname whenever their Vip group would expire, or also to obligate players with staff groups inherited, to always show their real name, even if before becoming staff they had a custom nickname defined.You must enable the radius chat, changing it from 0 to any number higher than it (in my case: 100 blocks). Then, the only thing you need to change on the config.yml of Essentials is on the EssentialsChat section.
After having the 6 plugins downloaded, you must download Player expansion for PlaceHolderAPI with /papi ecloud download Player.You will need the following 6 plugins (Vault, EssentialsX, EssentialsXChat, ChatInyector and its dependencies: PlaceHolderAPI and ProtocolLib) *Forget about LuckPerms, I used it for letting "Test" shout a message to demostrate you that the format is already fixed.The first thing I have to noticed, is that the bug doesn't actually comes entirely from Essentials, and now I'm confused about considering this a bug or not, maybe it is likely more a conflict problem that was actually fixed by Essentials, but not fully fixed (you will understand it after reading the How to reproduce the bug) Today I have been 2 entire hours making a deep investigation on this bug on a new empty server, and I figure it out a lot of things. Sorry for bringing poor information about the bug, I was a little busy.
0 kommentar(er)
