[TnTSCS]

just make sure you add notes to your updates letting them know there are new CVars... in the updater log, those notes will show up

[sinsic]

Originally Posted by TnTSCS just make sure you add notes to your updates letting them know there are new CVars... in the updater log, those notes will show up

that's my point, they will have to check logs to see updates..
Obviously, thats what I'm doing right now but as I said before it would be a nice upgrade for this plugin to simply compare the user cfg and updated cfg and add the missing cvars to user cfg..

Before I started writing plugins, I had no idea about this so I wasn't checking anything.. I just left the plugins with updater support to auto updater and didn't bother to look even in logs unless something was wrong with my server or a plugin. I managed everything with ftp, sm_rcon and panel which doesn't show anything about updates unless you happen to think "what a beautiful morning, lets check update logs"

Ofcourse this is just me and maybe not everyone is as ignorant as me

Don't get me wrong I understand what I need to do and this plugin is already awesome as it is..

[GoD-Tony]

Originally Posted by sinsic that's my point, they will have to check logs to see updates..

Regardless of all that, newly added cvars after an official release should already be set to the most ideal setting, or mimic the behaviour of the previous version by default. Then when your users notice that new config options are available, they can begin to customize it themselves on their own time.

You don't want to push an update that will basically force servers ops to immediately perform some kind of config maintenance.

[sinsic]

Originally Posted by GoD-Tony Regardless of all that, newly added cvars after an official release should already be set to the most ideal setting, or mimic the behavior of the previous version by default. Then when your users notice that new config options are available, they can begin to customize it themselves on their own time. You don't want to push an update that will basically force servers ops to immediately perform some kind of config maintenance.

Well if new cvars will mimic the old behavior then they won't be needing to do a config maintenance immediately.

But when they see the update, they won't need to get the new cfg and change old cvars to their values one by one either. (I said one by one because you can't just copy old cvars and past them to new CFG. Cvars get arranged by their names so old ones won't be at the top of cfg, new and old cvars will be mixed.)

I only wrote simple plugins so have no idea if what I'm saying is simple, hard or impossible. But from the replies I'm getting, it seems it's either a stupid idea or an impossible one so I'll shut up now