Console Errors

What do these mean and how should they be handled?

 Error fetching or processing plugin from API: Debug Missing Parent Entity
Invalid version number provided by API: null
 Error fetching or processing plugin from API: Furnace Stacks
Invalid version number provided by API: 1.02
 Error fetching or processing plugin from API: Lights On
Invalid version number provided by API: 2.1.06

https://github.com/WheteThunger/DebugMissingParentEntity

Hey, Debug Missing Parent Entity is listed on Git Hub, so we cannot get a version number from it, hence providing: null

Furnace Stacks and Lights On are not using the correct version method, it should not be, 1.02, it should be 1.0.2 or 1.2.0

https://semver.org/#spec-item-2 

Changed Status from Pending to Not a Bug

1 hour ago, Magic Services said:

Hey, Debug Missing Parent Entity is listed on Git Hub, so we cannot get a version number from it, hence providing: null

Furnace Stacks and Lights On are not using the correct version method, it should not be, 1.02, it should be 1.0.2 or 1.2.0

https://semver.org/#spec-item-2 

Isn't furance stacks ok at 1.0.5?

1 hour ago, Magic Services said:

Hey, Debug Missing Parent Entity is listed on Git Hub, so we cannot get a version number from it, hence providing: null

Furnace Stacks and Lights On are not using the correct version method, it should not be, 1.02, it should be 1.0.2 or 1.2.0

https://semver.org/#spec-item-2 

The plugin description says it supports GitHub though...

On 12/24/2024 at 3:43 AM, dustyhansen said:

Isn't furance stacks ok at 1.0.5?

Furnace stacks must be published in a few places then, because the Server API is returning 1.02, try using the overrides 

On 12/24/2024 at 3:44 AM, dustyhansen said:

The plugin description says it supports GitHub though...

There’s no version on the GitHub for us to work from, it was a description of what the Server Armour API provides

1 hour ago, Magic Services said:

Furnace stacks must be published in a few places then, because the Server API is returning 1.02, try using the overrides 

This worked, thanks!

1 hour ago, Magic Services said:

There’s no version on the GitHub for us to work from, it was a description of what the Server Armour API provides

If GitHub doesn't have version numbers and therefore you cannot verify plugins on GitHub, then you should probably remove it from your description as a supported source. 

Yes we will

23 hours ago, Magic Services said:

Furnace stacks must be published in a few places then, because the Server API is returning 1.02, try using the overrides 

I went ahead and created overrides for my plugins to point to exactly where I got them from to make sure I was getting accurate information. 

Here is what I am seeing in the console now:

 Checking for updates globally
 Checking 163 plugins for updates...
  Override not found in the API for AFDrops
  Override not found in the API for ArmoredTrain
 Error fetching or processing plugin from API: Debug Missing Parent Entity
Invalid version number provided by API: null
  Override not found in the API for LadderFlyhack
 Error fetching or processing plugin from API: Lights On
Invalid version number provided by API: 2.1.06
  Override not found in the API for PveMode
 Error fetching or processing plugin from API: RFRadio
Invalid version number provided by API: 1..2.11
  Override not found in the API for TCUpgrades
  Override not found in the API for WelcomePanel
 0 outdated plugins found
  Successfully sent to update embed channel!
  Next check in 60 minutes 

All of these have valid links provided. Any suggestions on how to clear these issues? The Debug Missing Parent Entity is the GitHub one and the Lights On is the version number issue. RFRadio has a version number issue as well. But AFDrops, ArmoredTrain, LadderFlyhack, TCUpgrades, WelcomePanel all have valid links.

The Errors for versions cannot be cleared, unless you ask the developers to use correct version numbers

The errors on overrides I want to take a look at, can you send me your overrides.json file please

11 hours ago, Magic Services said:

The Errors for versions cannot be cleared, unless you ask the developers to use correct version numbers

The errors on overrides I want to take a look at, can you send me your overrides.json file please

I sent a DM because I don't want my plugin list posted publicly.

AFDrops:

• the plugin name does not represent what it's called on codefling, so the SA API can't find it, if you search "Airfield Drops" it finds it.

ArmoredTrain

• This one is a bit more difficult, as I assume the creator used the same plugin name as the Christmas update one, so the Server Armour API isnt finding it. You need to search with the Christmas Update name, but the bot can't do this.

LadderFlyhack

• Similar issue, the plugin name does not represent what it's called on codefling, so the SA API can't find it image

Lights On

• Incorrect version usage, 2.1.06 should be 2.1.6.

PveMode

• This is listed on codefling as an extension, therefor the SA API cannot find it, as it only searches for plugins.

RFRadio

• Incorrect version usage, 1..2.11 should be 1.2.11.

TCUpgrades

• Same issue to Ladder Flyhack, the name doesn't represent what's on codefling, if you search "TC Upgrades" it finds it.

Welcome Panel:

• It is not publicly listed for sale on David's site anymore, therefor I think the Server Armour API is not picking it up. You're going to have to use the codefling url for this.

Didn't realise the edit reason was public, lol.. I was correcting my reasoning

I can report these findings and your overrides.json to the owner of Server Armour to see if he can make changes to help resolve this

6 hours ago, Magic Services said:

Didn't realise the edit reason was public, lol.. I was correcting my reasoning

I can report these findings and your overrides.json to the owner of Server Armour to see if he can make changes to help resolve this

I am a bit confused, sorry. So I thought that "name" was supposed to be the name of the plugin file and that "url" was supposed to be the link to the plugin page and that by defining these 2, the bot wouldn't have to search for anything. I am telling it plugin A is located at link B. 

Is this not the case? Why is is still searching?

If I change AFDrops to Airfield Drops, what will happen? Will it find it? Or will it not work because that is not the name of the plugin file?

I'm going to use this as an example - where you see [Info("MagicCore" - that's the plugin name that the bot sees and reports to the SA API

That name has to reflect the title of the product on any marketplace for it to find it, as far as im aware. I'm only assuming how the SA API works from testing with these names

Then what is the point of providing the direct link? If it has to search for the name AFDrops on Lone Design and can't find it, then why am I giving it a direct link to the file on Lone Design?

When you search a plugin name on the SA API it comes up with all the marketplaces it can find

If you have a direct link, it will see if it's in the result and use it

so it doesn't take whatever link i give it? it still searches at that link for a match? that is kinda frustrating, no?

is there any point on providing direct links then? or should i just put codefling.com and save myself the trouble of getting the exact url?

Unfortunately not without setting up all the scraping on the bot, which just wouldn't be nice

The direct links work perfectly when the name is similar to the product title, otherwise the SA API cant find it

As I said earlier, do you want me to report this to Pheonix I can try get a better resolution

Yes please, let's see if we can improve it for everyone.

@Pho3niX90

Found how we can resolve the inconveniences caused. We'll try out a new method for overrides in the near future.