/setserverpass and spaces

Question about this, if I just type "/setserverpass " leaving a space right at the end, will the server recognize that command as (a) no password entered, thus open server for all or (b) me changing to the password to be a literal space that people still have to input, as in " "?

[raptor]

If there are just spaces after it, then it is considered 'clear password'

[sam686]

might be a bug: /setserverpass " " isn't setting the password and only clears... But if you go to host menu and put a space in the password, that works for setting a password to just a space.

Another bug: fails to save passwords to bitfighter.ini that have just spaces and nothing else.

[watusimoto]

might be a bug: /setserverpass " " isn't setting the password and only clears... But if you go to host menu and put a space in the password, that works for setting a password to just a space.

Another bug: fails to save passwords to bitfighter.ini that have just spaces and nothing else.

I don't have the source in front of me, but I think we trim the passwords to avoid spurious spaces. From the sound of it, we do it inconsistently, and maybe we shouldn't do it all.

If you really think this is a bug, please either fix it, or put a bug report in so it doesn't get forgotten.

[raptor]

I don't think this is an issue - there are plenty of keys to choose from other than spaces for a password. Spaces are used for tokenization of commands and the effort to fix this is probably not worth for such an edge case.

[watusimoto]

There does at the very least seem to be some inconsistent behavior that should be corrected, even if the overall design is the one we want to stick with.

Putting my two sense in.

1. it should be consistant bolth ways.

2. I have needed to use a space before though rare.