Jump to content

Steenamaroo

Administrator
  • Posts

    3,697
  • Joined

  • Last visited

  • Days Won

    210

Everything posted by Steenamaroo

  1. Not really. Easiest thing to do would probably be to just back up your data file, then unload the plugin, delete the data file, then reload the plugin. If the errors go away, there is something wrong with your data file. If not then it's something else, but the data file is most likely as it isn't null checked in the code.
  2. Hi, Sounds like maybe your data file has an issue. I can add a null check to suppress the error, and should, but that won't fix the problem. Check your data file to see if it's broken or contents are null.
  3. Hi, I'll have to check that. Facepunch probably added a new type that isn't being automatically added by CustomLoot. I'll take a look today and let you know.
  4. Oh.... "A lock-on rocket is loaded..." Yeah, that'll be it ^.
  5. Hi, RustRewards has no checks or filters on distance but PlayerRanks does. It ignores kills by explosion or heat, for example, when considering kill distance, to cut out scenarios where a player has thrown a grenade then run, or TPd away. Are the kills in the feed from fire or explosions? If not, maybe this person is using explosive rounds and that's causing PlayerRanks to ignore?
  6. I'm not sure about adding that to the plugin. Seems like players would exploit it where high tier loot spawning is guaranteed. I'll DM you an alternative solution, though.
  7. I don't believe so, no, although you should double check with the author of server panel.
  8. Hi @maxalt There's an option in the Global config - Allow_Oilrigs. Sounds like you just need to set that to true. They're optional because there's no navmesh there and, so, having them as an enabled monument by default doesn't make sense, but some like to use them for stationary npcs regardless.
  9. Thank you. No, respawning is only time-based at present.
  10. Hi, Thanks for reporting. I'll have to look in to that tomorrow and see what's happening. I'll update you when I know more.
  11. Steenamaroo

    NPCKits

    Hi, What, specifically, were you looking for? Seems Facepunch have introduced a new npc type in certain areas, including the oilrig, which doesn't inherit from BasePlayer, use .userID, or use traditional inventory. Whether alternative approaches are developed in future I can't really say, but, for now, these npcs are fundamentally incompatible with NPCKits/Kits.
  12. Hi, I think you're on the wrong plugin page. This is UpdateSChecker. You're looking for UpdateChecker.
  13. Hi, Not exactly like that, no, but there are options to prevent Clan mates/Friends from contributing to PVPKills, so groups can't farm PVPKills by killing each other.
  14. Hi, I don't mark Carbon compatibility just because I don't test on Carbon myself, but if issues are reported I look in to them and, in the past, the Carbon team has made any necessary changes. That hasn't happened in some time so, realistically, everything should be good.
  15. Most likely, yes. I'll have to take a look at it, though.
  16. lol. No problem. Glad you found it and thanks for letting me know.
  17. Hi, If I had to guess, most likely a call from another plugin. If, for example, that was a BotReSpawn npc you killed, you have the choice of RustRewards managing and issuing the reward, though the value set in its UI, or BotReSpawn managing the reward through the 'RustRewardsValue' set in its own UI. It's a per-profile option under the 'Death' tab. The reason, or advantage, is that RustRewards can only see 'BotReSpawn' as one broad type, whereas using BotReSpawn UI to manage the rewards lets you have different reward values for different profiles. If both are enabled + greater than zero, you'd see two separate rewards coming through. There are other plugins which operate the same way, giving you the choice, so that's where I'd look.
  18. Hi, No worries - Thanks for the info. Are you 100% sure it's happening when killing npcs? It's a client side update error, which is kind of strange. You'd expect to see that if a player was parachuting and something went wrong, I think.
  19. Steenamaroo

    Sense Bug this wipe

    I'm really not sure what that could be. I'd have to try to replicate it to find out. With regard to the sense/assist code, there was an issue that would just prevent nearby npcs from locking on to you. A console error was possible, but there shouldn't have been any impact on behaviour, other than failing to engage.
  20. Steenamaroo

    Sense Bug this wipe

    I did find an issue. I think an object I'm addressing is maybe being disposed of sooner than it used to be. I've patched it now and all seems well. NPCs shouldn't be running to nowhere, though...Not sure what that's about. Can you tell me more?
  21. Steenamaroo

    Sense Bug this wipe

    Ok, thanks. I'll take a look now.
  22. Steenamaroo

    Sense Bug this wipe

    Hi, Is global setting NPCs_Assist_NPCs set to true?
  23. Steenamaroo

    Bot Respawn Rate

    No problem. Have fun!
  24. Steenamaroo

    Bot Respawn Rate

    Hi, Yes, every profile has a Respawn Timer (in minutes) which you can increase. You'll find it in the 'Death' tab for every profile in the /botrespawn UI.
  25. Steenamaroo

    NPC no attack

    Hi there, It sounds like you have Peacekeeper set to true for that profile. Changing it to false in the BotReSpawn Ui should solve the problem.

About Us

Codefling is the largest marketplace for plugins, maps, tools, and more, making it easy for customers to discover new content and for creators to monetize their work.

Downloads
2.4m
Total downloads
Customers
10.8k
Customers served
Files Sold
155.5k
Marketplace sales
Payments
3.3m
Processed total
×
×
  • 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.