HighOnTek

I had a player earlier who says he had RP on his tugboat, and although his doors were showing protected and still are ... his tugboat took damage when he was attacked. He was quite upset about it. lol I would presume this is a bug, or are tugboats classified as a vehicle and I need to turn the false value I see in the config to true under protection settings?

I have the server rewards plugin, installed and loaded. When I enabled it in the raid protection config (set value to true) and reloaded the Raid protection plugin I receive the following message in console. I'm using the old, standard ServerRewards plugin used for almost everything found over on umod, is there another one or something it's expecting? [RaidProtection] Integration with 'ServerRewards' is set to 'true' in your configuration file, however this plugin is not installed on this server. This option will be temporarily set to 'false' to avoid issues. Once this plugin is installed, you will no longer see this warning and your configuration settings will be followed.

Looks like Dropbox will work, images are good now... location of tabs is good. All good now, you can close ticket. Thanks

Thanks can move the tabs up now... appreciate it. Will dropbox work for image hosting?

The images don't appear to download, will a fix be coming out for this soon? Also, would it be possible to add a GUI movement panel similar to the one DeathMessages (lets users toggle button to move up, down, left and right to position) uses to reposition the 2 buttons you have for upkeep and protection? I provided screenshot in the hopes it shows you the issue. They are in bad location for anyone who also uses AutoBaseUpgrade. Being able to move these around would be nice.

UPDATE: So it would appear whatever happened with yesterdays 2 oxide updates... my config Json file was somehow corrupted and was causing the issue.. Even though I unloaded, removed all DeathMessage files ... when I uploaded again I copied my backup config file with my pre-set selections. When I just did the plugin itself, and manually changed my settings back in config... all is working fine again. So if you see others having same issue, they just have to delete there config json and let oxide re-compile a new one and re-set all config selections again. You can close ticket, thanks for help.

UPDATE: So it would appear whatever happened with yesterdays 2 oxide updates... my config Json file was somehow corrupted and was causing the issue.. Even though I unloaded, removed all DeathMessage files ... when I uploaded again I copied my backup config file with my pre-set selections. When I just did the plugin itself, and manually changed my settings back in config... all is working fine again. So if you see others having same issue, they just have to delete there config json and let oxide re-compile a new one and re-set all config selections again. You can close ticket, thanks for help.

I ran oxide.version and this is my readout, this looks correct and should be the most up to date version. Oxide.Rust Version: 2.0.6002 Are you testing on Windows, or Linux ... I have found in the past sometimes plugins work on Windows, but not Linux or vice verse. The two oxide updates may be the same version, but they are separate instances based on OS of server. My servers are Linux based.

I unloaded Death Message from 2 different servers, both servers run different plugins ... I even tested it on a TEST server with 0 plugins to confirm it just wasn't conflicting with something... still has issues. Fallback handler could not load library /home/rust/server/RustDedicated_Data/MonoBleedingEdge/x86_64/data-0x55889e82fd10.so Failed to call hook 'OnServerInitialized' on plugin 'DeathMessage v1.0.9' (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.DeathMessage.OnServerInitialized () [0x00006] in <7a56aaa7ea1542e6911088e56d6849e9>:0 at Oxide.Plugins.DeathMessage.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x002ab] in <7a56aaa7ea1542e6911088e56d6849e9>:0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <753b27d02c104b8d8166056be06d5c55>:0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 Loaded plugin DeathMessage v1.0.9 by Damo/beee Unloaded plugin DeathMessage v1.0.9 by Damo/beee Failed to call hook 'OnServerInitialized' on plugin 'DeathMessage v1.0.9' (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.DeathMessage.OnServerInitialized () [0x00006] in <7a56aaa7ea1542e6911088e56d6849e9>:0 at Oxide.Plugins.DeathMessage.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x002ab] in <7a56aaa7ea1542e6911088e56d6849e9>:0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <753b27d02c104b8d8166056be06d5c55>:0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 Loaded plugin DeathMessage v1.0.9 by Damo/beee

According to others, Death Notes the free version similar to this is also apparently broken, something to do with the latest update from oxide. I'll re-apply the plugin and see if this resolves, and report back.

Deathmessage appears to have stopped working after today's update... this is what I get in console now as I attempt to reload it. DeathMessage was compiled successfully in 6227ms Unloaded plugin DeathMessage v1.0.9 by Damo/beee Fallback handler could not load library /home/rust/server/RustDedicated_Data/MonoBleedingEdge/x86_64/data-0x55889cbb7bc0.so Failed to call hook 'OnServerInitialized' on plugin 'DeathMessage v1.0.9' (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.DeathMessage.OnServerInitialized () [0x00006] in <772a45334f3140439f864003c4300234>:0 at Oxide.Plugins.DeathMessage.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x002ab] in <772a45334f3140439f864003c4300234>:0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <753b27d02c104b8d8166056be06d5c55>:0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 Loaded plugin DeathMessage v1.0.9 by Damo/beee

Open the .cs file replace the image links with the following, and it will work... I simply used the images available already from Rustlabs. new ImageSettings { Name = "wood", Url = "https://rustlabs.com/img/items180/wood.png" }, new ImageSettings { Name = "stones", Url = "https://rustlabs.com/img/items180/stones.png" }, new ImageSettings { Name = "metal.fragments", Url = "https://rustlabs.com/img/items180/metal.fragments.png" }, new ImageSettings { Name = "metal.refined", Url = "https://rustlabs.com/img/items180/metal.refined.png"

Absolutely love the map. I notice in console though I am getting this error over and over, even though its working. Any idea what would be causing this? Failed to create agent because it is not close enough to the NavMesh (Filename: Line: 648) Failed to create agent because it is not close enough to the NavMesh (Filename: Line: 648) Failed to create agent because it is not close enough to the NavMesh (Filename: Line: 648) Failed to create agent because it is not close enough to the NavMesh (Filename: Line: 648) Failed to create agent because it is not close enough to the NavMesh (Filename: Line: 648)

Disregard the NPC Death, it looks like it shows monument NPC deaths... but not some random scientist found on side of the road. Most likely intentional I guess. But please consider my suggestion about adding environmental deaths, cold, drowning, falling etc. Keep up the good work.

I disabled reporting for animal kills as seen below, and it also disabled NPC reports, both in-game and in-discord. Not that it matters, I was going to disable NPC anyways. But thought you should know, why separate the two if they're treated as one and the same? Also, I notice deaths by environment deaths like falling & drowning are not reported. Any plans to add these in the future? "⟪ Global Messages settings": { "Enable About Animal": false, "Enable About Entitys": true, "Enable About NPC": true, "Enable Player Deaths": true "⟪ Discord settings": { "Webhook URL": "https://discord.com/api/webhooks/PRIVATESTRING", "Bot Name": "Death Message Bot", "Bot Avatar Link": "https://avatarfiles.alphacoders.com/128/128573.png", "Enable Animal Deaths": false, "Enable Entities Deaths": true, "Enable NPC Deaths": true, "Enable Player Deaths": true