RFC1920

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.

1.0.69 introduces some new code to try to actually handle horse decay. It seems they run in a separate loop as far as I can tell, so we try to adjust their decay by setting their nextdecaytime on spawn and at start based on the value of the horse multiplier.

It should only damage the building if the owner was the one being targeted. So, baiting should not work. Yes, the heli will otherwise damage buildings.

Need to know what is triggering this since literally everything hits this function. If possible, enable logging around the time of the error.

Those fall under the deployables category, so make sure you have "deployables": 1.0, in the config file.

That last image should do it.

I had to look because it has been awhile. But I did add in one of the upgrades an elevator_player rule. I believe this is enabled in the default ruleset. Try deselecting that if enabled. This should include only player-built elevators so that dying in the launch site elevators, etc. would still be a thing.

Changed Status from Pending to Closed Changed Fixed In to 1.0.91

Enable player_trap in the default ruleset. I am pushing a patch to make that the default because it has become a FAQ.

Trying running /pveupdate. That should populate the list with any/all unassigned entities. Normally, this would run at wipe to pickup new entities. Or, select All Entities instead and perhaps they are listed there for searching.