q3ded

[Dan]

Archived from groups: alt.games.quake3 (More info?)

I've just installed q3ded on a redhat8 linux box. When I run it - it says
what's below, then waits. If I load up quake3 on a win2k box on the same
lan, then I can't see my dedicated server. Any ideas what this might be?

Cheers,
Dan




[root@quakeserv quake3]# ./q3ded +exec test.cfg
Q3 1.32b linux-i386 Nov 14 2002
----- FS_Startup -----
Current search path:
/root/.q3a/baseq3
/usr/local/games/quake3/baseq3/pak8.pk3 (9 files)
/usr/local/games/quake3/baseq3/pak7.pk3 (4 files)
/usr/local/games/quake3/baseq3/pak6.pk3 (64 files)
/usr/local/games/quake3/baseq3/pak5.pk3 (7 files)
/usr/local/games/quake3/baseq3/pak4.pk3 (272 files)
/usr/local/games/quake3/baseq3/pak3.pk3 (4 files)
/usr/local/games/quake3/baseq3/pak2.pk3 (148 files)
/usr/local/games/quake3/baseq3/pak1.pk3 (7 files)
/usr/local/games/quake3/baseq3/pak0.pk3 (3539 files)
/usr/local/games/quake3/baseq3
../q3ded/baseq3

----------------------
4054 files in pk3 files
execing default.cfg
execing q3config.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok
--- Common Initialization Complete ---
Opening IP socket: localhost:27960
Hostname: quakeserv
IP: 127.0.0.1
Started tty console (use +set ttycon 0 to disable)
^3PunkBuster Server: PunkBuster Server (v0.993 | A0 C0.0) **DISABLED**
execing test.cfg
sv_maxclients will be changed upon restarting.
g_gametype will be changed upon restarting.
Hitch warning: 968 msec frame time

 

[Guest]

Archived from groups: alt.games.quake3 (More info?)

Dan wrote:

> I've just installed q3ded on a redhat8 linux box. When I run it - it says
> what's below, then waits. If I load up quake3 on a win2k box on the same
> lan, then I can't see my dedicated server. Any ideas what this might be?
>
> Cheers,
> Dan
>
>
> [root@quakeserv quake3]# ./q3ded +exec test.cfg

[snip]

Can you tell us what is in the file "test.cfg"? I suspect that you're not
actually telling the server to run a map. If you don't specify a map, then
how does it know what to do? (hence why it appears to just sit there
and wait)

As a test, put the following line at the bottom of your test.cfg file:

map q3dm17

... then reload the Quake 3 server and see if you can see it on the Windows
2000 client.

Also, make sure that the client is showing ALL types of games. Thus, for
instance, if you have set up a CTF game but are listing only Free For All,
it won't /list/ any servers, even though it might say "1 of 1 Arena
Servers".

Hope this helps,

Stephen.

 

[Dan]

Archived from groups: alt.games.quake3 (More info?)

"Stephen Smith" <null@void.pointer> wrote in message
news:O8kdc.28457$h44.4003203@stones.force9.net...
> Dan wrote:
>
> > I've just installed q3ded on a redhat8 linux box. When I run it - it
says
> > what's below, then waits. If I load up quake3 on a win2k box on the
same
> > lan, then I can't see my dedicated server. Any ideas what this might
be?
> >
> > Cheers,
> > Dan
> >
> >
> > [root@quakeserv quake3]# ./q3ded +exec test.cfg
>
> [snip]
>
> Can you tell us what is in the file "test.cfg"? I suspect that you're not
> actually telling the server to run a map. If you don't specify a map, then
> how does it know what to do? (hence why it appears to just sit there
> and wait)
>
> As a test, put the following line at the bottom of your test.cfg file:
>
> map q3dm17
>
> .. then reload the Quake 3 server and see if you can see it on the Windows
> 2000 client.
>
> Also, make sure that the client is showing ALL types of games. Thus, for
> instance, if you have set up a CTF game but are listing only Free For All,
> it won't /list/ any servers, even though it might say "1 of 1 Arena
> Servers".
>
> Hope this helps,
>
> Stephen.





I copied the config from section 5.3 of this webpage:
http://www.tldp.org/HOWTO/Game-Server-HOWTO/quake3.html

What are the m1, m2, m3, etc values? Will this be calling the map command?
I'm actually away from the linux box until Tuesday now, as it's at work - so
I can't test it out. The gametype is set to show all on my client.

Thanks,
Dan.

 

[Guest]

Archived from groups: alt.games.quake3 (More info?)

Dan wrote:

> I copied the config from section 5.3 of this webpage:
> http://www.tldp.org/HOWTO/Game-Server-HOWTO/quake3.html
>
> What are the m1, m2, m3, etc values? Will this be calling the map
> command?
> I'm actually away from the linux box until Tuesday now, as it's at work -
> so I can't test it out. The gametype is set to show all on my client.

Ahhh, Dan, I see the problem.

To make it all work as expected, simply include the following line at the
bottom of your copied-n-pasted test.cfg

vstr m1

If you look at section 5.4, [Q3CTF (Capture The Flag)] you will see in that
small config they include 'vstr m1' at the very end, (that is the thing
which kicks the server into action, more on this shortly) so I presume it
was a small (albeit critical!) omission in 5.3 Configuring.

Add that line to your config, restart server, and you should be up and
running!

Now, regarding m1, m2 and m3, etc. In answer to your question, no, they do
not actually /start/ the map, per-se.

(copied n pasted from section 5.3)

set m1 "map q3dm1; set nextmap vstr m2"
set m2 "map q3dm2; set nextmap vstr m3"
set m3 "map q3dm3; set nextmap vstr m4"
..
..
set m25 "map q3tourney6; set nextmap vstr m1"

The 'set' command works like:

set [variable name] [data]

Thus, set m1 "map q3dm1; set nextmap vstr m2" assigns the text string:

map q3dm1; set nextmap vstr m2

.... to a variable called 'm1'

The same goes for the lines that set m2, m3 ... m25.

Study the lines in your config; you'll see that the 'nextmap' variable is
assigned to the /next/ mX variable, i.e.

m1 has a nextmap vstr m2
m2 has a nextmap vstr m3
m3 has a nextmap vstr m4

right up to..

m25 has a nextmap vstr m1

Clearly, m25 is assigned back to our start, (m1) therefore completing the
map cycle.

So, what does Quake actually do then when it reads your config? All it is
doing at the moment is simply assigning those text strings to those
variables, nothing more. One final push is required to make it work. This is
(in this case) the vstr command.

vstr tells Quake to actually /interpret/ and /process/ a variable's
contents, as if you had typed the contents directly into Quake's console
window, as a command - hence, why the "vstr m1" line is important at the end
of your config.

Anyway, going back to your test.cfg file. When Quake reads that line, (vstr
m1, the currently all-important missing line) it expands the contents of m1,
which are:

map q3dm1; set nextmap vstr m2

It then executes the command:

map q3dm1

That kicks the server into action, starting the map.

It then assigns the the text:

vstr m2

.... to a variable called 'nextmap'.

'nextmap' gets to be interpreted/processed when the level
timelimit/fraglimit comes to an end, and as m2 contains:

map q3dm2; set nextmap vstr m3

Which Quake executes as:

map q3dm2 -- i.e. change level

set nextmap vstr m3 -- reconfigures 'nextmap' to be vstr m3

So, the next time the level finishes, the contents of m3 will be
interpreted/processed. Wash, rinse, repeat.

This procedure repeats itself, and as the m25 variable refers back to m1,
the whole cycle starts again just like the initial vstr m1 command started.

I hope that has cleared it up, sorry if it has too much waffle in it! ;-)

Stephen.

 

[Guest]

Archived from groups: alt.games.quake3 (More info?)

"Stephen Smith" <null@void.pointer> wrote in message
news:xhydc.28582$h44.4032733@stones.force9.net...
> Dan wrote:
>
> > I copied the config from section 5.3 of this webpage:
> > http://www.tldp.org/HOWTO/Game-Server-HOWTO/quake3.html
> >
> > What are the m1, m2, m3, etc values? Will this be calling the map
> > command?
> > I'm actually away from the linux box until Tuesday now, as it's at
work -
> > so I can't test it out. The gametype is set to show all on my client.
>
> Ahhh, Dan, I see the problem.
>
> To make it all work as expected, simply include the following line at the
> bottom of your copied-n-pasted test.cfg
>
> vstr m1
>
> If you look at section 5.4, [Q3CTF (Capture The Flag)] you will see in
that
> small config they include 'vstr m1' at the very end, (that is the thing
> which kicks the server into action, more on this shortly) so I presume it
> was a small (albeit critical!) omission in 5.3 Configuring.
>
> Add that line to your config, restart server, and you should be up and
> running!
>
> Now, regarding m1, m2 and m3, etc. In answer to your question, no, they do
> not actually /start/ the map, per-se.
>
> (copied n pasted from section 5.3)
>
> set m1 "map q3dm1; set nextmap vstr m2"
> set m2 "map q3dm2; set nextmap vstr m3"
> set m3 "map q3dm3; set nextmap vstr m4"
> .
> .
> set m25 "map q3tourney6; set nextmap vstr m1"
>
> The 'set' command works like:
>
> set [variable name] [data]
>
> Thus, set m1 "map q3dm1; set nextmap vstr m2" assigns the text string:
>
> map q3dm1; set nextmap vstr m2
>
> ... to a variable called 'm1'
>
> The same goes for the lines that set m2, m3 ... m25.
>
> Study the lines in your config; you'll see that the 'nextmap' variable is
> assigned to the /next/ mX variable, i.e.
>
> m1 has a nextmap vstr m2
> m2 has a nextmap vstr m3
> m3 has a nextmap vstr m4
>
> right up to..
>
> m25 has a nextmap vstr m1
>
> Clearly, m25 is assigned back to our start, (m1) therefore completing the
> map cycle.
>
> So, what does Quake actually do then when it reads your config? All it is
> doing at the moment is simply assigning those text strings to those
> variables, nothing more. One final push is required to make it work. This
is
> (in this case) the vstr command.
>
> vstr tells Quake to actually /interpret/ and /process/ a variable's
> contents, as if you had typed the contents directly into Quake's console
> window, as a command - hence, why the "vstr m1" line is important at the
end
> of your config.
>
> Anyway, going back to your test.cfg file. When Quake reads that line,
(vstr
> m1, the currently all-important missing line) it expands the contents of
m1,
> which are:
>
> map q3dm1; set nextmap vstr m2
>
> It then executes the command:
>
> map q3dm1
>
> That kicks the server into action, starting the map.
>
> It then assigns the the text:
>
> vstr m2
>
> ... to a variable called 'nextmap'.
>
> 'nextmap' gets to be interpreted/processed when the level
> timelimit/fraglimit comes to an end, and as m2 contains:
>
> map q3dm2; set nextmap vstr m3
>
> Which Quake executes as:
>
> map q3dm2 -- i.e. change level
>
> set nextmap vstr m3 -- reconfigures 'nextmap' to be vstr m3
>
> So, the next time the level finishes, the contents of m3 will be
> interpreted/processed. Wash, rinse, repeat.
>
> This procedure repeats itself, and as the m25 variable refers back to m1,
> the whole cycle starts again just like the initial vstr m1 command
started.
>
> I hope that has cleared it up, sorry if it has too much waffle in it! ;-)
>
> Stephen.
>


Wow - that was a long post! ) I'll give it a go on Tuesday when I got
back into work. I wanna go and play with it now! ) But being 200 miles
away from work at the mo would make it kinda difficult |

Thanks a lot for your help, it's greatly appreciated.

Regards,
Dan.