Adding the GameCam Proxy

Topics regarding running or playing on D-Day servers.
Post Reply
User avatar
[IRS] Aeon6911
Posts: 21
Joined: Sat Jun 08, 2013 7:53 pm

Adding the GameCam Proxy

Post by [IRS] Aeon6911 » Sat Jun 08, 2013 8:03 pm

Features

Introduction

GameCam is a plug-in mod, or, to be more accurate, an API-proxy mod. GameCam adds a client camera (spectator mode) to any other Quake II mod. This is done by literally adding external code to an existing mod, without having to know or modify its source code.
GameCam contains only the code for the camera, which makes it a very small download (~90KB, including the manual...). Note that GameCam is a server-side mod, so clients don't have to download or install anything.

Camera Modes

GameCam provides three camera modes:
ACTION - based on q2cam by Paul Jordan. This is the default camera mode in which the camera tracks the areas where most of the players are. This usually means that it tracks the areas where most of the action takes place. Fixed camera positions may also be defined, so that specific locations usually get filmed from the same point of view.
CHASE - this is a very much enhanced version of the original id software CTF chase camera. The GameCam CHASE camera swivels around the player being chased to provide the best view of his/her closest opponent. Spectators also have the option to manually adjust the camera position themselves.
FREE - aka noclip: spectators move freely around the map, and can pass through walls, etc. This mode is usually disabled, and is mostly used for defining fixed cameras to be used with the ACTION camera.
The GameCam ACTION camera can be configured to focus on specific types of players, based on a priority list. This allows it to track CTF flag carriers, HeadHunters with the most heads, Quad berserkers, etc.
User Interface

The default settings of GameCam make it replace the in-game spectator mode. This means that players can become spectators by simply typing spectator 1 (or spectator <password>), and return to the game with spectator 0. This way players don't have to figure out any special camera commands.
While in spectator mode, players can access the camera menu. The menu allows spectators to switch camera modes, modify the camera options, get help about the camera keyboard binds, and return to the game.

The menu provides access to the most useful features of GameCam - other features can be accessed via the camera console command.

Automatic Demo Recording

With this feature turned on, GameCam makes the client record a demo of the game using a unique file name. The recording will be stopped upon changing levels and restarted with a different (unique) file name.
The demo file name format is as follows: mapname-DDMMYY-HHMM.dm2, where mapname is the current map (e.g. q2dm1), and the rest is the date and time (at the server!) when the recording started. This format makes it easy to sort the demos by map and date/time.

This feature is available to all players even if they're not spectators! - just type camera demo and start playing...

General Admission Mode

GameCam makes it easy to run and manage tournaments while playing mods that have not been specifically designed with tournaments in mind. In General Admission mode all players start as spectators, and only a limited number of players are allowed to enter the game. The rest just sit back and enjoy the show ...
If a time-limit is set then the timer will start as soon as the first player exits spectator mode.

To switch players during the match (why?), one of the players must step down (become a spectator, or disconnect), and one of the spectators can then join the game.

Everyone will return to be spectators upon changing levels.

Ticker Tape

This unique feature puts a scrolling line of animated text at the bottom of the screen in ACTION and FREE modes. The contents of the tape and the way it scrolls (right, left, blink, etc.) can be configured using a simple scripting language.
The text itself may include special characters, highlighted (green) text and escape sequences to print any console variable (e.g. hostname), the time and date in various formats and a simple running high-scores update.

The script is re-loaded upon level changes, and/or from within the script itself using the reload script directive. This feature allows automatic updating of the ticker script using an external utility.

Other Features

GameCam provides other features as well:
spectators do not appear on the scoreboard (but can be listed with the players console command),
the HUD is removed in FREE and ACTION modes,
player identification can be toggled,
the player's inventory can be inspected in CHASE mode (!)
Performance

GameCam actually reduces the load on the server, since spectators do not generate network traffic for other players. A game with 32 players is a lot more demanding than a match with 4 players and 28 spectators (which is a lot more demanding than a match with 4 players and no spectators ...)
Security Measures

GameCam provides features specifically designed to prevent lamers from cheating:
camera mode can be protected with a password, so that only authorized players may become spectators,
the number of spectators can be limited,
spectators return to the game as new clients,
spectators suicide as soon as they return to the game (may be disabled),
CHASE mode can be disabled, so that it is not abused,
spectators' chat messages can be disabled, so that they don't interfere with an on-going match, or try to tip off players (they can still chat with one another using say_team),
standard (v3.20) flood protection on spectator chat messages,
spectators' names are changed from name to [CAMERA]name, so that it remains clear who's playing and who's just watching.
Note that spectators can't improve their ranking on services like CLQ by chasing high ranking players, because their names show up as [CAMERA]name when queried by GameSpy, QStat etc. Furthermore, mods with any logging facilities treat spectators as if they disconnected from the game.
ZBot detection is provided (on Win32 systems) via a separate plug-in module - ZKick, which can be used with GameCam or independently. ZKick is available on the download page.

GameCam can also be used together with the BW-Admin and Q2Admin server administration plugins (both on Win32 and Unix servers).


table of contents

Installation

Windows 95/98/NT

Simple: create a folder named release under C:\Quake2 (replace C: with the correct drive letter), and extract the contents of the distribution package (zip) to C:\Quake2\release\. The package contains two files: gamecam.html - the manual, and gamex86.dll - the binary.
Unix

(the instructions are for Linux, a similar procedure applies to Solaris with gamesparc instead of gamei386)
Repeat the following for every mod for which you want to add GameCam:

rename the game library from gamei386.so to gamei386.real.so
extract the GameCam gamei386.so to the mod directory
You should now have two .so files in each mod directory: gamei386.so (GameCam), and gamei386.real.so (the original game library).
UnInstall

Windows 95/98/NT: Delete the new gamex86.dll from the release folder.
Unix: Delete the new gamei386.so from each mod directory and rename gamei386.real.so back to gamei386.so.

GameCam and Other Plug-in Mods

BW-Admin and Q2Admin

(the following applies to both Win32 and Unix servers)
Install GameCam, create a new directory named proxy under the quake2 directory. Place the BW-Admin library under another new directory: proxy/bwadmin and/or Q2Admin under proxy/q2admin. Make sure to place all the configuration files of these plugins at their correct locations, as if they were installed normally.

To activate the other plugin you have to launch the server with either +set proxy bwadmin or +set proxy q2admin added to the command line.

Note that I don't support this configuration. Use it at your own risk.

ProxyMod Standard Mods (Win32)

GameCam can be used with any number of plug-in mods based on the ProxyMod (the "blank" plug-in) source code. These include ProxyMod itself, ZKick, EntZ, and the forthcoming GameBot.
To load any number of proxy modules you should follow the next procedure:

place one proxy module in the C:\Quake2\release folder (I use ProxyMod - but you can use any other)
create a new folder: C:\Quake2\proxy
place all other proxy mods in their own folders: GameCam in C:\Quake2\proxy\gamecam\, EntZ in C:\Quake2\proxy\entz\, ZKick in C:\Quake2\proxy\zkick\, etc.
to run a server with any of these plug-ins active you need to set the proxy cvar to a colon seperated list of proxy mods:
quake2 +set proxy zkick:entz:gamecam <rest_of_command_line>
will load ProxyMod (or whatever plug-in is installed in C:\Quake2\release), and then ZKick, EntZ and GameCam, and then the real game DLL will be loaded from the folder specified by the game cvar.

table of contents

Usage

The following sections explain how to use GameCam on the server side and on the client's side.
Server Side

Server Setup

GameCam is transparent. You should be able to setup a server for any game you want, the same way as before the installation:
quake2 +set game <gamedir>, etc.
GameCam prints a startup message to the console, before the game begins. GameCam also prints an optional welcome message to the players' console (saying "[GameCam]: type 'camera ?' for help").

A set of configuration files for several mods (CTF, LMCTF, HeadHunters, QPong, CTC, Predator, and TagYerIt) is available as a separate package. The configuration files are optional - GameCam should work just fine without them, but may look better with them. Consult the configuration section for details.

Console Variables

gc_version
GameCam version string (read-only).
gc_count
Number of GameCam spectators (serverinfo, read-only).
gc_flags
GameCam configuration flags (archived, default is "18147").
This cvar works very much like dmflags - you add up the values for each flag to get the required setting:
GCF_SUICIDE (1) - enable spectator suicide upon camera off (default: on).
GCF_ALLOW_CHASE (2) - enable CHASE mode (default: on).
GCF_ALLOW_FREE (4) - enable FREE mode (default: off).
GCF_ALLOW_SAY (8) - enable spectator chat (default: off).
GCF_VERBOSE (16) - print message when changing camera mode (default: off).
GCF_WELCOME (32) - enable welcome message (default: on).
GCF_AVOID_BOTS (64) - avoid bots when showing scoreboard (default: on) - must be on for Gladiator Bot (otherwise it'll crash), and may be off for Eraser.
GCF_DEFAULT_ID (128) - turn player id display on by default (default: on).
GCF_DEFAULT_TICKER (256) - turn ticker tape on by default (default: off).
GCF_DEFAULT_FIXED (512) - turn fixed cameras on by default (default: on) - this only takes effect if the map has fixed cameras defined for it.
GCF_DEFAULT_AUTO (1024) - turn auto chase camera position (creep camera) on by default (default: on).
GCF_DEFAULT_DEMO (2048) - turn auto demo recording on by default (default: off).
GCF_LOCK_SERVER (4096) - lock the server (refuse connection) in General Admission (tournament) mode when match is in progress (default: off).
GCF_TEAMS (8192) - use the gc_teams cvar to distinguish between teams (default: off).
GCF_SPECTATOR (16384) - replace in-game spectator mode (default: on) - flag is ignored in General Admission mode. Note that setting this flag causes spectator_password to override gc_password, and maxspectators to override gc_maxcameras.

gc_password
Spectator mode password (default is "" - i.e. no password).
gc_maxcameras
Maximum number of spectators allowed (archived, default is 4). Set this to 0, to allow all players to become spectators. Value is ignored in General Admission mode.
gc_maxplayers
The maximum allowed players. This doesn't reject new clients, but rather prevents a spectator from joining the game with camera off, when enough players are already playing (default is 0, which disables this feature). Value is used only in General Admission mode.
gc_autocam
Set this to 1 in order to put the server in General Admission mode, to force everyone to enter the game as spectators (latched, default is 0).
gc_motd
The General Admission welcome message (default is "\!GameCam\! General Admission\nEnjoy the Show!\n\n\ntype '\!camera\!' to see the menu").
gc_ticker
Name of ticker script, without extension (archived, default is "" - which loads an internal default script). Ticker script file name extension is ".led".
gc_maxscores
The number of top scores to list on the ticker tape (archived, default is 5, set to 0 to list all players).
gc_teams
Used with GCF_TEAMS to distinguish between teams (archived, default is "" - allowed values are "model", "skin", "gun", "model2", "model3", "model4"). Used in creep-cam mode to help it prefer tracking the other team's players.
gc_update
Number of minutes between timer updates in tournament mode (archived, default is 5 - 0 disables timer updates).
proxy
Proxy module chain string (serverinfo, latched).
nextproxy
Internal to proxy module loading mechanism (read-only).
Client Side

With the default settings GameCam replaces the in-game spectator mode. Combined with the camera menu this means that clients don't need to use any of the following commands or keyboard bindings ...

Camera Menu

The camera menu can only be accessed by spectators. The menu can be toggled with the camera command or with the TAB key (inven), and its use is self evident. Note that most camera console commands are disabled while using the menu, and camera mode changes take effect only when the menu is removed.
The following console commands are enabled while the menu is displayed: camera off, camera menu, camera ? and camera.


Console Commands

camera
toggle camera menu on/off (works for spectators only)
camera menu
toggle camera menu on/off
camera ?
show help message
camera on [<password>]
enter spectator mode, with optional password
camera off [<password>]
exit spectator mode, with optional password (password needed only in General Admission mode)
camera id
toggle identification of player in view (FREE and ACTION camera modes)
camera free
FREE camera mode
camera chase
CHASE camera mode
camera action
ACTION camera mode
camera action normal
ACTION camera NORMAL sub-mode
camera action follow
ACTION camera FOLLOW sub-mode
camera max_xy [<value>]
show/set maximum x/y lag for ACTION mode
camera max_z [<value>]
show/set maximum z lag for ACTION mode
camera max_angle [<value>]
show/set maximum yaw angle lag for ACTION mode
camera select [auto | <id>]
show/set current target in ACTION/CHASE mode (auto reverts to automatic target selection in ACTION mode)
camera chase auto
toggle camera auto position (creep-camera) in CHASE mode
camera demo
toggle auto demo recording
camera ticker
toggle display of ticker tape in ACTION and FREE mode
camera inven
toggle display of player inventory in CHASE mode
camera layout
toggle display of player layouts in CHASE mode (allows you to see if player is watching the scoreboard or uses menus)
camera fixed
toggle the use of fixed cameras in ACTION mode, when such cameras are defined
The following commands are available only on a non-dedicated server for client #0 in FREE mode:

camera list
list all fixed cameras
camera add ["name"]
add camera at current position, view angles and fov (default name is "unnamed camera")
camera update ["name"]
update current camera (will add camera if new)
camera remove
remove the current camera
camera next
go to the next camera
camera prev
go to the previous camera
camera none
deselect current camera
camera save
save cameras to file <basedir>/<game>/cameras/<mapname>.cam
Keyboard Bindings

While in spectator mode (camera on):

use [ or ] (invprev, invnext) to enter CHASE mode from FREE and ACTION modes
use [ and ] (invprev, invnext) to switch to the previous/next client while in CHASE mode
use BACKSPACE (invdrop) to enter FREE mode
use ENTER (invuse) to enter ACTION mode
use TAB (inven) to toggle the camera menu
use F1 (help) or X (score) to toggle the scoreboard (updated every ~3 seconds)
use CTRL (+attack) to reset manual CHASE camera position
use mouse or normal movement keys to manually adjust CHASE camera position (camera can be moved up/down and backward/forward, strafe left/right, turned up/down and left/right)

table of contents

Configuration

GameCam should work just fine without any special configuration, but may look and behave much better with it. The following first two sections explain how to tweak the CHASE camera and the ACTION camera target selection. The third section deals with fixed cameras (how to define and use them), and the last section is a description of the simple script language used for programming the GameCam ticker tape.
CHASE Camera Target Selection

The GameCam CHASE camera has two modes of operation:
MANUAL - this is the familiar CTF chase camera, only that spectators can adjust the camera position and view angles with the movement keys (or mouse). The camera may be reset with the CTRL key (+attack command).
AUTO - the computer adjusts the camera position and view angles automatically to provide the best view of the closest opponent. I refer to this mode as creep-camera because the first camera mod to ever use this concept was CreepCam for (classic) Quake (but the GameCam creep-camera uses my own original algorithm).
Obviously, in order to get the best results, GameCam has to figure out who are the chased player's opponents and who are his team mates. The problem is that different mods use different ways to distinguish between teams.
By default GameCam detects teams by following the next rules:

if either DF_SKINTEAMS (64) or DF_MODELTEAMS (128) is set in dmflags, then GameCam detects teams by skin or by model (respectively)
if the game folder name has the string "ctf" (or "CTF") in it, then GameCam detects teams by skin
But not all CTF games use skins for teams, and other mods use other methods (e.g. HeadHunters uses disks). GameCam can be configured to distinguish between teams by looking at their model, skin, gun, and auxiliary models 2, 3 and 4 (e.g. HeadHunters disks). To do that just set the flag GCF_TEAMS (8192) in gc_flags, and set gc_teams to one of the following values: "skin", "model", "gun", "model2", "model3" or "model4".

Long explanation, short solution ...

ACTION Camera Target Selection

The ACTION camera may be configured to focus on specific types of players, based on a priority list.
By default, the ACTION camera focuses on the player that can see the maximum number of players (favoring players with larger frag counts). This behavior may not suit some mods - e.g. in CTF the camera should favor flag carriers, and in HeadHunters the camera should focus on players carrying the largest number of heads.

When using the priority based target selection scheme, GameCam first attempts to find a player that matches one of the potential targets specified in gamecam.ini. If a match is found, GameCam focuses on that player (favoring players that see the most players and have the most frags). If a match is not found, GameCam reverts to the default selection scheme, and attempts to find the spot where most of the players are located.

Each game folder should have its own gamecam.ini (if needed). This file holds a list of potential targets, grouped by priority. Each target is specified as "<type> <value>", where <type> is one of the following:

model - player plugin model; <value> is <model>/<skin>.
gun - player gunindex model (weapon view model); <value> is the model's (.md2) file path.
model2 - player modelindex2 model; <value> is the model's (.md2) file path.
model3 - player modelindex3 model (CTF flag, HH heads); <value> is the model's (.md2) file path.
model4 - player modelindex4 model; <value> is the model's (.md2) file path.
shell - player shell; <value> is a pair of numbers separated by a colon - <effect>:<renderfx> (e.g. quad is 32768:0, pentagram is 65536:0, and 256:<color> is a color shell - consult id software's source code for more values).
Several example configuration files are available for download.

Note that gamecam.ini contains the target list only and is not used for anything else. Any console variable setting should be placed in your server's configuration script (autoexec.cfg, server.cfg etc.).

Fixed Cameras

The ACTION camera can find its way around the map without any help. The dynamic behavior of the camera generates very cool shots most of the time. However, sometimes it looks better if the camera always films the action from the same position in certain areas of the map.
To enable this you can define fixed cameras for each area in each map that you think would be best covered from specific positions. GameCam uses fixed cameras as long as the player being filmed is visible by some camera. When the player goes out of sight GameCam reverts to the free moving ACTION camera, until another camera has the player in view.

So here's what you should do:

start up a listen (i.e. not dedicated) server and load the required map
set the flag GCF_ALLOW_FREE (4) in gc_flags, so that you can enter FREE mode
type camera on and then use the menu to switch to FREE mode (or type camera free)
move through the level to find a good spot for the camera, tweak the zoom (fov) to your liking and when ready type camera add "<name>" (where "<name>" is the name of the camera, which is later displayed to spectators at the bottom of the screen)
repeat the last step for all other spots
use camera list to list all the cameras, and camera next or camera prev to cycle thru the cameras and review your work
use camera remove to delete the current camera, and camera update ["<name>"] to modify its parameters
save the cameras to file with camera save (this will generate a file named mapname.cam under a new cameras sub-folder in the current game's folder, where mapname is the name of the current map)
(Linux: the cameras directory has to be created manually before you attempt to save!)
The new camera file will be auto-loaded by GameCam the next time you load that map, so that the above procedure can be used to edit an existing camera file. To test your work I recommend you run the map with bots, to see whether the resulting camera behavior looks good.
IMO it's not a good idea to cover all the map with cameras - a better approach seems to use fixed cameras to cover large (open) areas or strategic spots, and let the free moving camera have control over the rest of the map.

Ticker Tape Scripts

The GameCam ticker tape can be programmed with a simple script language which is a subset of the script language used to program the Java LEDSign Applet.
Script Commands

Appear - display text
Sleep - wait (current text is kept unchanged)
ScrollLeft - scroll text from right to left
ScrollRight - scroll text from left to right
Blink - blink text several times with a specified delay
Do - begin loop
Repeat - end loop (loop is executed a specified number of times)
Reload - reloads the script file (this allows an external utility to update the script automatically!)
Commands Parameters

All script commands have parameters:
delay - delay in frames (10 frames = 1 second - applies to Sleep and Blink commands only)
times - times to perform command (applies to Repeat and Blink commands only). Note that "Repeat times=-1" is used to generate infinite loops.
clear - clear text flag (possible values: true or false), this parameter overrides any of the following
center - center text flag (possible values: true or false)
startspace - number of spaces before text (ignored if centered)
endspace - number of spaces after text (ignored if centered)
text - text to display (must be last parameter on the line)
Note that some parameters have no effect on some commands so they are simply ignored if encountered.

Text Codes

The ticker text may include the following escape sequences and codes:
\!text\! - highlight text
\" - quotation mark
\\ - back slash
\x00 - special character: hexadecimal ascii code ('x' and two hex digits)
\000 - special character: octal ascii code (three octal digits)
\{$cvar$} - any console variable (replace 'cvar' with name of cvar)
\{sb} - top scores (number of entries controlled by gc_maxscores)
\{tt} - current time (12 hour format)
\{hh} - current hour (12 hour format)
\{HH} - current hour (24 hour format)
\{hm} - current minutes
\{ss} - current seconds
\{am} - "am" or "pm"
\{AM} - "AM" or "PM"
\{dd} - day of the week (Sun Mon etc.)
\{DD} - day of the week (Sunday Monday etc.)
\{dn} - day of the month
\{mn} - month number (1-12)
\{mm} - month name (Jan Feb etc.)
\{MM} - month name (January February etc.)
\{yy} - year (two last digits)
\{YY} - year (four digits)
These escape sequences are also available for the General Admission MOTD.
Using The Script

After writing down your script save it to the current game folder with extension ".led". Set gc_ticker to be the name of this script file without the extension (e.g. "myscript" for "myscript.led"). The script will be loaded as soon as someone becomes a spectator.
Example Script

The following script is the internal script used by GameCam when gc_ticker doesn't point to any valid script file.
Do
Appear center=true text=\!GameCam\! v1.02
Sleep delay=10
ScrollLeft center=true text=\x90\x80\x91 1998-99, Avi \"\!Zung!\!\" Rozen
Sleep delay=10
ScrollRight center=true text=http://www.telefragged.com/\!zungbang\!
Do
Sleep delay=3
Appear center=true text=http://www.telefragged.com/zungbang
Sleep delay=3
Appear center=true text=http://www.telefragged.com/\!zungbang\!
Repeat times=3
Sleep delay=10
ScrollLeft center=true text=\!TOP SCORES\! . . .
ScrollLeft endspace=39 text=\{sb}
Sleep delay=10
Appear center=true text=type '\!camera\!' to see the menu
Sleep delay=10
ScrollRight center=true text=\!GameCam\! v1.02
Repeat times=-1

table of contents

Compatibility

GameCam has been tested with Quake II v3.20 and the following mods on public servers: Lithium II (see notes below), Zoid's CTF and other CTF variants, Rocket Arena II, Weapons Of Destruction, Action Quake 2, HeadHunters 2 and more. I've tested GameCam with several other mods and it seems to work just fine. It's likely that GameCam can work with most game modules out there, but there's no guarantee.
There are some known compatibility issues that I don't intend to address (for technical reasons):

The HUD and scoreboard are mostly broken with Lithium due to the unconventional layouts in this mod. But the camera itself works just fine.
Some mods provide several formats for the scoreboard that can be cycled thru with the score command - GameCam can only show the first format available.
Some mods have parts of the scoreboard actually implemented as part of the statusbar (HUD). GameCam does its own handling of the HUD, so it might not be able to show the scoreboard correctly in these cases.
With a few mods the ACTION camera algorithm makes very little sense - and it'll look pretty stupid. Proper configuration may solve this, but some mods are just too original to handle. Remember that GameCam also has an enhanced CHASE camera ...
GameCam supports emulated clients (i.e. bots) only in ACTION mode (bots can't be chased). This feature has been tested with Eraser v1.01, Gladiator v0.9 and CRBot v1.14 and is known to have some quirks (for example: when the spectator is the only client, bot chat messages are not displayed, and the CTF scoreboard plaques are lost after a level change).
These problems are due to limitations inherent to the proxy module concept, and the fact that client emulation is just that: emulation.
Note that you should clear the flag GCF_AVOID_BOTS in gc_flags in order to view the scoreboard with Eraser or CRBot. This flag must be set with the Gladiator Bot, or else the server will barf an error and die as soon as you try to view the scoreboard (this means that you can't view the scoreboard unless there is another real client connected to the game).
GameCam overrides any game native camera console command (if it exists).

Currently GameCam is available for Win95/98/NT, Linux (libc5 and glibc) and Solaris (Sparc).


Copied and Pasted from http://jasonwilliams400com.startlogic.c ... _v1.02.htm

User avatar
MetalGod
Posts: 276
Joined: Sun Apr 09, 2006 8:18 am
Location: New York
Contact:

Re: Adding the GameCam Proxy

Post by MetalGod » Sun Jun 09, 2013 5:59 pm

Aside from being a really poorly written article. That would require a ton of modification to the code to get it to be compatible with Dday. I don't it would be high on the priority list, if considered at all.

User avatar
[IRS] Aeon6911
Posts: 21
Joined: Sat Jun 08, 2013 7:53 pm

Re: Adding the GameCam Proxy

Post by [IRS] Aeon6911 » Sun Jun 09, 2013 11:16 pm

It works on my server fine. However, I have not set up any static cams though. When you get a moment, take a look at my server and see how it works.

User avatar
TeRRor
Posts: 474
Joined: Tue Jul 27, 2010 3:52 am
Location: Croatia

Re: Adding the GameCam Proxy

Post by TeRRor » Tue Jun 11, 2013 11:27 am

The camera works.
Image

User avatar
MetalGod
Posts: 276
Joined: Sun Apr 09, 2006 8:18 am
Location: New York
Contact:

Re: Adding the GameCam Proxy

Post by MetalGod » Tue Jun 11, 2013 11:41 am

Post your server ip, please. It's not showing up in Qtracker.

User avatar
TeRRor
Posts: 474
Joined: Tue Jul 27, 2010 3:52 am
Location: Croatia

Re: Adding the GameCam Proxy

Post by TeRRor » Tue Jun 11, 2013 1:11 pm

50.40.162.61:27910
Image

User avatar
[IRS] Aeon6911
Posts: 21
Joined: Sat Jun 08, 2013 7:53 pm

Re: Adding the GameCam Proxy

Post by [IRS] Aeon6911 » Tue Jun 11, 2013 6:35 pm

Sorry about that guys. Here is the current ip for it. 50.40.162.61:27910 . It shows up on q2servers.com . My ip changes everytime the power goes out here. As far as the qtracker goes, I don't know why it does not show up. The same for the server browser.

User avatar
InFerNo
Developer
Developer
Posts: 4371
Joined: Mon Aug 25, 2003 11:07 am
Location: dday2
Contact:

Re: Adding the GameCam Proxy

Post by InFerNo » Thu Jun 13, 2013 6:49 pm

register on afraid.org to get a dynamic dns address.
Image

Post Reply