SourceMod plugin for competitive Neotokyo. WIP.
nt_fadefix - Block any unintended un-fade user messages. Hide new round vision to block "ghosting" for opposing team's loadouts.
Some optional features also require:
PLUGIN_VERSIONCompetitive plugin version.FCVAR_DONTRECORD1How a match win is determined. 1 = best of X rounds, 2 = first to X points1.02.015If sm_competitive_round_style equals 1, this is the best of X rounds. If it equals 2, this is the score required to win.1.010How many players total are expected to ready up before starting a competitive match.2How many time-outs are allowed per match per team.0.060How long can a competitive time-out last, in seconds.0.0300How long can a pause last when team experiences technical difficulties.0.01Should the competitive plugin automatically record SourceTV demos.0.01.0replays_competitiveDirectory to save SourceTV demos into. Relative to NeotokyoSource folder. Will be created if possible.JinraiJinrai team's name. Will use \"Jinrai\" if left empty.NSFNSF team's name. Will use \"NSF\" if left empty.Name of the tournament/competition. Also used for replay filenames. 32 characters max. Use only alphanumerics and spaces.0Voice comms behaviour when live. 0 = no alltalk, 1 = enable alltalk, 2 = check sv_alltalk value before live state0.02.01Competitive logging mode. 1 = enabled, 0 = disabled.0.01.01How much info is given to players upon death. 0 = disabled, 1 = print amount of players remaining to everyone, 2 = only show the victim how much damage they dealt to their killer, 3 = only show the victim their killer's remaining health0.03.000 = display kill info instantly, 1 = display kill info nextround0.01.01Should clients automatically record when going live.0.01.00Team restrictions when game is live. 0 = players can join any team, 1 = only players present when going live can play in their teams 2 = new players can join teams midgame0.02.01Are teams enforced to use set numbers (5v5 for example).0.01.02Pausing mode. 0 = no pausing allowed, 1 = use Source engine pause feature, 2 = stop round timer0.02.00Can a team collectively ready up by anyone of the players. Can be useful for more organized events.0.01.01Whether or not to disable timeout wins.0.01.00Competitive plugin's internal score cvar. Editing this will directly affect comp team scores.0.00Competitive plugin's internal score cvar. Editing this will directly affect comp team scores.0.01Whether or not to allow match to end in a tie. Otherwise, game proceeds to sudden death until one team scores a point.0.01.01How the number of remaining players is displayed to clients in a competitive game. 0 = disabled, 1 = show remaining player numbers, 2 = show team names and remaining player numbers0.02.03Who to center display remaining players to. 1 = spectators only, 2 = spectators and dead players, 3 = everyone1.03.0vsWhat kind of divider to use between the scores (eg. 3 vs 2, 3 v 2, 3--2)45Add up to this many seconds to the round time while the ghost is held.0.0120.015Freeze the round timer at this many seconds while the ghost is held. Will decay and end at 0 when the overtime runs out. 0 = disabled0.030.00Whether ghost overtime decay should be exponential or linear. Exponential requires grace reset to be enabled. 0 = linear, 1 = exponential0.01.01When the ghost is picked up, reset the timer to where it would be on the decay curve if the ghost was never dropped. This means the full overtime can be used even when juggling.0.01.0To illustrate how the timer behaves with default settings: Ghost overtime kicks in at 15 seconds on the clock and will add a maximum of 45 seconds to the round. This gives us a total of 15 + 45 = 60 seconds for the timer of 15 seconds to decay. 60 / 15 = 4, meaning each second on the clock during ghost overtime will last for 4 real seconds.
* Ghost is picked up at 15 seconds and is held for 16 seconds. The timer shows 10 (15 - 16/4 = 11, rounded down to 10 for simplicity).
* The ghost is dropped, making the timer speed up.
* 8 seconds later the ghost is picked up again. Since grace reset is enabled, the timer jumps from 2 to 8 seconds (10 - 8/4 = 8).The nt_competitive plugin modifies player score/deaths values under some conditions. If you're a plugin developer and would like to override this behaviour, a global forward is exposed for this:
function Action Competitive_OnPlayerScoreChange(PlayerScoreChangeReason reason, int client);The shared header is available at scripting/nt_competitive/nt_competitive_shared.inc.
Example of overriding the score change behaviour from your plugin:
#include <sourcemod>
// needed for the PlayerScoreChangeReason enum definition
#include "nt_competitive/nt_competitive_shared"
// optional: handle cases where the forward doesn't exist,
// if it's critical to your plugin
public void OnAllPluginsLoaded()
{
if (!LibraryExists("CompetitiveFwds"))
{
PrintToServer("Competitive forwards don't exist!");
if (null != FindConVar("sm_competitive_version"))
{
// nt_competitive exists, but it doesn't have the forward.
// Is the nt_competitive plugin out of date?
}
else
{
// nt_competitive plugin does not exist
}
}
}
// listener for the global forward from nt_competitive
public Action Competitive_OnPlayerScoreChange(PlayerScoreChangeReason reason, int client)
{
bool allow = true;
if ( true /* replace with your custom condition! */ )
{
allow = false; // Block the nt_competitive score change!
}
// return Plugin_Continue to allow the nt_competitive score change.
// return Plugin_Handled to block the nt_competitive score change.
return allow ? Plugin_Continue : Plugin_Handled;
}