Suggestions to SourceMM Plugin Dev's
 

Okay, I already re-organized my Fakeclients installation to follow this, but a while back a bunch of the lead developers of HLDS and HL1 plugin developers (AdminMod, AMX, AMXX (I think), and United Admins) all decided to have a standard. I'm proposing this standard be followed in HL2 plugins and SourceMM Plugins. So, I'll lay it out simply and include Metamod: Source w/ it's files.

See attached file.

I'm laying this out for mod developers so that we (the server administrators) can keep the plugins organized, this is also a shout out to those other straight Source plugin developers (mattie, beetle, xad, Roger Devil, and mani) to organize their files for configs data and all that.

Please SOMEBODY listen to this...I was so happy when this standard was set in place in HL1.

There could be some modifications set in place (but exec can't use .. for some reason in Source so cfg files gotta say within the cfg directory structure, but I'm pretty sure the rest can be organized better)

From the Metamod: Source readme files on how to install a plugin it seems almost like SourceMod is already following this directory structure setup. (Once it's done we'll see), but from what I can see it looks it. So PLEASE keep stuff organized for us...

Also note, this could still be modified, there are plenty of ways to do it, but at least give us something easier to work with.

This is a good idea, but I have a few revisions:

Plugin name: <plugin>
Configs: addons/<plugin>/config or simply in addons/<plugin>/ if one config file
SourceMM Binaries: addons/<plugin>/bin/<plugin>_mm

As you can see, I prefer plugins to be completely isolated to their addons folder if possible. This makes them easily transferable to other setups/servers.

The only real problem is that I can't seem to execute any cfgs outside of the cfg folder. so unless there's some scripted execute command it doesn't seem possible to exec it as a server admin...not not nice like that :(. Maybe build a function like this into metamod? :) meta exec might be useful...

but I'll put in those revisions.

How's that look?

I'll write out some better documentation on it later soon as bailopan approves of the latest revision, granted it'd be short documentation but it's docs nonetheless. Really not much else than that quote need be said, but still...

I attached a little "documentation" to this post.

Edit: the documentation I wrote has been updated.

Edit: Edit to the documentation I wrote again (credits :))

So does anybody else think a standard like this should be set in place?

It's not a bad idea at all. I'll rearrange the directory structure on updates to my existing plugins and change the VIP plugin to use that layout also.

EDIT: I believe models and sounds have to be in the their respective directories and won't work in the "addons" directory, but I'll change the rest.

Like I said, it can be "played around" with. :)
The txt file of my post before the last one is the most recent revision.

I dunno about sounds/models...if the plugin calls the sounds they could possibly be anywhere right? Oh well, I'll look more into it as best I can (not a coder myself.) Unless the call function is based around the sounds directory, and if it is, I'll revise it to be more friendly to that. Soon as this is information is confirmed I'll edit it.

I'll update it as people tell me what can and can't be done ;)

I changed around my first post a bit to include the txt file.

Updated the txt to follow what Lduke has stated (I came to realize it'd be best this way because it matches both client and server side when it comes to models/sounds.

I kinda think this should be stickied...or moved to where it would be in it's proper location and THEN stickied.

What's the difference between a config and an ini?

I think "config" should be renamed to "configs" (plural) or "cfg" (to mimic sourceds).

If we're going to make a standard, I'm going to nitpick it ;)