-
Posts
910 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Scalbox
-
then, that is only useful for turrets that do not belong to players, so for example event turrets, raidable bases etc. Instead, to change the limit of the turrets, there are 4 groups: default vip1 vip2 vip3 For each group you decide how many turrets they can put in a certain radius and then assign the role to the group. For example you can set the default group limits to everyone by setting the permission: autoturretinterference.default to the default group Or you can create groups based on the VIP and set the various permissions for the various VIP groups autoturretinterference.vip1 autoturretinterference.vip2 autoturretinterference.vip3- 87 comments
-
- 1
-
-
- #auto turret interference
- #auto turret
- (and 22 more)
-
I'm happy that everything works, if you like leave a review, it's the best support you can give me. Thank you
-
Auto Turret setting reverting on their own
Scalbox replied to JohnnyHalfwit's Support Request in Support
Changed Status from No Response to Closed -
Auto Turret setting reverting on their own
Scalbox replied to JohnnyHalfwit's Support Request in Support
maybe that server has some plugin that conflicts, in any case let me know how it goes. Thank you -
Auto Turret setting reverting on their own
Scalbox replied to JohnnyHalfwit's Support Request in Support
Changed Status from Pending to No Response -
Auto Turret setting reverting on their own
Scalbox replied to JohnnyHalfwit's Support Request in Support
If you use it the way you use it, the plugin makes little sense because it would be enough to use the rust settings: sentry.interferenceradius 0 sentry.maxinterference 99 -
Auto Turret setting reverting on their own
Scalbox replied to JohnnyHalfwit's Support Request in Support
But what do you mean that the turrets don't work, do you mean that all the player's turrets don't work? Are there still some left on? Then I would ask you to put at least 1 meter as the radius and let me know how it goes. Thank you -
Auto Turret setting reverting on their own
Scalbox replied to JohnnyHalfwit's Support Request in Support
HI Thanks for the report. I'll do some tests right away to fix the problem -
I would be grateful if you would leave a review, it would help me a lot. Thank you
-
Changed Status from Pending to Closed Changed Fixed In to 1.0.0
-
Hi, you haven't let me know yet if everything works for you now too. Will you let me know as soon as you can? Thank you @Robis
-
I care about you being satisfied with my products. Let me know if everything works fine now. Then if you like, leave a review, it would give me a big hand. Thank you
- 87 comments
-
- 1
-
-
- #auto turret interference
- #auto turret
- (and 22 more)
-
Another person confirmed to me that the problem no longer exists, download the latest update which solves all the problems and has much better performance @Robis
-
I'm really happy I would be grateful if you would leave a review, it would help me a lot. Thank you
-
I look forward to your response
-
okay, I'm sure it works 100% now, it's been completely rewritten and is ultra optimized now
-
try with the updated plugin, for now don't put these parameters that I gave you, everything should be solved now
-
Have you tried with the updated plugin? @Robis
-
Have you tried with the updated plugin?
-
plugin updated: Improved performance
-
Improved performance
-
Plugin updated
-
A new version will be released tomorrow that fixes these issues
-
A new version will be released tomorrow that fixes these issues
-
you can type them into the console like this: server.maxpacketspersecond_tick 2000 server.maxpacketspersecond 2500 without the + in front, but they are lost when restarting. Then you should go to your server panel and add them to the startup arguments, like this: +server.maxpacketspersecond_tick 2000 +server.maxpacketspersecond 2500 If there are already others, add these at the end