RFC1920

Changed Status from Pending to Closed

Ok, so is it working now?

Changed Status from Pending to Closed Changed Fixed In to 1.3.4

Changed Status from Pending to Closed Changed Fixed In to 1.3.4

Yes, something broke. Looking into it.

Just to verify, make sure the rules are all lower case, e.g. player_building. I'm not sure about that plugin, but if it is free I can check into it. Otherwise, perhaps there is a hook I could call to check. Ideally, it should be that plugin that manages the damage. I can't possibly add every new plugin in here as a check as it would be TOO much to check on EVERY damage attempt, because that is the reality of how it would have to work.

This is (now being) caused by line 1587, which reads: sphereCollider.tag = "FlyingCarpet"; You can comment it out: //sphereCollider.tag = "FlyingCarpet"; I don't think this will cause problems.

Actually, I just saw this while porting it to a different plugin framework. The carpet spawns but this message appears in console. Will be looking into it, although it's possibly harmless.

Not sure. I cannot duplicate that. Make sure you are running the most current version from here.

The best way to know what is happening is: 1. Enable debug using the "nodecay log" command (add slash in chat). 2. Set decay tick, e.g. using "decay.tick 30" in console (not chat). Before doing that, run "decay.tick" to see your current setting - should be 600 by default. 3. Messages should be logged to the oxide log for all decaying items. 4. Set decay tick back to normal using "decay.tick 600" 5. Run "nodecay log" again to disable logging. 6. Send me the relevant logging or at least a portion of it showing the decay operations on blocks, doors/windows, etc. Ultimately, they should show a before value > 0 and then an after value of 0, as long as some other plugin or server setting is getting in our way. Again, if there are materials in the cupboard that would protect the building or parts, this will happen without NoDecay being able to intervene.

Changed Status from Pending to Can't Reproduce

Can you run /lp log (or lp log in console) to get some logging around the same time this may be happening?

Changed Status from Pending to Closed Changed Fixed In to 1.3.4

With materials in the TC that match the base grade(s), the plugin is skipped altogether.

Other than not needing the Multipliers section this looks fine. It shouldn't interfere with anything, but what's the problem?

Changed Status from Pending to Can't Reproduce

I just looked and I do see the electrical branch on the right side of the fridge (when facing the front), and I was able to connect a generator to the Power In connection.

Switches should not be in the default config. If they are in there and set to true, then they would have to be shared. /lp log as admin to enable logging.

These are a complete mystery unless I can see what else was happening around the same time with the log enabled on NextGenPVE. FWIW, the two traces above are similar but different. @Ondraasek, please update to 1.3.2 and let me know if that goes away. @HowlingWolf, are you running RaidableBases or DynamicPVP, HumanNPC/Humanoids, etc.?

Changed Status from Pending to Closed Changed Fixed In to 0.4.6

0.4.6 should now unlock the copter(s) of players with unlimited permission if allowFuelIfUnlimited is true. It also prevents adding fuel on every plugin reload since the point was to add 1 fuel with zero consumption just to keep it flying. The server restart fuel consumption thing has always been a problem. The easiest workaround is to nomini/mymini to create a new copter until I find a nice way to handle this.

I think so. We're both set false?

Do you have this in your config? "requireCupboard": true, "cupboardCheckEntity": true,

About to release 1.3.2 partially to test a theory about that. It doesn't happen that often on my server so it was harder to track down.

Changed Status from Pending to Closed (Bad docs, sorry)