I'd like to be able to set up a MOTD over more that one line, at lesat one that would wrap if the line got too long..

Just insert \n wherever you want to have a linebreak...

in 1.5 too? Cool.. Me and tZork were cursing about that when setting up the charging testservers

Why not \r\n btw?

If it does work its in 1.5.x

In 1.5 it does not, just prints out the \n

tChr wrote:Why not \r\n btw?

Because \r\n is only for stupid OSes, that can't stick to existing standards [/rant]

tZork wrote:If it does work its in 1.5.x

In 1.5 it does not, just prints out the \n

d'oh! You're right, it doesn't work... (neither in 1.5 nor SVN)
I was quite certain that it would work

KadaverJack wrote:

tChr wrote:Why not \r\n btw?

Because \r\n is only for stupid OSes, that can't stick to existing standards [/rant]

I hate to be the one to tell you this, but this is one of the very few places windows does it by standards, and Unix does not Standard internet newline (even pre-unix) is crlf, wich also makes much more sense, as cr should take you to the beginning of the line and lf should take you one down, nothing more

For an interesting anecdote read the jargon files intry about Unix brain-damage http://www.catb.org/jargon/html/U/Unix-brain-damage.html

Sorry KJ, but he's right...

"the nice thing about standards is that there are so many to choose from"

ISO C99 for example defines \n another way:

5.2.2 Character display semantics

...

2. Alphabetic escape sequences representing nongraphic characters in the execution character set are intended to produce actions on display devices as follows:

• ...
• \n (new line) Moves the active position to the initial position of the next line.
• \r (carriage return) Moves the active position to the initial position of the current line.
• ...

And yes, if you are on Windows and C and write "foo\n" to a file opened in "text mode", it will output the bytes 0x0D and 0x0A (CR and LF). If you, OTOH, output "\r\n" on Windows, you will actually write CR CR LF.

Now talk about \r\n being right. \n is _always_ the line delimiter - but when writing to a file, \n could expand to more than one byte. Only PHP kiddies[tm] think \r\n is the right way to end a line... in "proper" code, it's either \n and opening the file in text mode, or \x0D\x0A and opening the file in binary mode.

Disclaimer: when using POSIX output functions like write(), binary mode is assumed. So Darkplaces is doing it right

KadaverJack wrote:d'oh! You're right, it doesn't work... (neither in 1.5 nor SVN)
I was quite certain that it would work

I think its because \n inside a string is special in (Q)C.. if you just set the variable sv_motd to "foo\nbar" the \n is just normal text. I suppose we have to split the string in QC..

esteel wrote:

KadaverJack wrote:d'oh! You're right, it doesn't work... (neither in 1.5 nor SVN)
I was quite certain that it would work

I think its because \n inside a string is special in (Q)C.. if you just set the variable sv_motd to "foo\nbar" the \n is just normal text. I suppose we have to split the string in QC..

Or make auto-wrapping.. or is that hard?

tChr wrote:Or make auto-wrapping.. or is that hard?

String operations in qc are really nasty, but that linewrap thing shouldn't be too hard...
But someone has to count how many chars will fit in one line and if there will fit the same amount of chars for every resolution first. (i think the answer to the second question is yes, but i'm not certain of that...)