I am seeing the following error in console after this latest Rust update:

12/09/2024 09:17:22 | Timer of 5s has failed in 'Fix Fireworks v1.1.0 by Clearshot' [callback] (Object reference not set to an instance of an object)
at void Oxide.Plugins.FixFireworks.FixFirework(BaseFirework firework) in /home/container/carbon/plugins/FixFireworks.cs:line 50
at void Oxide.Plugins.FixFireworks.OnServerInitialized()+() => { } in /home/container/carbon/plugins/FixFireworks.cs:line 37
at Timer Oxide.Plugins.Timers.Every(float time, Action action)+() => { } in /home/runner/work/Carbon/Carbon/Carbon.Core/Carbon.Components/Carbon.Common/src/Oxide/Libraries/Timer.cs:line 86

Hello, still getting this error.

> o.reload FixFireworks
Unloaded plugin Fix Fireworks v1.1.0 by Clearshot
Loaded plugin Fix Fireworks v1.1.0 by Clearshot

Bad Config? Or Maybe Bata Carbon your using as seems to have no errors with oxide? And i have heard of others using carbon where receving errors on OnServerInitialized recently Carbon is not supported by alot of plugin's and plugin devs and most will ignore errors here on UMOD home of oxide for carbon related issues.

The error does not happen when I reload the plugin, so not sure why you posted that?

The error happens in the console throughout the day.

I am not going to get into an argument about Carbon vs Oxide with you. There is no evidence that this is a Carbon issue and the config file has one setting, so it is not my config file.

{
"checkFireworksInterval": 5.0
}

dustyhansen

The error does not happen when I reload the plugin, so not sure why you posted that?

The error happens in the console throughout the day.

I am not going to get into an argument about Carbon vs Oxide with you. There is no evidence that this is a Carbon issue and the config file has one setting, so it is not my config file.

{
"checkFireworksInterval": 5.0
}

""The error does not happen when I reload the plugin, so not sure why you posted that?""
I Specified that as you did not give enuf details in your report to reproduct the error at the time.

Ran the plugin over night on oxide no errors ran it on carbon errors. sooooooooo sorry i will not post any suggestions for you to try to fix it for carbon have a nice day.

I don't know how to reproduce the error. If I did know, I would have stated that in my original post.

Keep fighting Carbon, I am sure you will win.

dustyhansen

I don't know how to reproduce the error. If I did know, I would have stated that in my original post.

Keep fighting Carbon, I am sure you will win.

Nothing to fight i could care less what you use. Just stating your on a oxide forums trying to get support for carbon server try the carbon forrms maybe?

How am I supposed to know if it is an issue with the plugin or an issue with cabon/oxide compatibility? 

dustyhansen

How am I supposed to know if it is an issue with the plugin or an issue with cabon/oxide compatibility? 

Spend some free time testing?  What would help devs out would be ways to replicate there errors if possable.