-
Notifications
You must be signed in to change notification settings - Fork 94
2.4. Configuration: Replay
rtldg edited this page May 22, 2022
·
2 revisions
You can change some of the replay bot (ghost)'s behavior and its appearance.
To change the replay bot's appearance, open the configuration file.
Here's the default configuration file:
// Configuration file for replay bot styling.
//
// WARNING: DO NOT DELETE/ADD YOUR OWN KEYS!
// WARNING: IF YOU DISABLE THE CENTRAL REPLAY BOT - MAKE SURE BOT NAMES CONTAIN A VARIABLE OR YOU'LL END UP WITH A MESS!
//
// The replay bot clan/name styling will be loaded from this file.
// A central bot is the replay bot that can play all styles. It's enabled by default with "shavit_replay_centralbot".
//
// Keys:
// "clantag" - clan tag for replay bots (central or not) to use.
// "namestyle" - this is the name style replay bots will use. Including the central bot, as long as it's during playback.
// "centralname" - the central bot's idle name, AKA when nothing is playing.
//
// Variables:
// {map} - current map.
// {style} - the style name.
// {styletag} - the style's tag. See "clantag" in "shavit-styles.cfg".
// {time} - formatted time for the WR currently being played.
// {player} - the name of the player that holds the *record*, might be incorrect for replays from the beta version of bhoptimer.
// {track} - track that the bot replays. Translated from the server's defined language.
// {type} - Replay bot type. Central, Dynamic, and Looping...
//
"Replay"
{
"clantag" "{type}"
"namestyle" "{track} {style} - {time}"
"centralname" "!replay"
// Replay data folder. This is where replays are loaded from and saved to.
// Note: To use a path outside of the game directory, you will have to get out of it with "../".
// Edit at your own risk.
//
// Variables:
// {SM} - SourceMod folder. If this variable isn't included, you will have to specify the full path.
"replayfolder" "{SM}/data/replaybot"
// "enabled" - whether the looping bot will spawn in when there's replay data
// "tracks" - semicolon seperated list of track numbers to loop through. 0 (main), 1-8 (bonus)
// "styles" - semicolon seperated list of style numbers to loop through.
"Looping Bots"
{
"Main Normal Bot"
{
"enabled" "1"
"tracks" "0"
"styles" "0"
}
"Main Segmented Bot"
{
"enabled" "1"
"tracks" "0"
"styles" "7"
}
"Other Styles"
{
"enabled" "1"
"tracks" "0"
"styles" "1;2;3;4;5;6;8;9;11;12;13;14;15;16"
}
"Bonus Normal Bot"
{
"enabled" "1"
"tracks" "1"
"styles" "0"
}
"Shit Bonuses Bot"
{
"enabled" "1"
"tracks" "2;3;4;5;6;7;8"
"styles" "0"
}
"TAS Bot"
{
"enabled" "1"
"tracks" "0;1;2;3;4;5;6;7;8"
"styles" "10"
}
"Dumb Styles Bot"
{
"enabled" "0"
"tracks" "0"
"styles" "4;6"
}
}
}
The replay bot can have extra configuration applied via cfg/sourcemod/plugin.shavit-replay.cfg
. I'll explain most of the interesting stuff:
-
shavit_replay_centralbot
- decides on if there's a central replay bot. A central bot is a single bot that can play all kinds of replays and is toggled with +USE or !replay. If disabled, each style for the main track will get its own replay bot that replays itself. Note: Support will not be given if this is set to 0. -
shavit_replay_bot_enabled
- if set to 0, replay bots won't show up. I recommend leaving this as 1 and then disabling for exclusive game modes/maps. -
shavit_replay_timelimit
- this setting controls the maximum amount of time per recording to be saved. The default setting is 5400.0 - 1:30 hours! If your server has a slow playstyle (_strafe/400 velocity/scroll etc) I recommend increasing this value, as runs above 1:30 hours will occur often. -
shavit_replay_dynamicbotlimit
- this determines how many dynamic replay bots can be spawned by players.