I'm diverting this from another thread where tempers were running a bit high. There's a concern that a careless server host (or remote admin) might leak someone else's IP unintentionally, rather than only maliciously.

I did some cursory research into other multiplayer games where people host their own servers instead of using the publisher's server. From what I can tell--and I don't play any of these games, so forgive me if I make a mistake here--Minecraft doesn't show client IPs by default, but does save them in a log file, and some plugins may add equivalents to the /IP command. Counter-Strike: Global Offensive shows all IPs by default in a console, but this may be disabled using the cl_hideserverip setting, similar to JJ2+'s /streaming. Several other games allow kicking and banning by IP, but it's not clear to me how you're supposed to find the IP in the first place. Because a lot of games are run through Steam or PSN or whatever, they often have built-in (bannable) unique identifiers for players besides IP addresses, so in those cases it's not useful information to have.

A couple of the poll options are mutually exclusive, but everyone do your best~!

It looks like there's a lot of disagreement right now, does anyone want to defend their position in words and try to convince anyone else?

Hello! I'd like to share some thoughts! I pretty much understand the concern, that the IP leak can compromise the players! After all it happened during the NT! Which was long ago, but it was the only NT in which I participated. Anyway... As a host, it feels pretty handy to see IPs. It's more convenient in case of adding IPs by the command into admin (/addadminip) This command would be kinda useless if you wouldn't be able to see the IP right away. There's the argument that you can use iplog. For me that is pretty annoying - for some reason it feels like the Jazz Jackrabbit 2 just decides almost randomly to which IP log it is gonna write. It can be iplog001, iplog002, etc. Being able to see the IP right away is much more handy. For the admin thing, it may be more handy to have somekind of command which ... makes a targeted player an Admin right away. (Similiar to how Minecraft has a /op command) But still ... in the old days, I was checking IPs to see if there are some ... bad players who may compromise the server. For me personally the IPs are handy to see. But I have also opposite concern. I don't like that the player list has a Host IP shown. It may serve a similiar threat. You are on a server, take a screenshot of the playerlist, and there is the host IP visible. You may send it to some public server ... and someone uses that IP to DDOS the server. In case of host, it would be probably good to hide the IPs into a command. Like it is for clients. But it would be cool if there is a command to add admins by the other way than a IP. I still think it is important to see the IPs, but it's true that they do not need to be shown all the time. Or there could be some shortcut - hotkey, which makes the IPs visible, which may make it harder to screenshot the IPs by accident. (Something like [Tab] which shows playerlist but other key.) Shared my thoughts... thanks! Have a nice day!

For 6.6c, I've made the following two changes:

The /kick and /ban commands no longer show the IP address of the kicked/banned player to remote admins who aren't allowed to use the /ip command.

This one was clear, everyone agreed this made sense.

Split the old /streaming option into new /showpasswordsandips and /modulemusiconly options, both disabled by default. As a result, unlike before, all passwords and IP addresses are now hidden/censored inside the game window. You must opt in to seeing them, by enabling this setting after opening the game.

There wasn't a consensus here, but "The visual effects of /streaming should be enabled by default" seemed like it covered all the IP visibility concerns, so now you have to opt in to seeing client IPs as the server (what was being discussed in the poll) and to seeing the server IP as a client (Clank's concern, although obviously server IPs are public information no matter what you choose), as well as all the chat stuff that was also getting hidden by /streaming.

In fact, let's go into detail, since apparently not everyone knew about /streaming to begin with.

These are now hidden by default, unless you enable /showpasswordsandips. (Previously they were shown by default unless you disabled /streaming.)

• Client and server IPs in the player list
• All IPs received through chat, particularly the /ip and /kick and /ban commands, except for links
• The /getadminpass command
• Passwords in the /login, /password, and /setadminpass commands
• Passwords while joining or configuring a server in the main menu system
• Admin chat

The option name "Show Passwords and IPs" feels awfully wordy (and doesn't even cover admin chat!) but I couldn't come up with anything better that would still be clear. There's the "Personally Identifiable Information" acronym, PII, but I doubt it's widely known.

Meanwhile, mp3 and ogg files are still loaded by default, unless you enable /modulemusiconly. (Previously they were loaded unless you disabled /streaming.)

Originally Posted by Violet CLM

[url=https://docs.jj2.plus/#lc040326]
The option name "Show Passwords and IPs" feels awfully wordy (and doesn't even cover admin chat!) but I couldn't come up with anything better that would still be clear. There's the "Personally Identifiable Information" acronym, PII, but I doubt it's widely known.

I think in this case it is only good that it is wordy, since the aim was to make it as difficult as possible for clients and servers to accidentally display ANY IPs to the world via various medias. I think it works splendidly here.

EDIT: Oh right, this was about the menu option, not the command itself. But either way I suppose it is good that they're named similarly in order to stay consistent.