nivex
-
Posts
5,812 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
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 -
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
-
@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
-
@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
-
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
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
anyone with abandonedbases.convert permission can use the command. it does require TC access
-
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
-
@Covfefewhat is that from? it would need to use my hook OnPlayerExitedRaidableBase and check if they're dead, then use the BaseName variable for the discord messages void OnPlayerExitedRaidableBase(BasePlayer player, Vector3 Location, bool AllowPVP, int mode, string ID, float spawnTime, float despawnTime, float loadTime, ulong ownerid, string BaseName)
-
@beetlecan you clarify your question? I don't understand it completely. also thanks for answering! @BetterDeadThanZedah ok, i've added the permission raidablebases.setowner in the next update for these 2 commands
-
thanks @thepiercedweirdoim looking into it
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@BetterDeadThanZedthat's not what I said. I said it shouldn't be given to players. you can give it to whoever you trust of course.. but that's on you. it is admin permission to the plugin
-
@Delltusthats a neat idea ill keep it in mind
-
@BetterDeadThanZedthis doesn't require permission for admins. raidablebases.allow is the equivalent admin permission and should not be given to players
-
that was very entertaining. well done
-
@McCoy84@Swedish Chef boxes have always despawned after being fully looted and i have no plans to change this. this shouldn't be confused with Drop Container Loot X Seconds After It Is Looted either @Emigoenable it in the config under ui settings
-
@dIMjIMzone manager would need to bypass any flags by using the EventTerritory API to allow exceptions for raidable bases
-
@KingSizeKevinthat would be a bug. i will check it when i can. very busy irl atm
-
@bobbybaker82 if (position == Vector3.zero) { return null; } Vector3.zero is 0,0,0 and this plugin does not spawn npcs there. thats where the server sends entities to be destroyed. so you have another plugin interfering. as for code locks, those will be destroyed in next update during server shutdown
-
alright thanks @Pupsik@Neighigh I'll have to determine how I want to handle this as it's not intended lol
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
we'll see. I'm going to try reimplementing it differently first
-
@Swedish ChefI will likely remove it since I see no reason why it should be an issue in the first place. if I can't fix it then it should be removed
-
@Emigodepends how you have rb configured for the zones in Allowed Zone Manager Zones other than that idk how that is possible that it just randomly breaks.
