MON@H
-
Posts
348 -
Joined
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by MON@H
-
@BetterDeadThanZed if owner's "Limits Building" set to 50 then yes (in that specific building). -
@BetterDeadThanZed there are no wildcards. I was thinking about adding entities grouping, but it would add complexity to the code and probably performance loss, with a payoff from little to nothing. Limiting by exact prefab doing 99% scenarios and for 1% it doesn't it's still possible to just set lower limit. For your example you can set regular foundation to 50 and triangle foundation to 25 and it may be pretty much it. About TC, "Limits Global" is personal per player and has nothing to do with TC but "Limits Building" has. For building limit check, if there is a cupboard placed - the limits of the owner of the cupboard will apply, if the cupboard is not placed - the restrictions of the owner of the first block will apply.
-
Damn, I missed this message for some reason. In your example you can just keep the default priority and it should work. The higher tier of your group, the higher priority you should set. Like default = 10, VIP = 20, Elite = 30, Ultimate = 40, GODLIKE = 50 etc... If player has several permissions, the one with highest priority will be applied. Isn't this clear from description? I hope you figured it out already... UPD: Oh, now I see... There were a typo in default config file and vip priority = elite = 1. Fixed in latest version.
-
I can add this, but honestly, I just can't see no real purpose of doing this. Admin/server owner can edit config file with permissions and then just check which permission is granted to player know his limit. And I really don't understand why admin need this information for. If you want to see what limits the players hit most often, just activate logging at the Info level and the logs will show all the cases when players reach the limit
-
No, but why so you even need this?
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Not a Bug
-
What's the problem with putting a huge number? Use 1 000 000, for example
-
Changed Status from Pending to Not a Bug Changed Fixed In to 1.6.3
-
If you are talking about this plugin https://umod.org/plugins/dynamic-pvp then it's not currently supported. What exactly are you asking for help with? Adding support for this plugin?
-
Clear cache & cookies Redownload plugin ... ... Profit!
-
[Error] Error while compiling: RaidableBases.cs(13713,144): error CS0103: The name `GetObstructionRadius' does not exist in the current context Redownloaded file several times. Feels like uploaded file is broken.
-
Changed Status from Pending to Not a Bug
-
You can't limit horses directly with this plugin, since they are not deployable. You can limit Hitch & Trough with this: "assets/prefabs/deployable/hitch & trough/hitchtrough.deployed.prefab": 10 Also check this article to see additional info about horses.
-
@SlayersRustbuilding blocks is a different story, you can't use this logic to them, since they are all build as twig tier. You'll have to increase litits accordinaly, because adding Raidable base territory check into plugin can impact performance and people who don't want this feature will hurt. Maybe I'll come up with something later
-
@SlayersRust Add entity prefab name to Excluded list and plugin will ignore that prefab completely.
-
Added Excluded list in latest version. Add entity prefab name to Excluded list and plugin will ignore that prefab completely
-
Changed Status from Pending to Not a Bug
-
This is not a bug. Plugin works as expected. This is more like a feature request. I'll get to this soon.
-
@PopGP this plugin is for personal limits only. No teams, friends, clans support planned.
-
You can try to set log level to "debug" and see what exactly happens. It will log tons of data so it might be hard to parse, but at least some way to go
-
Changed Status from Pending to Can't Reproduce
-
Plugin is already tracking destroyed entites. Perhaps you have some custom despawn plugin that prevents tracking. To update data you can reload plugin as a workaround. To fix this issue I need more details since I can't recreate this in my environment.
