[xm3kilo]

What's the weight of doing this? I've got about 20 plugins that I want to condense into one big plugin. They all use the same sort of event hooks, would it be better to include everything into one big event for each hook? Or will this cause overhead?

Just want to make everything more optimised

EDIT: The plugins are basically modules of the same overall thing

Cheers!

[klippy]

You're spending time by combining plugins into one, you won't notice any difference and is MUCH more prone to errors and less maintainable.

[headline]

You won’t notice any performance difference. There’s a few reasons why people build large plugins in a module-based format, but the most significant reason in my opinion is that if one part of a sub module failed or was unloaded: it won’t take down your entire mod.

The other reason is that it makes certain features easy to disable. If you don’t want time rankings, remove timer-rankings.smx.

Regardless of these reasons, it’s not going to be worth your time to combine them.

[xm3kilo]

Ah okay, thanks everyone. Is started doing it before I read these comments and I realised I was losing track of what I was looking for etc and went fk me, this is probably not worth it.

So, thanks!

[Powerlord]

Originally Posted by Headline You won’t notice any performance difference. There’s a few reasons why people build large plugins in a module-based format, but the most significant reason in my opinion is that if one part of a sub module failed or was unloaded: it won’t take down your entire mod. The other reason is that it makes certain features easy to disable. If you don’t want time rankings, remove timer-rankings.smx. Regardless of these reasons, it’s not going to be worth your time to combine them.

Some of the other common reasons to break a large plugin into a modular system:

• Some parts of the plugin can be encapsulated to make them optional components.
  • You can see this in SourceMod's map voting plugins. mapchooser is the main plugin, rockthevote and nominations are optional components that exist in separate plugins.
• The main plugin has parts you can switch out, such as
  • Game-specific modules / overrides
  • Storage engines

Overrides came to mind because back when I was still heavily involved in writing SourceMod plugins, I had two plugins that I was working on (one new, one a rewrite/restructure) that were going to use them.

[pcmaster]

Personally, I also prefer having smaller sub-modules instead of one enormous plugin, makes maintenance/finding things again easier.

[_GamerX]

One big or plugin with sub-plugins but never put on server e.g. 50+ plugins this making server so bad...