There have been a few plugins made for the Source engine based off Valve's example code, and posted to the SourceMod site. Although we're waiting for SourceMod before officially supporting Source plugins, if you are looking to add functionality to your Source-based server, you might consider one of these.
The current consensus is generally that this one is the best: http://www.sourcemod.net/forums/viewtopic.php?t=222. It comes with simple install instructions that you can use to add it through our FTP, and it appears to be compatible with our systems.
Source plugins
-
Edge100x
- Founder
- Posts: 13109
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Thu Apr 18, 2002 11:04 pm
- Location: Seattle
- Contact:
Source plugins
Last edited by Edge100x on Sun Dec 12, 2004 11:08 pm, edited 1 time in total.
I keep getting questions in email about Source plugins.
Again, we do not officially support these yet. If you want to install a Source plugin, that's great, but we don't officially support them. This thread is here purely for your information; it's not meant to endorse or support a particular Source plugin or indicate that we are supporting them through email and IRC.
That said, I've still been getting quite a few people emailing us to ask for access to the main "bin" folder of the server, so they can install the "SAP.dll" Source plugin (which is a different plugin from the one I mentioned above). You do not need access to the main "bin" folder of the server to install Source plugins. You can upload a plugin .dll to wherever you want on the server, as long as you put the correct pathname in the .vdf file.
The author of the "SAP" plugin makes less-than-adequate install instructions that do not talk about this.
For instance, if I were to put "SAP.dll" into the "addons" folder on the server, I would need to create a file called "SAP.vdf" in the "addons" folder as well, and make it contain this:
You should try to keep all of your plugins in the "addons" folder or subfolders of "addons" so that they are easy to keep track of. The "addons" folder is the same standard that HL used.
Again, we do not officially support these yet. If you want to install a Source plugin, that's great, but we don't officially support them. This thread is here purely for your information; it's not meant to endorse or support a particular Source plugin or indicate that we are supporting them through email and IRC.
That said, I've still been getting quite a few people emailing us to ask for access to the main "bin" folder of the server, so they can install the "SAP.dll" Source plugin (which is a different plugin from the one I mentioned above). You do not need access to the main "bin" folder of the server to install Source plugins. You can upload a plugin .dll to wherever you want on the server, as long as you put the correct pathname in the .vdf file.
The author of the "SAP" plugin makes less-than-adequate install instructions that do not talk about this.
For instance, if I were to put "SAP.dll" into the "addons" folder on the server, I would need to create a file called "SAP.vdf" in the "addons" folder as well, and make it contain this:
Code: Select all
"Plugin"
{
"file" "../cstrike/addons/sap"
}
.