RFC1920

Changed Status from Pending to Closed Changed Fixed In to 1.0.67

That's 43 seconds! I am sure that it's not the fault of this plugin but something going on with your server in general or it's plugins. You could make sure to set killOnSleep to false in the config to bypass all that gets done by this plugin in OnPlayerDisconnected. This was automatically closed, btw, because I missed it.

Just curious whether the player names being shared to had spaces in them.

Posted an update for this as well.

Please see the video I posted this morning in the plug in description.

Are you using a computer station to control it? That is the only way at this point.

Surely this would have been noticed by now so I am sure it works. Did you have some other copy of MyMiniCopter, perhaps customized, which was also installed?

Auto-closed. Found that the documentation was missing for some reason.

Documentation was missing somehow...

Changed Status from Pending to Closed Changed Fixed In to 1.0.1

Changed Status from Pending to Closed

Changed Status from Pending to Not a Bug

You do also have the option to learn sql and enter things that way

Yes, it's not super simple to operate mainly because Cui is so horrible. But, it is possible.

Seems that the type for both is MiningQuarry. Note that you must hit enter on each and every text entry field in any form for that value to be saved. Cui is fairly troublesome, and this is one of its weakest spots. [pro-tip: Pasting can avoid a lot of the typical issues with Cui where entry is interrupted by some other game function. This way you can enter an entire word without being interrupted. Type the word you want in a text editor or any other window on your machine. Copy it. Go to an entry field and paste. ENTER or RETURN to save. ] First, make sure "AllowCustomEdit": true, is set in the config. If necessary, change that and reload the plugin. In the GUI, click on the Rule/Ent Editor button. Click on the Unknown Entities button. Click on MiningQuarry. If not present, someone has already added it to a collection. If that is the case, there is an All Entities button where you can search for it. Click to the right of New Collection where you should see the word new. Type a name, e.g. quarry and hit enter (see our tip above). Close the Entity Select window, which should now NOT show the MiningQuarry. Click on the Rule/Ent Editor button again. Click on the Custom Rules button. Click Add. Enter a valid name such as player_quarry. It is typically a good idea to make sure that the rule name, e .g. source_target, matches the rule source and target values. The source and target values are collection names, e.g. player, npc. Description is optional, and leave damage as True. For source, type (or paste) the word player. The word player matches the built-in collection player which includes BasePlayer. For target, type (or paste) the word quarry. The word quarry matches the collection name we entered earlier. Repeat #3 as desired for other damage sources, e.g. helicopter, npc, etc. Now that MiningQuarry is in a collection (quarry), it should no longer be included in any default action. So, for the default ruleset it should be excluded already. You can verify that your rule appears by clicking on any of the Allow rules in the default or any other ruleset. If desired, you can select that rule (player_quarry, etc.)

If you enable the log with the command pvelog, that will create a log file under oxide/logs/NextGenPVE. Enable it and attack whatever object you want to control. The name you see in the log file for ____ attacking SOMETHING is what you can then add to a rule. Type pvelog again to disable the log. Once my server is up this morning, I'll take a look.

I have not heard this complaint before, and I also use the plugin and have not run into this. Do you have any associated error messages?

I went ahead and made a simple plugin to manage targeting for SAM Sites. It currently handles player or server-owned SAM Site targeting of NPCs, players, and animals. NextGenPVE can now call out to it: SAM Targeting. Note that if loaded, NextGen shows it's settings in global flags.

Those wouldn't be flags, although SAM site targeting would have to be modded by another plugin for targeting. For damage, you should be able to add SAMSite to the traps entity group if they aren't in there already. Turret targeting and damage should already be a feature of the plugin.

I had not seen that yet but if you don't mind trying this link maybe it will help.

From the couch that looks like some other version of NoDecay.

Curious who did this for you? I only see one message call along with all of the other questionable mods.

Possible that you were impacted by a bug in versions before 1.0.78.

Please enable the log using /pvelog and let's see what it shows when those errors pop up. Basically: 1. Type /pvelog in chat 2. Watch for the console errors. 3. Type /pvelog again. 4. Copy contents or paste enough here to see of oxide/logs/NextGenPVE/nextgenpve_log-DATESTRING.txt. I want to see what is happening in that log when you are seeing those errors. It will tell me what it thinks was attacking what if it was able to see at all.