-
Notifications
You must be signed in to change notification settings - Fork 0
/
replay_example.cfg
79 lines (72 loc) · 2.98 KB
/
replay_example.cfg
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
//
// Example replay configuration file.
//
// DO NOT MODIFY THIS FILE! Instead, copy this file to replay.cfg and modify that file.
// You will need to select either FTP offload mode, or local HTTP server mode.
// Note that it is NOT enough to exec this config file. The -replay switch much be present on the
// command line, for example:
//
// srcds -game tf -console -replay
//
// The replay system will do a sanity check at startup to help you debug any issues.
//
// For a full overview on getting setup, view the "Replay Overview for Server Operators & FAQ" here:
//
// http://forums.steampowered.com/forums/showthread.php?t=1882475
//
// Enable replay!
replay_enable "1"
// How often we dump replay data. You should not need to modify this value.
replay_block_dump_interval "15"
// This is the method by which clients download replay data. At the moment, only HTTP is available.
replay_fileserver_protocol "http"
// There are currently two supported ways that your replay server can operate:
//
// - The "local HTTP" method requires that you run a web server on the
// same machine as your game server, or at least that your gameserver can
// get the files to the HTTP server using local filesystem paths and ordinary
// filesystem copies. (For example, an NFS share.)
//
// - The "FTP" method allows you to offload replay data to another machine (which
// must be running a web server) over FTP. Clients will download their replay
// data over HTTP.
//
// Select one of those two methods, uncomment the appropriate block of code below,
// and modify the convars appropriately.
/////////////////////////////////////////////////////////////////////////////
//
// Local HTTP mode
//
//// Don't offload over FTP. Use a local web server.
//// You don't need to edit this line, just uncomment it.
//replay_fileserver_offload_enable "0"
//
//// The replay data will be copied to this directory
//replay_local_fileserver_path "/path/to/my/web/server"
//
//// These are used to reconstruct a URL on the client.
//replay_fileserver_host "my.server.com"
//replay_fileserver_port "80"
//replay_fileserver_path "/replays"
/////////////////////////////////////////////////////////////////////////////
//
// FTP mode
//
//
//// Offload using FTP. Do not use a local web server.
//// You don't need to edit this line, just uncomment it.
//replay_fileserver_offload_enable "1"
//
//// These are used to reconstruct a URL on the client.
//replay_fileserver_host "my.server.com"
//replay_fileserver_port "8080"
//replay_fileserver_path "/"
//
//// Your FTP info. This data is private and not shared with the client.
//replay_fileserver_offload_protocol "ftp"
//replay_fileserver_offload_hostname "ftp.my.server.com"
//replay_fileserver_offload_port "21"
//replay_fileserver_offload_remotepath "/"
//replay_fileserver_offload_login "username"
//replay_fileserver_offload_password "password"
//replay_fileserver_offload_maxuploads "16"