Report reply Maverick Posted June 13, 2020 I have a ruleset enabled to allow players to damage NPC and get an absolute ton of errors in console when they get shot. https://pastebin.com/0UgEpxhV Quote Share this comment Link to comment
Report reply Bran Posted June 13, 2020 Quote namespace Oxide.Plugins { [Info("NextGen PVE", "RFC1920", "1.0.40")] [Description("Prevent damage to players and objects in a PVE environment")] public class NextGenPVE : CovalencePlugin { #region vars private Dictionary<string, NextGenPVERule> custom_rules = new Dictionary<string, NextGenPVERule>(); // Ruleset to multiple zones private Dictionary<string, NextGenPVEZoneMap> ngpvezonemaps = new Dictionary<string, NextGenPVEZoneMap>(); private Dictionary<string, string> ngpveschedule = new Dictionary<string, string>(); private const string permNextGenPVEUse = "nextgenpve.use"; private const string permNextGenPVEAdmin = "nextgenpve.admin"; private const string permNextGenPVEGod = "nextgenpve.god"; private ConfigData configData; private SQLiteConnection sqlConnection; private string connStr; [PluginReference] private readonly Plugin ZoneManager, HumanNPC, Friends, Clans, RustIO, ZombieHorde; Replace original with this, that might help. 1 Quote Share this comment Link to comment
Report reply Maverick Posted June 13, 2020 DUDE YES. Thank you! That got rid of the errors I was having. At one point tonight there were probably over like 500 messages in a single second and it nearly crashed my server. I had to delete the plugin to prevent server crash. Thanks again man, much appreciated!! 1 Quote Share this comment Link to comment
Report reply RFC1920 Posted June 16, 2020 Bran, afaict all you have done was to add ZombieHorde to the plugin references. Hey, as long as it works. Quote Share this comment Link to comment
Report reply Maverick Posted June 16, 2020 The plugin ended up crashing my server but yeah it stops the error messages in console. Would be nice if there weren't error messages to begin with but nonetheless, seemed like it would be a good plugin. Quote Share this comment Link to comment
Report reply RFC1920 Posted June 16, 2020 If you have any of those errors I might be able to do something about it. Quote Share this comment Link to comment
Report reply Bran Posted June 16, 2020 1 minute ago, RFC1920 said: If you have any of those errors I might be able to do something about it. He posted a pastebin to the errors that were spammed in console. Quote Share this comment Link to comment
Report reply Maverick Posted June 16, 2020 Take your pick, my friend. 2800 lines of errors practically instantaneously. https://pastebin.com/TafiLdnJ Quote Share this comment Link to comment
Report reply RFC1920 Posted June 16, 2020 Were these all related to ZombieHorde or for any damage? Quote Share this comment Link to comment
Report reply Maverick Posted June 16, 2020 With that amount that quick, my assumption would be a combination of both. Quote Share this comment Link to comment
Report reply RFC1920 Posted June 16, 2020 The coincident server log (not oxide) might offer more info as well. For what it's worth, I am running this on 3 different servers including the home test machine and do not see this behavior. Quote Share this comment Link to comment
Report reply RFC1920 Posted June 16, 2020 Must be some entity for which GetType() does not work. Worst case I might have to wrap that. Quote Share this comment Link to comment
Report reply Maverick Posted June 16, 2020 I'm honestly not that great with scripting so I would be limited in my ability to help with that. I would be more than happy to test any revisions you make and let you know what happens, though. Quote Share this comment Link to comment
Report reply Maverick Posted June 16, 2020 9 minutes ago, RFC1920 said: The coincident server log (not oxide) might offer more info as well. For what it's worth, I am running this on 3 different servers including the home test machine and do not see this behavior. Just as a follow up on that, when NextGenPVE was on the server with ZombieHorde, Any zombie from ZombieHorde would generate those error messages, This does not happen when NextGenPVE is unloaded. Quote Share this comment Link to comment
Report reply RFC1920 Posted June 16, 2020 I guess I will have to spring for a copy. Quote Share this comment Link to comment
Report reply RFC1920 Posted June 16, 2020 (edited) I did. As expected, my initial testing on the home server showed no such errors. I am working with the most recent release 1.0.41 and ZH 0.2.7, but that didn't change anything as far as detection or where I thought the errors might be so far. I will keep looking when I can. Curious to see your ZH config, which you might hopefully be able to attach here. Edited June 16, 2020 by RFC1920 Quote Share this comment Link to comment
Report reply Maverick Posted June 17, 2020 For whatever reason it's not letting me submit the config using the code format. https://pastebin.com/dV0Sftb0 Quote Share this comment Link to comment
Report reply RFC1920 Posted June 17, 2020 (edited) Loaded here - of course I do not have RandomSpawns. No errors so far. Edited June 17, 2020 by RFC1920 Quote Share this comment Link to comment
Report reply Maverick Posted June 18, 2020 That's really odd that we have the exact same plugins and configs and you get no errors while I do. I'm just not going to use the plugin, it's causing far too many issues for me. Thanks for troubleshooting I guess lol Quote Share this comment Link to comment
Report reply RFC1920 Posted June 18, 2020 Well, not exact overall. If it isn't these two conflicting it could certainly be another plugin. This hook is one of the more common ones and a lot of plugins use it. Working from the case of only these two and adding others one by one might be the only way to be sure where the problem starts. Quote Share this comment Link to comment
Report reply Maverick Posted June 19, 2020 I placed only this plugin and the zombies plugin on an isolated testing server and I was still getting the errors. There were no other plugins to conflict with them. Quote Share this comment Link to comment
Report reply RFC1920 Posted June 19, 2020 Then it cannot possibly ever be explained... I guess. Quote Share this comment Link to comment
Report reply Guest Posted June 25, 2020 Changed Status from Pending to No Response Quote Share this comment Link to comment