Jump to content

MON@H

Creator
  • Posts

    406
  • Joined

Everything posted by MON@H

  1. MON@H

    error

    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. MON@H

    error

    Like I said already, plugin is not a problem, it works as expected
  3. MON@H

    error

    Changed Status from Not a Bug to Fixed Changed Fixed In to 2.3.11
  4. MON@H

    error

    Take a look at this https://codefling.com/files/sc/30118-bug/#findComment-149654
  5. MON@H

    error

    @ProjektEU, as I already said, the problem is not with the plugin.
  6. MON@H

    error

    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" ] }
  7. MON@H

    error

  8. MON@H

    error

    No, there are no problems
  9. MON@H

    error

    Changed Status from Pending to Not a Bug
  10. MON@H

    error

    Please, be more specific. Plugin works as expected (not only) for me
  11. 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
  12. MON@H

    bug

    How exactly are you 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.
  13. MON@H

    bug

    Changed Status from Pending to No Response
  14. MON@H

    bug

    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
  15. MON@H

    Limit Entities

    @etiv someone reported that the plugin works fine on Carbon, I haven't tried it myself, so I didn't change the default "unsupported" label.
  16. MON@H

    Foundation Bypass

    Changed Status from Pending to Not a Bug
  17. MON@H

    Foundation Bypass

    There is an option in config to prevent that: "Prevent excessive merging of buildings": true What exactly do you mean by "bypass foundation limits entirely"?
  18. Changed Status from Pending to Not a Bug
  19. Make sure you have installed https://github.com/dassjosh/Rust.UIFramework/releases/latest
  20. MON@H

    Limit Entities

    @SlayersRust the easiest way to implement other plugin support is to add a custom hook into that plugin to let other plugins to block some action. Something like "CanPlaceDeployable" or "OnExtendedPlaced". Then other plugins like Limit Entities could add that hook to block/allow that action
  21. MON@H

    Limit Entities

    @Chill Roleplay edit your localization file according to your needs?
  22. MON@H

    Bug in Limits

    I'll add it into next version
  23. MON@H

    Bug in Limits

    Changed Status from Pending to Not a Bug
  24. MON@H

    Bug in Limits

    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
173.9k
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.