nivex
-
Posts
6,066 -
Joined
-
Last visited
-
Days Won
202
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
does not look like this can be configured anymore after the rust update which makes it read-only removed option in next update
-
Changed Status from Pending to Closed Changed Fixed In to 2.2.3
-
there are multiple posts regarding this already thanks
-
edit the config and enable it on every day of the week @nashslash@Dr. BoomStick@TwoShoesknown issue with loot. looking into it now @Niko31no please do not give players any permissions. let the plugin do it -
Changed Status from Pending to Closed
-
sounds good thanks. not much I could do
-
@KingSizeKevinno problem, and Ill add your suggestions to the TODO list- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@恶sure
-
yes it appears so as it seems to be a server side issue. i'll likely have to use some sort of delay
-
no problem. any other questions?
-
autoheight should always be false. it does not work for every base. the building must be copied from eye level of the foundation. would you like a video to demonstrate? @恶
-
ya I will add the message @KingSizeKevin
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
Don't use AutoHeight option
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
fixed in next update thanks!
-
hi, this can only happen if these are set false: Do Not Destroy Player Built Deployables Do Not Destroy Player Built Structures
-
ill look into it thanks!
-
@Neighighon second thought that replacement of code would disable other features of the plugin, too. which is bad find this code: if (EventTerritory(center)) { Message(user, "Near Abandoned Base"); return Response.Skipped; } and remove it and you'll be good ill make this optional next update as, Check If Abandoned Bases Are Too Close Together enabled by default
-
Changed Status from Pending to Closed
-
np glad its sorted
-
i need error messages for this from the server log
-
there isn't really a viable parameter to control, other then the Radius of each event which has multiple options. though changing this will cause other issues with the dome not encompassing some base entirely. the only real solution would be to remove the check entirely private bool EventTerritory(Vector3 position) => false; you would need to replace the existing method with this one glad to hear its working well for you!
-
@chuck norrisI've added a delay to prevent this issue in the next update
