Jump to content

API Non Null

Pending 1.1.1

Hi! Great plugin, everything's working well on my end, just one little conflict with another plugin I'm utilizing for it's NPC Loadouts.

I'm Using Raidable Bases by Nivex: Looking to make sure the defined loadouts for these NPCs aren't being overwritten by NPCKits.

I see the tag about the API needing to "return non null" - Not sure what this means as I haven't played with API stuff at all with any of our plugins. Can you help me out with this? Assuming it's the ticket to resolving the conflict I'm seeing. 😄 

Share this comment


Link to comment

non null just means any object which isn't null.
The convention is to use 'true'.

Nivex will know that, though - He could add the NPCKits api to his plugin, to prevent his npcs being given kits.

  • Like 1

Share this comment


Link to comment

Copy! I'll relay it over to Nivex's territory and see what we come up with.  

In the end it comes down to who's plugin loads 2nd. If RaidableBases comes in 2nd, everything works great except we get some double loot spawning action on deaths. whereas if NPCKits comes 2nd, we overwrite the spawned loot intended. - Either way it's a conflict, but it's cool to see different results XD

Share this comment


Link to comment

Nivex has the two working together now! Now the kits designed for each difficulty in Raidable Bases can be manually configured while still having NPC Kits functioning on all other NPCs without conflicts.

  • Like 1

Share this comment


Link to comment
350.5k

Downloads

Total number of downloads.

1.8k

Customers

Total customers served.

24k

Files Sold

Total number of files sold.

373.8k

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.