RFC1920

Changed Status from Pending to Not a Bug

I suspect that the elevation on your custom map may be other than default. I might be able to add a Y correction value for use in these cases, but unless you knew what that number was it would be hard to set. That said, I don't think this is a bug.

I rolled back the change requiring the sandbox adjustment in 1.3.8 - no version change.

Two different sources and errors. The first may be caused by the Oxide sandbox being enabled. Either disable manually or install the DisableSandbox plugin. The second error could be a plugin conflict, but probably isn't. This particular error is what 1.3.8 was for. But, there are still issues.

You don't need to create any rules for building privilege (TC) as this is handled explicitly. When in doubt, unload the plugin and remove the config file and database then reload.

Changed Status from Work in Progress to Closed Changed Fixed In to 1.4.5

It's getting better but I am not sure when this will be done.

The whole cooldown system is a real pleasure to maintain. This needs a rework.

Please try the pre-release 1.3.8 from https://github.com/Remod-org/NextGenPVE Let me know...

Changed Status from Pending to Work in Progress

This may be a map issue so I assume it's a custom map. This is definitely not normal and nothing has changed much in the art of teleportation to cause this. (I closed your other ticket. One is enough.)

Changed Status from Pending to Closed

Changed Status from Pending to Closed Changed Fixed In to 1.4.4

This may be a map issue so I assume it's a custom map. This is definitely not normal and nothing has changed much in the art of teleportation to cause this.

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

Indeed - fix in 1.4.3.

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

Is this on /home, /bandit, /outpost? I am not seeing this.

Changed Status from Pending to Closed Changed Fixed In to 1.4.2

in 1.4.2, I fixed an issue where the object containing the timer was being removed too soon. Hopefully, that particular issue is gone now.

You can adjust warningTime in the config to avoid seeing those messages. The default is 10 and you could change that to 15 or more (100). Sounds like the server may be struggling a bit. SO MANY plugins use the same hook for managing damage including decay. I don't have access to BetterNpc or the other one to investigate further. However, you could try this edit to the plugin. Find the lines that read as follows: private object OnEntityTakeDamage(BaseCombatEntity entity, HitInfo hitInfo) { // Puts(entity.name); if (!enabled) return null; if (entity == null || hitInfo == null) return null; if (!hitInfo.damageTypes.Has(Rust.DamageType.Decay)) return null; Comment out that last line and add this new line: //if (!hitInfo.damageTypes.Has(Rust.DamageType.Decay)) return null; if (hitInfo.damageTypes.GetMajorityDamageType() != Rust.DamageType.Decay) return null; See if that helps performance any.

Changed Status from Pending to Closed Changed Fixed In to 0.4.9

If you can, try adding this around line 279 in the plugin (not config) as follows: BaseHelicopterVehicle mini = player.GetMountedVehicle() as BaseHelicopterVehicle; if (mini == null) return; // Add this line if (storedData.playerminiID.ContainsKey(player.userID) && mini.net.ID == storedData.playerminiID[player.userID]) Otherwise, wait for the next update...

Please check your config, or send it to me. It seems like you may be missing something there.

Yeah, I see now the removal code has been commented out for some reason for about 2 years. Looking.