Jump to content

MON@H

Creator
  • Posts

    406
  • Joined

Support Replies posted by MON@H

  1. The cause lies in something within your environment: another plugin, an extension, or a custom DLL. As previously mentioned, carbon was reported buggy and then fixed couple times. As soon as you explain to me how to reproduce the problem, I will fix the plugin if the issue lies there; but if the problem is external, how am I supposed to fix it?

  2. I cannot fix a problem that cannot be reproduced. Please provide the specific circumstances that allow the problem to be reproduced.

    @Teastick note that furnaces and legacy furnaces are different items from Rust perspective; unless you group them together, the limit won't be applied.

        {
          "Group name": "Furnaces",
          "Group Entities list": [
            "assets/prefabs/deployable/furnace/furnace.prefab",
            "assets/prefabs/deployable/legacyfurnace/legacy_furnace.prefab"
          ]
        }

     

  3. Why are your groups empty? Have you tried deleting them? If so, you can't use them in the "Limits Entities" lists because they don't exist (they weren't created by the plugin). Therefore, you can't use, for example, "TC"; you can only use Rust prefabs.

    LimitEntities.json

  4. How exactly are you 

    3 hours ago, Super Xero said:

    picking it back up

    Using vanilla hammer or some custom plugin? In any case the plugin itself is not an issue. Try it on server without any other plugins and you'll see it's working just as expected. Most likely you have a custom plugin that preventing / avoiding to call OnEntityKill hook, which vanilla Rust does when destroying any entity and this plugin depends on it.

  5. Attach your config. Have you tried to reload the plugin? Also you may want to set "Log Level (Debug, Info, Warning, Error, Off)": "Debug" then reload plugin and see more details in log file in /oxide/logs/LimitEntities

  6. As I mentioned before, this plugin doesn't control the behavior of other plugins in any way. It works straightforwardly, preventing the creation of entitis above the limit. This plugin is using "CanBuild" hook and returns "false" to block entity creation. However, any plugin can create an entity while ignoring this hook. So, it's a matter of whether the developer wants to allow other plugins to prevent creation first. If so, they need to monitor this hook and not create entities if CanBuild returns false. If the developer doesn't want to monitor anything, they simply create the entity. We've already discussed this here right? Nothing has changed since then.

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
3.2m
Total downloads
Customers
12.3k
Customers served
Files Sold
174.8k
Total sales
Payments
3.8m
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.