Ability to disable plugin management.

[Sam-Belliveau]

I like to edit the code some of the mods that are included in csgosl, however, whenever I update, it breaks all of them. Also, the checkboxes for the plugins are a bit confusing when I can manage them my self.

Would it be possible to add a button that opens the plugins folder, and maybe a checkbox for manual management?

Thanks, csgosl has been a joy to use otherwise.

[RAbuuu]

+1 for this!
Example I want to change pugsetup default setup to something that is most often used and everytime when updated, it overruns my changes :(

[lenosisnickerboa]

"Would it be possible to add a button that opens the plugins folder"
Should be simple, just one question, exactly which folder do you mean? I assume you mean the sourcemod-folder? Since from that you can reach the sourcemod/configs and sourcemod/plugins folders?

"and maybe a checkbox for manual management?"
Enabling this would mean that csgosl will not update any config files when saving config?
But when you update csgosl I guess the configs will still be overwritten with default ones, just not overwritten on every save?

[lenosisnickerboa]

UPDATE: Having looked into this I realize the second "checkbox control per mod" isn't as easy to implement as I first thought. It will require a workaround of how mods are incorporated into csgosl so that each mods config files are stored per mod, not just crammed together as today. The below will remain the wanted way to solve this but I will have to look into this further and it will require more work.

Have not received an answer. To sum it up the following features will be added (please respond if this is not what you want):

• A button to open the sourcemod folder will be added. From that you can easily find the configs and plugins folders
• A checkbox will be added to control if a plugin is managed by csgosl or not. It will prevent overwriting plugin configs AND it will prevent plugin updates (and overwriting any config files related to that plugin). If you want to update the plugin using csgosl you can temporarily enable csgosl management, save your configs, perform an update, disable csgosl management and then restore the configs.

[florinilie139]

Can you, for the love of everything in this world, make it in some way that an update on the app or server doesn't update the sourcemod? I have SM with the new syntax and every time an update happens, it breaks the smlibs cause of the older version. And the cfgs as well. I had to rename the addons folder before the update but when the client gui updated, I thought that it won't mess with the files, because is not a server update, but it did, and I was wasting time cause I couldn't compile my plugin and I didn't know where was the problem.

[lenosisnickerboa]

Sorry for not noticing your post, here goes...

What do you mean "I have SM with the new syntax"? Is this the unstable branch? I always just use the stable/latest.

I know it would be nice to have some kind of "differential update" but as I've explained before, csgosl is mainly intended for people who don't manually edit stuff. Allowing that kind of control requires a completely different packaging which I unfortunately don't have the time to implement.

In your case, wouldn't it be enough to just copy the entire addons folder outside of csgosl/server/csgo and after the update simply copy it back? Not sure I understand your setup though.

[florinilie139]

I am using SourceMod version 1.10, and the smLib updated for that version here: https://codeload.github.com/bcserv/smlib/zip/refs/heads/transitional_syntax
Every time csgosl does an update, it updates sourcemod, all the configurations are replaced with the default ones and the smlib is replaced with the one from csgosl before the transitional syntax.
Is there a way if that I disable sourcemod checkboxes in csgosl, it disables the update or the whole SM entirely?

In your case, wouldn't it be enough to just copy the entire addons folder outside of csgosl/server/csgo and after the update simply copy it back? Not sure I understand your setup though.

This is what I have been doing it since I found out this override problem, but sometimes I don't know what it triggers it