nivex
-
Posts
5,571 -
Joined
-
Last visited
-
Days Won
194
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
"Lock Treasure To First Attacker": true, "Bypass Lock Treasure To First Attacker For PVE Bases": false, "Bypass Lock Treasure To First Attacker For PVP Bases": false, these settings in the config file control the locking
-
heya! you can change your Eject Enemy settings in the other profiles to false in order allow this
-
the plugin is told to kill them but because it kills the door or box first it is not killing the child entities for some reason. it's not just entities from the plugin that go there, either. this is where native Rust puts the entities as well, to be destroyed, or when they're orphaned -
hey thanks. ill take a look at my changes and see if i can figure this out. in the mean time try to get a screenshot if it happens again
-
thank you guys for the info, this helps a ton when its so informative! @MNfreakTim@Lawnmorr@Rust Admin @Swedish Chef@Rust Adminthe codelock issue is already fixed in 2.4.2 but it will only apply towards new bases. existing codelocks will not be removed. not really an issue for servers that wiped though. search lights shouldn't be an issue as the plugin should kill them before it kills any building blocks. i suppose checking for children entities and killing them before their parent entity would be a permanent fix to this issue. i will investigate that after the performance issue is solved. i believe it's a loop
-
you will need to verify your loot tables. both base loot and difficulty loot. you can zip everything and upload somewhere for me to double check and/or reproduce to fix this plugin does not destroy the tc. so i believe it is either a Rust game bug stating the entity is null when it's not, or a failure on CopyPaste which would produce an error in the oxide logs that you can look for
-
heya Gumby, I will need that full error. it will be in your server log if you cannot find it in the oxide log. without this error i won't be able to help. thanks
-
@Covfefedid you see my prior message? I can do your request but need more information from you @MNfreakTim@Lawnmorr did you change the Spawn Settings in the profiles from their default values? I have no suggestions other than to set these back, however it does seem the issue is with finding a spawn point, since you say it occurs when there are multiple bases. the plugin must find spawn points and obviously this becomes more difficult when there are a large amount of bases already spawned and occupying prime spawn points. it can become difficult for the plugin to find a suitable location on the map due to this, and that will create load because it checks continuously. however this does not explain your server freezing. i will check and see if its related, and i will put this method into its own coroutine. note that this will not be in future versions 2.4.3 but 2.4.4 as 2.4.3 will address a few minor issues that are very annoying (such as placement of ladders not working). though if it is related then it may be fixed and in 2.4.3, with the primary coroutine implementation being in 2.4.4
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
hi, i believe i've found the issue and fixed in next update. will release it once i fix other minor issues too
-
hi, i would need the exact message shown Fixed `Allow Players To Use Ladders` compatibility with `Require Cupboard Access To Place Ladders` this was the change per update notes
-
@beetle@Delltus same with your suggestions. not forgotten, and it is noted for a future update
-
@Baron Von FinchusI haven't forgotten your request. It is noted down, but it will need to wait until a future update. I need to get the current update released before I make additional changes/implementations
-
I believe it may need support added for MLRS. I can check this out once I fix the other issues -
@CovfefeI looked into changing this message but I see no reference to Raidable Bases in the Death Notes plugin. those messages look to be from Discord. so I'm not sure how without more information if you can provide some @kalinovec2you would need to remove that shortname from the config or replace it with the correct shortname, as Swedish Chef said
-
Not all bases are converting to Purge Event
nivex replied to KingSizeKevin's Support Request in Support
hi, sorry, this is due to the Check If Abandoned Bases Are Too Close Together setting i imagine. it is fixed in next update to be ignored when purge is enabled -
this will be fixed sorry about that guys. a bubble does not normally indicate everything inside as being raidable. it is only supposed to be the abandoned base and no others inside or outside of it
- 610 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
ah, yes, you can control this with Player Cupboard Detection Radius but i do not recommend lowering it
-
anyone with abandonedbases.convert permission can use the command. it does require TC access
-
that setting is for the automated bases. you will want to use Distance To Spawn Bought Raids From Player for buyable events
-
which nightmare base has no TC? use adminradar to find it using the TC filter no other packages atm. tier 1 and tier 2 will be made unique soon so that will be an option for you
-
need to enable the automation on server startup, or every x seconds, in the config file you can do this by typing /sar at the base. check the documentation for the commands and required permissions
-
Medium base NPCs have different loot pool.
nivex replied to Phelan Keller's Support Request in Support
you can try replacing it, sure. there is no other possibility afaik -
hi, which map are you using? this generally just means it didn't find a position. it's more clear in the next update
-
Medium base NPCs have different loot pool.
nivex replied to Phelan Keller's Support Request in Support
yes, but what im saying is its not possible for it to do unless its 1. configured to do so, or 2. a plugin is interfering. i do not randomly generate items in this plugin. i simply pick randomly from a provided list, and if that list does not contain said item then it will never be picked nor spawned