Tremulous Forum

Community => Servers => Topic started by: Pete on January 06, 2008, 09:47:40 am

Title: Info files
Post by: Pete on January 06, 2008, 09:47:40 am
I've tried Googling and searching but haven't found any answer to this.

How do I make a info file? I mean, for use through !info.
I guess it should be called 'info', but what extension, and where should it be placed?

My server is on Linux, FYI.
Title: Re: Info files
Post by: Caveman on January 06, 2008, 01:37:50 pm
What is !info?
maybe contact the author of that server-side patch, or read the source?
Title: Re: Info files
Post by: benmachine on January 06, 2008, 02:11:47 pm
!info is mine, and poorly documented I'll admit.
In your base folder, create a new folder called info.
Create a new text file in that folder called info-default.txt, this will get printed when someone uses !info with no arguments.
You can also create other files, like info-rules.txt or info-maps.txt, which will be printed when someone does !info rules or !info maps, for example.
There's other neat stuff you can do, but it's kinda complicated so I won't get into it here. If/when I finish writing my docs, I'll edit in a link.
Title: Re: Info files
Post by: Pete on January 06, 2008, 06:56:56 pm
!info is mine, and poorly documented I'll admit.
In your base folder, create a new folder called info.
Create a new text file in that folder called info-default.txt, this will get printed when someone uses !info with no arguments.
You can also create other files, like info-rules.txt or info-maps.txt, which will be printed when someone does !info rules or !info maps, for example.
There's other neat stuff you can do, but it's kinda complicated so I won't get into it here. If/when I finish writing my docs, I'll edit in a link.

Ok, thanks  :)
Title: Re: Info files
Post by: master@sparta on January 08, 2008, 01:25:26 am
thanks ben i have been trying to figure that out for ever nice too know
Title: Re: Info files
Post by: jake on November 16, 2008, 04:14:03 pm
i am currently trying to create an info file, however it has glitched and the only way to see !info is to use rcon :(

doing !info without rcon nothing happens at all.
Title: Re: Info files
Post by: David on November 16, 2008, 09:00:00 pm
Do the people trying have whatever admin flag it needs?
Title: Re: Info files
Post by: cactusfrog on November 17, 2008, 05:37:09 am
thanks ben i have been trying to figure that out for ever nice too know
same thanks
Title: Re: Info files
Post by: jake on November 17, 2008, 08:15:09 am
It turns out that you can only have a very very small .txt file. anything bigger than maybe 100 words doesnt work, anyone know how to make bigger ones work?
Title: Re: Info files
Post by: mooseberry on November 18, 2008, 06:43:49 am
Summarize?
Title: Re: Info files
Post by: Thorn on November 18, 2008, 09:48:35 pm
I remember someone saying it was limited to 1024 charactors ( or some number around there )...
Title: Re: Info files
Post by: gimhael on November 19, 2008, 12:11:50 pm
The code in G_admin_info truncates the message at 1023 bytes and then sends a print "message" to the client. I wouldn't increase this limit as this could have all sorts of nasty side effects, but it should be possible to split a longer message into 1023 character chunks and send multiple print commands.

Title: Re: Info files
Post by: David on November 19, 2008, 02:02:11 pm
However how is the client going to read it?  The people who need !info are probably the same group who don't get how to scroll the console etc.  Or maybe don't even know there is a console...

Do it in pages.
Title: Re: Info files
Post by: Caveman on November 22, 2008, 11:00:38 pm
Why not just blast those poor guys/girls with !tellplayer <url> until they get your point?
Title: Re: Info files
Post by: benmachine on December 01, 2008, 04:04:17 pm
The limit is intentional to make handling the data easier.

src/qcommon/q_shared.h:
Code: [Select]
// the game guarantees that no string from the network will ever
// exceed MAX_STRING_CHARS
#define MAX_STRING_CHARS        1024    // max length of a string passed to Cmd_TokenizeString