Update Checker 4.2.10

13 hours ago, COVID-19 said:

[CHAOSCODE] Plugins:
PlayerRanks 2.2.0 -> 3.0.27 LINK TO DOWNLOAD -> https://chaoscode.io/resources/14/ this is wrong and not the same plugin 

This is due to the wrong resourceid, which is indicated by the developer, I will later add the ability to add a custom link to any plugin for Chaoscode

It'd be great if we could include a specific link to check for certain plugins. Sort of like a dictionary config: { "Shop": "blah.com" }. For example, there are two "Shop" on CodeFling because the actual plugins are both Shop.cs.

So, after using this for a little bit, it is great. Takes a little setup to get your plugins looking up on the correct site, but saves a ton of work when an update comes out.

There is one small issue that I've had though. If a plugin doesn't load for whatever reason, be it a rust/oxide update changed an event hook, etc, it won't be in the list to look for updates. It would be great if maybe the plugin would save a list of the current plugins and versions somewhere and when there is an update check, any plugins not found in the saved list get checked for an update and/or added to  the update report to say they weren't found. Maybe add another tab to the blacklist window to show not-found plugins and remove them from future checks/reports.

I'm a bit confused about update 2.0.6.  I looked at our server output from 2.0.5, no extra letters.  I compared the .cs files for 2.0.5 and 2.0.6 and the ONLY change is the version line.

Was something missed in the update?

10 hours ago, mughi said:

I'm a bit confused about update 2.0.6.  I looked at our server output from 2.0.5, no extra letters.  I compared the .cs files for 2.0.5 and 2.0.6 and the ONLY change is the version line.

 

Was something missed in the update?

Same. Odd there was an update for version 2.0.5 because that was already the current version. No changes. Now 2.0.6 has no new changes either.

21 hours ago, mughi said:

I'm a bit confused about update 2.0.6.  I looked at our server output from 2.0.5, no extra letters.  I compared the .cs files for 2.0.5 and 2.0.6 and the ONLY change is the version line.

 

Was something missed in the update?

11 hours ago, MadKingCraig said:

Same. Odd there was an update for version 2.0.5 because that was already the current version. No changes. Now 2.0.6 has no new changes either.

Since they created a suppoprt ticket + I had it too, I fixed it.

i cant get the web hook to work,,, exactly how should it look in the config please

15 hours ago, marc wadmore said:

i cant get the web hook to work,,, exactly how should it look in the config please

 

6 hours ago, tofurahie said:

thanks buddy

Sir, I am ecstatic at how thorough and well designed this plugin is. It beats every other option by a mile. Incredible.

Anyone looking for a complete solution for plugin update checking, THIS IS IT!

I'm starting to think it would be easier to whitelist plugins at each site rather than blacklist.  Just mathematically the amount of work is much more with blacklisting. 

I have one plugin. I will only want it to check 1 site in 100% of cases. I would have one entry under the site of choice to whitelist.

With blacklisting, I have to have 3 entries instead. 1 for each of the sites the plugin doesn't reside on. This creates a lot of management issues. Checking every list is time consuming and prone to error.

I'd love to see a whitelist added to ensure each site is only checked for the plugins that reside there along with the ability to turn off blacklisting or to leave it blank.

1 hour ago, Bumfuzzler said:

I'm starting to think it would be easier to whitelist plugins at each site rather than blacklist.  Just mathematically the amount of work is much more with blacklisting. 

I have one plugin. I will only want it to check 1 site in 100% of cases. I would have one entry under the site of choice to whitelist.

With blacklisting, I have to have 3 entries instead. 1 for each of the sites the plugin doesn't reside on. This creates a lot of management issues. Checking every list is time consuming and prone to error.

I'd love to see a whitelist added to ensure each site is only checked for the plugins that reside there along with the ability to turn off blacklisting or to leave it blank.

ok, i will add it in the next update

On 10/22/2022 at 11:11 AM, tofurahie said:

ok, i will add it in the next update

On 10/22/2022 at 9:50 AM, Bumfuzzler said:

I'm starting to think it would be easier to whitelist plugins at each site rather than blacklist.  Just mathematically the amount of work is much more with blacklisting. 

I have one plugin. I will only want it to check 1 site in 100% of cases. I would have one entry under the site of choice to whitelist.

With blacklisting, I have to have 3 entries instead. 1 for each of the sites the plugin doesn't reside on. This creates a lot of management issues. Checking every list is time consuming and prone to error.

I'd love to see a whitelist added to ensure each site is only checked for the plugins that reside there along with the ability to turn off blacklisting or to leave it blank.

For what it's worth, this is going to make it much more difficult for some of us.

We have 176 plugins.  Of them, less than 30 exist on multiple sites.  Now, instead of occasionally having to blacklist a plugin IF it starts showing up on a new site, EVERY TIME A PLUGIN IS ADDED, we will have to go add it to the whitelist.  If a plugin changes its URL for some reason, we'll have to go update the whitelist.  Our current config is 67 lines long.  The new version would be close to 3x that.

This probably should have been an option instead of a complete behavior change.  The new behavior makes this much more work intensive for servers with a lot of plugins or frequently added plugins.  And even for smaller servers, will require considerably more initial configuration than the previous design.

[edit]:  One possible compromise would be the ability to autodetect and add plugins, but I'm not sure how you'd figure out which site they came from.  

1 hour ago, mughi said:

 

For what it's worth, this is going to make it much more difficult for some of us.

We have 176 plugins.  Of them, less than 30 exist on multiple sites.  Now, instead of occasionally having to blacklist a plugin IF it starts showing up on a new site, EVERY TIME A PLUGIN IS ADDED, we will have to go add it to the whitelist.  If a plugin changes its URL for some reason, we'll have to go update the whitelist.  Our current config is 67 lines long.  The new version would be close to 3x that.

 

 

This probably should have been an option instead of a complete behavior change.  The new behavior makes this much more work intensive for servers with a lot of plugins or frequently added plugins.  And even for smaller servers, will require considerably more initial configuration than the previous design.

 

[edit]:  One possible compromise would be the ability to autodetect and add plugins, but I'm not sure how you'd figure out which site they came from.  

I'll try to think of something, you can still download the old version if it makes you so uncomfortable.

Actually, this is perfect! The emails from this site never mention updates, only forum posts The other site I use, emailing on update works great. 

So, I did the mods I have from this site and used a Discord hook for notifications.

Question: Does marking true to "Ignore new version" stop it from checking them, saving CPU usage? 

I don't understand ..wasn't the blacklisting made automatically? Why would you need to check it?

Why would you make such a drastic change to the way the plugin works to please one person? Going from an automatic system to something you have to do manually... or am I missing something?

22 hours ago, Gallorum Rex said:

Actually, this is perfect! The emails from this site never mention updates, only forum posts The other site I use, emailing on update works great. 

So, I did the mods I have from this site and used a Discord hook for notifications.

Question: Does marking true to "Ignore new version" stop it from checking them, saving CPU usage? 

If you really don't need to check any plugin, it's better to put true

18 hours ago, Don said:

I don't understand ..wasn't the blacklisting made automatically? Why would you need to check it?

Why would you make such a drastic change to the way the plugin works to please one person? Going from an automatic system to something you have to do manually... or am I missing something?

I will return the automatic search in the near future while you can use the old version if it gives you a big inconvenience

Why does the update checker keep giving me checks on the plugin "HUD"? I don't use that plugin. It is not relevant to me at all. This occurred after the update. I tried disabling it in the JSON; I set the value for "Ignore new version" to True. That didn't work. So then I ended up just deleting the block of code in the JSON for HUD. That still doesn't work. Can we resolve this?

9 hours ago, Shors Algorithm said:

Why does the update checker keep giving me checks on the plugin "HUD"? I don't use that plugin. It is not relevant to me at all. This occurred after the update. I tried disabling it in the JSON; I set the value for "Ignore new version" to True. That didn't work. So then I ended up just deleting the block of code in the JSON for HUD. That still doesn't work. Can we resolve this?

I have the same problem, I dont have a plugin that is called 'HUD' or 'Server-Hud' where it links to...

I guess iot has to do with this part in de code of the plugin, but I don't know how to code so I would not dare to change it...

 

        #region Classes 

        private class Configuration
        {
            [JsonProperty(PropertyName = "Command to open UI")]
            public string Command = "ucsetup"; 
            
            [JsonProperty(PropertyName = "Discord WebHook")]
            public string DiscrodWebHook;

            [JsonProperty(PropertyName = "Check Interval(In minutes)")]
            public int CheckMinutes = 60;

            [JsonProperty(PropertyName = "Add a link to the plugin to be updated")]
            public bool UseURL = true;

            [JsonProperty("List of plugins", ObjectCreationHandling = ObjectCreationHandling.Replace)]
            public List<PluginInfo> ListOfPlugins = new List<PluginInfo>
            {
                new PluginInfo("Hud", "2.1.10", "https://codefling.com/plugins/server-hud"),
            };
        } 

3 hours ago, Mortis said:

I have the same problem, I dont have a plugin that is called 'HUD' or 'Server-Hud' where it links to...

I guess iot has to do with this part in de code of the plugin, but I don't know how to code so I would not dare to change it...

 

        #region Classes 

        private class Configuration
        {
            [JsonProperty(PropertyName = "Command to open UI")]
            public string Command = "ucsetup"; 
            
            [JsonProperty(PropertyName = "Discord WebHook")]
            public string DiscrodWebHook;

            [JsonProperty(PropertyName = "Check Interval(In minutes)")]
            public int CheckMinutes = 60;

            [JsonProperty(PropertyName = "Add a link to the plugin to be updated")]
            public bool UseURL = true;

            [JsonProperty("List of plugins", ObjectCreationHandling = ObjectCreationHandling.Replace)]
            public List<PluginInfo> ListOfPlugins = new List<PluginInfo>
            {
                new PluginInfo("Hud", "2.1.10", "https://codefling.com/plugins/server-hud"),
            };
        } 

 

I noticed this. I know how to write code, but rather than sift through his and make changes, I decided to just revert to the older version, which works perfectly fine. He said the way his new version works is only temporary, so I'll wait it out. I recommend reverting to the older version.

@Shors Algorithm @Mortis
The Hud plugin is listed first in the config file. I'm assuming it was placed there as a way to show proper formatting. You can remove that plugin entry easily enough. It should be the first one listed after "List of plugins"

3 hours ago, RepeatPete said:

@Shors Algorithm @Mortis
The Hud plugin is listed first in the config file. I'm assuming it was placed there as a way to show proper formatting. You can remove that plugin entry easily enough. It should be the first one listed after "List of plugins"

Hey - As I said in my original message, I did that already. I deleted the entire section for the HUD plugin in the JSON. But that didn't seem to work. I'll re-upload the latest version and try it again, though. 

same here, its spamming server-hud plugin which I never had on my server, ever. not a big deal tho just kinda annoying.

10 hours ago, Shors Algorithm said:

Hey - As I said in my original message, I did that already. I deleted the entire section for the HUD plugin in the JSON. But that didn't seem to work. I'll re-upload the latest version and try it again, though. 

Working so far. Maybe I forgot to save the JSON or something when I did it last time.