1.16.5 § Character gets messed up when generating a new config

Why not just store them using a '&' and then translate the color codes?

 

This

Code (Text):

ChatColor.translateAlternateColorCodes('&', "&b&lCool Message here with fancy Colours");

 

That is basically how to use it, yea. It just takes any string you have and returns a new string that replaces the given char with section signs(§)

 

If you wana color code the lore of the item, I recomend you look into Streams (Specifically Mapping)

 

Just create a method like this:

Code (Java):

private String formatColors(String arg) {
    return ChatColor.translateAlternateColorCodes('&', arg);
}

private List<String> formatColors(List<String> arg) {
    ArrayList<String> preList = new ArrayList<>();
    arg.stream().forEach(s -> preList.add(formatColors(s)));
    return preList;
}
 

P.S. Written without IDE, may have made a mistake in creating a stream.
P.P.S. Use formatColors(Arrays.asList(.....)) for your lore.

 

Why do that when you could...

Code (Java):

private String formatColors(String arg) {
    return ChatColor.translateAlternateColorCodes('&', arg);
}

private List<String> formatColors(List<String> arg) {
    return arg.stream().map(string -> formatColors(string)).collect(Collectors.toList());
}
 

 

like I said look insto streams, its alot cleaner.

can be shortened to

Code (Java):

arg.stream().map(this::formatColors).collect(Collectors.toList());

 

You two are right, but the point is the same: use ChatColor and a method

 

true, I was just pointing out a cleaner way of doing stuff

 

You only have to set encoding to UTF-8. Using ChatColor's method isn't a bad idea but you can avoid it and it's easier to just change the encoding.

 

no its not, using the § character is super bad practice, not to mention its harder on users since that character isnt even on the keyboard.