Beast failing to spawn even after reboot

Hello, we arent seeing the beast spawn and are receiving this message. Can you advise?

Failed to call hook 'OnEntitySpawned' on plugin 'LegendaryBeasts v1.1.3' (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.LegendaryBeasts.CreateLegendaryBeast (BaseEntity entity, Oxide.Plugins.LegendaryBeasts+LegendaryBeastConfig selectedLegendaryBeastConfig) [0x0013a] in <4b1de49174ac49bb9b2899aafe46fa29>:0 at Oxide.Plugins.LegendaryBeasts.OnEntitySpawned (BaseNetworkable entity) [0x000a1] in <4b1de49174ac49bb9b2899aafe46fa29>:0 at Oxide.Plugins.LegendaryBeasts.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x009f5] in <4b1de49174ac49bb9b2899aafe46fa29>:0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in :0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <46ff2b534abb4b35952608167523b7ec>:0 at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <46ff2b534abb4b35952608167523b7ec>:0

Sorry about this, please could you share your configuration files for the plugin. I'm looking to have an update out this evening to fix this. If possible I'll try it out with your configuration before just to make sure everything's working correctly .

On 6/5/2022 at 3:26 PM, GuestMods said:

Sorry about this, please could you share your configuration files for the plugin. I'm looking to have an update out this evening to fix this. If possible I'll try it out with your configuration before just to make sure everything's working correctly .

Thanks for getting back to me, however it seems you shared the source file for the plugin, please could you amend you post to remove the plugin attachment and upload your LegendaryBeasts.json configuration file.

7 hours ago, GuestMods said:

Thanks for getting back to me, however it seems you shared the source file for the plugin, please could you amend you post to remove the plugin attachment and upload your LegendaryBeasts.json configuration file.

Oops, here you go

LegendaryBeasts.json

already uploaded them to the other support thread....

Thank you for your patience, with your configuration I was able to reproduce the error on my end. With a previous update a new feature was added to enable configuration of beast map markers. The error is caused when there are no configuration settings for the map marker present in the configuration file. The latest version 1.1.4 should fix this issue and correctly use default settings for the map markers. I do encourage you to check the default configuration on the plugin page to see an example of how you can customise the map marker just in case you might prefer something other than the default settings. Please let me know if you have any more issues and I apologise again for the inconvenience.

Changed Status from Pending to Closed

Changed Fixed In to 1.1.4