War Mode (SourceMod) - Revision history

MisakaSora at 09:43, 11 September 2019

2019-09-11T09:43:05Z

Fireandy: /* Sample Files */ Corrected warmode_off to warmode_on and vice versa

2008-04-01T03:44:57Z

‎Sample Files: Corrected warmode_off to warmode_on and vice versa

BAILOPAN at 17:31, 16 December 2007

2007-12-16T17:31:59Z

BAILOPAN at 05:40, 22 October 2007

2007-10-22T05:40:45Z

BAILOPAN at 05:40, 22 October 2007

2007-10-22T05:40:26Z

BAILOPAN: New page: SourceMod does not have a "war mode" built-in. Instead, it has options that let you lock-down SourceMod to only keep a few plugins loaded. Matches can be completed without SourceMod inte...

2007-10-22T05:39:54Z

New page: SourceMod does not have a "war mode" built-in. Instead, it has options that let you lock-down SourceMod to only keep a few plugins loaded. Matches can be completed without SourceMod inte...

New page

SourceMod does not have a "war mode" built-in. Instead, it has options that let you lock-down SourceMod to only keep a few plugins loaded. Matches can be completed without SourceMod interfering, and once done, SourceMod can be "unlocked" again. You can still retain administrative control.

There are a few plugins that are absolutely safe to use for matches. They are:
*<tt>adminhelp.smx</tt> - Provides the <tt>sm_help</tt> command.
*<tt>adminmenu.smx</tt> - Provides the <tt>sm_admin</tt> command. Note that menu items are only added from other plugins, and thus enabling the menu plugin will not add abusive admin commands unless the plugin implementing those commands is also loaded.
*<tt>admin-flatfile.smx</tt>, <tt>admin-sql-threaded.smx</tt>, and <tt>admin-sql-prefetch.smx</tt> - These three plugins simply load administrators.
*<tt>basebans.smx</tt> - Ban/unban functionality. [[Admin_Commands_%28SourceMod%29#Ban/Unban Commands|Click here]] for command listing.
*<tt>basecommands.smx</tt> - General, non-abusive admin commands. [[Admin_Commands_%28SourceMod%29#Basic Commands|Click here]] for command listing.

Implementing warmode is very simple. Two sample configs are provided as <tt>cfg/sourcemod/sm_warmode_on.cfg</tt> and <tt>cfg/sourcemod/sm_warmode_off.cfg</tt>.

The first file, <tt>sm_warmode_on.cfg</tt>, does three things:
*Unloads all plugins.
*Re-loads the "safe" plugins.
*Locks any more plugins from being loaded.

The second file, <tt>sm_warmode_off.cfg</tt>, removes the plugin loading lock, and then reloads all plugins from the plugins folder (as would happen on server start).

You can simply use <tt>sm_execcfg</tt>, <tt>rcon exec</tt>, or the admin menu to run these configs. Of course, you can also change or rename them. Samples are provided in the default package, and also reproduced below.

<tt>sm_warmode_off.cfg</tt>:
<pre>
//This file unloads all plugins, re-loads a few "safe" ones, and then prevents
//any more plugins from being loaded.
sm plugins unload_all
sm plugins load basebans.smx
sm plugins load basecommands.smx
sm plugins load admin-flatfile.smx
sm plugins load adminhelp.smx
sm plugins load adminmenu.smx
sm plugins load_lock
</pre>

<tt>sm_warmode_on.cfg</tt>
<pre>
//This file re-enables a server from "war mode" by unlocking plugin loading
//and refreshing the plugins list.
sm plugins load_unlock
sm plugins refresh
</pre>

@@ Line 1: / Line 1: @@
 __FORCETOC__
+{{Languages|War Mode (SourceMod)}}
 SourceMod does not have a "war mode" built-in.  Instead, it has options that let you lock-down SourceMod to only keep a few plugins loaded.  Matches can be completed without SourceMod interfering, and once done, SourceMod can be "unlocked" again.  This way you can still retain administrative control.

@@ Line 27: / Line 27: @@
 =Sample Files=
-<tt>sm_warmode_off.cfg</tt>:
+<tt>sm_warmode_on.cfg</tt>:
 <pre>
 //This file unloads all plugins, re-loads a few "safe" ones, and then prevents
@@ Line 40: / Line 40: @@
 </pre>
-<tt>sm_warmode_on.cfg</tt>:
+<tt>sm_warmode_off.cfg</tt>:
 <pre>
 //This file re-enables a server from "war mode" by unlocking plugin loading

← Older revision		Revision as of 17:31, 16 December 2007
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__

−	SourceMod does not have a "war mode" built-in. Instead, it has options that let you lock-down SourceMod to only keep a few plugins loaded. Matches can be completed without SourceMod interfering, and once done, SourceMod can be "unlocked" again. ~~You~~ can still retain administrative control.	+	SourceMod does not have a "war mode" built-in. Instead, it has options that let you lock-down SourceMod to only keep a few plugins loaded. Matches can be completed without SourceMod interfering, and once done, SourceMod can be "unlocked" again. This way you can still retain administrative control.
		+
		+	Of course, it is subjective as to which plugins are usable in war mode. You can tweak SourceMod to achieve the functionality you wish to retain.

@@ Line 1: / Line 1: @@
 SourceMod does not have a "war mode" built-in.  Instead, it has options that let you lock-down SourceMod to only keep a few plugins loaded.  Matches can be completed without SourceMod interfering, and once done, SourceMod can be "unlocked" again.  You can still retain administrative control.
 There are a few plugins that are absolutely safe to use for matches.  They are:
 *<tt>adminhelp.smx</tt> - Provides the <tt>sm_help</tt> command.
@@ Line 8: / Line 12: @@
 *<tt>basecommands.smx</tt> - General, non-abusive admin commands.  [[Admin_Commands_%28SourceMod%29#Basic Commands|Click here]] for command listing.
 Implementing warmode is very simple.  Two sample configs are provided as <tt>cfg/sourcemod/sm_warmode_on.cfg</tt> and <tt>cfg/sourcemod/sm_warmode_off.cfg</tt>.
@@ Line 19: / Line 24: @@
 You can simply use <tt>sm_execcfg</tt>, <tt>rcon exec</tt>, or the admin menu to run these configs.  Of course, you can also change or rename them.  Samples are provided in the default package, and also reproduced below.
 <tt>sm_warmode_off.cfg</tt>:
 <pre>