Unsupported decaying entity detectedFixed
ALANMAN

I tried this and got this error

Error while compiling: NoDecay.cs(389,41): error CS1501: No overload for method `Scale' takes `3' arguments

I'm getting a very similiar error. Mines"[Error] Error while compiling: NoDecay.cs(382,26): error CS1501: No overload for method `Scale' takes `3' arguments". Tried both Hoskin's fix and Substrata's fix. Let me know if you get yours fixed since we're in the same boat. I'll let you know if I find anything too.

If it's not working for you - Listen to @SubtleSara and what I have posted previously. We ARE lucky to have a fix in the first place - if it's not working it's PROBABLY SOMETHING YOU FUCKED UP in the spacing/formatting when editing. Thanks again @Hoskins and whoever else posted the same fix! It also might be in your best interest to restore your server's file system from fresh (you should do this at force wipe anyway) before trying, to remove any files that might cause a conflict. Cheers.
5efeb2e21df47.png GreasyGunz
If it's not working for you - Listen to @SubtleSara and what I have posted previously. We ARE lucky to have a fix in the first place - if it's not working it's PROBABLY SOMETHING YOU FUCKED UP in the spacing/formatting when editing. Thanks again @Hoskins and whoever else posted the same fix! It also might be in your best interest to restore your server's file system from fresh before trying, to remove any files that might cause a conflict. Cheers.

I ran it through a json checker and it does check out, so I'm not sure what the error is referring to. The (389,41) on mine and (382,26) on Lightning's error referrs to the line and column where the error happens, but it isn't obvious to me what the error means. If someone could post a link to a working file or pastebin, that would be great. I'm not sure if that's allowed here though. I have checked and double checked my file, even recreated it and I receive the same error.

I mean wipe your entire server's file system and reinstall it. Not just the plugin files. Then quadruple check that you have edited and formatted your plugin file properly, and install it first before any others on a fresh server file system.
ALANMAN

I ran it through a json checker and it does check out, so I'm not sure what the error is referring to. The (389,41) on mine and (382,26) on Lightning's error referrs to the line and column where the error happens, but it isn't obvious to me what the error means. If someone could post a link to a working file or pastebin, that would be great. I'm not sure if that's allowed here though. I have checked and double checked my file, even recreated it and I receive the same error.

Okay, so I decided to try once more and got the same error message. What I didn't realize is there are two different posts by two different users suggesting fixes on page 6. 1 is from Substrata, which is the one I was following. This fix does not work for me, and gives the error I mentioned. I then followed Hoskins post, which is after Substrata's on page 6 and the error messages have gone away. Previously I mentioned that I thought I had fixed it, then edited my post saying it came back within 5 mintues of a restart. So I started a timer, and I'm at 10 minutes since I reloaded the plugin. If it does come back I'll edit this post. Otherwise this should be fixed for me. Hope that helps.Also @GreasyGunz don't be so quick to asume we are fucking up. If anything Substrata should remove their first "fix" post as it isn't working for some users. I was not pointing fingers at anyone, and was here to simply report my findings, get help, and now am back to help others with my findings.
5efeb2e21df47.png GreasyGunz
I mean wipe your entire server's file system and reinstall it. Not just the plugin files. Then quadruple check that you have edited and formatted your plugin file properly, and install it first before any others on a fresh server file system.

This laughable at best. I'm not wiping my entire server for a json error.

Lightning
Okay, so I decided to try once more and got the same error message. What I didn't realize is there are two different posts by two different users suggesting fixes on page 6. 1 is from Substrata, which is the one I was following. This fix does not work for me, and gives the error I mentioned. I then followed Hoskins post, which is after Substrata's on page 6 and the error messages have gone away. Previously I mentioned that I thought I had fixed it, then edited my post saying it came back within 5 mintues of a restart. So I started a timer, and I'm at 10 minutes since I reloaded the plugin. If it does come back I'll edit this post. Otherwise this should be fixed for me. Hope that helps. Also @GreasyGunz don't be so quick to asume we are fucking up. If anything Substrata should remove their first "fix" post as it isn't working for some users. I was not pointing fingers at anyone, and was here to simply report my findings, get help, and now am back to help others with my findings.

This is also what I understood to do, but I may have made an error in the syntax. Thanks for the update, I'll give it another shot.

ALANMAN

This is also what I understood to do, but I may have made an error in the syntax. Thanks for the update, I'll give it another shot.

If you can't get it working, I'll screen grab a gif file of me making the needed changes and post a link. We're not allowed to share files for security reasons.

Edit: Here's a screen recording: https://i.imgur.com/jMfSGSJ.gif

Not sure if it's illegal or anything here, but I can send my custom .cs file if anyone wants it. PM me or something.
ALANMAN

This laughable at best. I'm not wiping my entire server for a json error.

You should be deleteing and reinstalling your server files from fresh every force update ANYWAY. But a few days into the wipe - I wouldn't if I were you either. I would just do without the plugin for now or until a plugin update - and use "decay.upkeep false" and tell your players to keep shit in their TC until then, or until you figure it out. Sorry nothing worked for you homie.

Merged post

@Lightning I'm not assuming anything at all, I'm just saying it's very easy to have one space in the wrong place with those file edits, and that's all it takes... and to look at it closely is all I meant, thanks.

[NoDecay] Unsupported decaying entity detected: 1module_cockpit_with_engine --- please notify author

[NoDecay] Unsupported decaying entity detected: 1module_flatbed --- please notify author

[NoDecay] Unsupported decaying entity detected: 1module_engine --- please notify author

[NoDecay] Unsupported decaying entity detected: 1module_engine --- please notify author

[NoDecay] Unsupported decaying entity detected: 1module_cockpit --- please notify author

scare Z. Collins[7392666] was killed by Parizer[76561198203770392]

[NoDecay] Unsupported decaying entity detected: 1module_cockpit_with_engine --- please notify author

[NoDecay] Unsupported decaying entity detected: 1module_rear_seats --- please notify author

[NoDecay] Unsupported decaying entity detected: 1module_storage --- please notify author

[NoDecay] Unsupported decaying entity detected: 1module_engine --- please notify author

Please note that we do not allow random versions of plugins to be posted in threads. The plugin has been marked as abandoned though should a developer wish to maintain it. For sharing custom modifications as a whole plugin, please use PM.
New Update coming today <3
help me the plugin returns an error

Failed to run a 0.05 timer in 'NoDecay v2.0.0' (NullReferenceException: )
at (wrapper managed-to-native) UnityEngine.Component.GetComponentFastPath(UnityEngine.Component,System.Type,intptr)
at UnityEngine.Component.GetComponent[T] () [0x00021] in <0618f269b594493b97c56ba78f03373a>:0
at Oxide.Plugins.NoDecay+<CanMoveItem>c__AnonStorey3.<>m__0 () [0x00028] in <9d7f8da20fba4dc9a474089e26a56539>:0
out
at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <cf88a28c7fb44d36890d85a78331cc9d>:0
[NoDecay] Unsupported decaying entity detected: car_chassis_2module.entity --- please notify author.

Latest Update
Locked automatically