UpdateChecker

Thank you very much!!

I see this in console, but it seems to work anyway

(09:37:30) | Missing plugin name prefix 'updatechecker.' for permission 'updater.check' (by plugin 'UpdateChecker')

 

Line 71 has this:
[Command("updates"), Permission("updater.check")]
change it to this to get rid of the message as the permission is not set in the code:
[Command("updates")]
Or we can add the permission, I will PM the the author a fix.

 

Code:

[UpdateChecker] Following plugins are missing their resourceId, and therefor cannot be checked for updates: AdminHammer, BuildingRestrictor, ClansUI, DropBlocker, IPLogger, LockOnRockets, NameFix, NoRecoil, PlaneCrash, RandomSpawns, RespawnProtection, SaveAlerter and StashBlocker[UpdateChecker] Following plugins are not accessable online at the moment, and therefor cannot be checked for updates: RustIO, Clans, AlphaLoot, DynamicCupShare, CCUpdateCheck, RemoveAAA and SkinBox[UpdateChecker] Following plugins seem to be using an inproper version name, and therefor cannot be checked for updates: BetterChat, BetterChatMute and StartupCommands[UpdateChecker] Following plugins are outdated:
# HitIcon | Installed: 1.5.6 - Latest: 1.5.7 | https://oxidemod.org/plugins/1917/

Hi, can you add something to avoid RustIO and Ch4os Code plugins like a list of exclusion?

BetterChat, BetterChatMute, StartupCommands and probably others plugins have there Oxidemod page redirected on umod.org can you do something for that?

 

It is getting very confusing with there now being three sites mods are. Many of the same folks are involved with all three sites, so it should be possible to work out a solution.

Perhaps there needs to be an indicator the [Info ] section of the plugins to know which site to go looking for them to make this cleaner? Could be as simple adding a new site indicator to the ResourceId?

Hmmm then we could have one checker for all three sites too!

 

Support for plugins on umod will be added in the next days.

 

Any chance of a universal updater that spans all three servers to make it easier on operators?

 

I can not add support for every third-party website that hosts plugins, I will think about it.

 

Yes, I agree with you on this point but in this case, would it be possible to create an exclusion list in the config file?

 

That might be a possibility.

 

Just noticed this popping up in console. Not sure if it's an issue or not?....just fyi.

Code:

[UpdateChecker] Failed to access plugin information api at [URL]http://oxide.laserhydra.com/plugins/739/[/URL] If this keeps happening, please content the developer.

 

Using the info section it should be possible to add some sort of site identifier so the two checkers (chaos and umod) can know whos plugin is from where and thus avoid unneeded messaging.

 

Will there be some mechanism that will allow an update checked to know the correct host for the plugin?

 

Many operators run plugins from more than one site. Several plugin authors publish different plugins across the three sites. The current UpdateChecker does not know where plugins are from and says it can't find them (when they are from different sites). Ideally it would just check plugins relative to its host to avoid these message.

I understand you do not want to change the info section to support this behaviour. There are a variety of alternative ways it could be handled, as long as it is consistent across plugins and sites so the updatecheckers can function consistently and accurately. It could even default to a site in the case where the indicator is missing.

Several operators I have talked to would rather the checking either be universal or not complain about plugins from other site. Thus my advocacy for them here.

 

As long as it does not keep happening constantly, that should not an issue.

 

In case it was not noticed yet, support for moved umod plugins and umod plugins with resourceid's was added (no plugin update required).

 

Thank you LaserHydra.