RFC1920

I see you have debug enabled. Do you also have logging enabled when this error occurs?

Changed Status from Pending to Gremlins

Sadly, that is the state of things. It has been easily a couple of years since the game allowed it to show properly.

FWIW I will update the plugin code to simplify that call. But, since you are the only one reporting this issue I want to see if you are able to fix it on your own by validating your files first.

IPlayer is an object that is connected to all player objects (BasePlayer), at least if they are actual players and not NPCs. But, even for NPCs it would not throw a compiler error but instead might show a different error altogether if not considered as a possibility in the plugin. For it to show this error seems to imply that the game libraries don't know about that object, which is pretty weird. The best advice I can give is to validate your server files and reinstall oxide.

That's been in the plugin for at least a month or so and should still be valid and not changed this month as far as I know. player.IPlayer is used in several plugins as well. Hopefully your oxide is up to date and the right version for Windows/Linux.

Changed Status from Pending to Closed Changed Fixed In to 0.3.7

Changed Status from Pending to Closed

Changed Fixed In to Next Version

Well, it used to be that you could put wood in the top row somewhere but now wood appears to be blocked somehow? Whatever the fuel choice, it has to be to the right of whatever else you add to the recycler. You might need to change to some other currency if it won't let you add wood. For example, using fuel.lowgrade.item in the config, this will NOT work: But this WILL work:

Changed Status from Pending to Closed Changed Fixed In to Next Version

Changed Status from Pending to Closed

Changed Status from Pending to Closed

Changed Status from No Response to Closed

Ah, to NOT decay. Gotcha.

Changed Status from Pending to Closed Changed Fixed In to Next Version

I tested again and this is not what I am seeing at all. Without the nodecay permission, the overlay is not displayed. However, in cases where it is not working for whatever reason or otherwise not wanted, it will be an option in the next version. Sadly, there isn't much I can do about the resolution problem causing the overlay to be in the wrong spot.

Changed Status from Pending to No Response

Changed Status from Pending to Closed Changed Fixed In to 1.1.1

In 1.1.1, I added one additional null check to try to fix this sort of issue. Hopefully that covers it.

There is no nodecay.overlay permission, and that overlay should only appear if you have the nodecay.use permission and if the global disableWarning setting is true. The goal was to cover up the orange text that says "Your base is not protected..." What's really distressing is that the positioning is wrong for the actual overlay and that you are getting the global warning anyway (which has been disabled for months). For the questions below, please select one user and their assigned permissions, etc: Is "disableWarning" true? Is "usePermission" true? Is nodecay enabled for the user in these screenshots (did they turn it off by command)? Does the user have the nodecay.use permission, regardless of the setting of usePermission? What is the screen resolution?

Changed Status from Pending to Closed Changed Fixed In to 1.1.1

This is fixed in 1.1.1 as the target "fire" including BaseOven was present but the rule player_fire was missing.

You're right, seems the automatic check does not find them so they are special. Will take a look later today.