nivex
-
Posts
5,927 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
here are some reasons why a base may not despawn properly: 1. the datafile became corrupted during a restart (oxide/data/RaidableBases_UID.json) 2. your server did not restart properly (crashed, shut down incorrectly, process was terminated early, a script or application that restarts the server, clicking STOP in your control panel instead of RESTART, etc) 3. your server is unstable from excessive load 4. your server is unstable because it is not restarted frequently enough (daily is recommended) 5. the map file reverted (even as little as 1 second) or was not saved prior to shut down 6. missing libgdiplus library on linux machines. host must install this for you. they will verify this is installed if you ask. if they are unsure what this is or what its for then they likely don't have it installed. it is for converting byte arrays to bitmap for the images inside of the copypaste files. 7. a plugin. such as truepve versions under 2.1.6 but any PVE plugin can potentially cause this. I have seen protection plugins break this too. 8. your machine cannot handle the load on it from plugins. ties into #3 as well 9. your machine cannot handle the load because it is shared with too many other servers. ties into #3 as well low memory and cpu usage do not exclude you from this. most common reasons that I have seen are #3, #4 and #8 data file becoming corrupted would explain why there are so few reports of this map file being reverted or not saved after further changes is fairly common too -
@Kobani Buyable Cooldowns is for raids purchased with /buyraid and is in the config. this does not affect player lockouts / public raids Player Lockouts is for public raids spawned by maintained and scheduled. this is also in the config. this does not affect Buyable Cooldowns @Emigo I have 2-3 reports of this per month and have not seen the issue on any of my servers in at least 6 months. this leads me to believe it is an issue with your server, or a plugin that's interfering. if this were an issue with the plugin then I would get constant reports. it's unknown how something would bypass all the checks in raidable bases even then. it could happen on an unstable server if it is not restarted frequently enough. daily restarts are recommended. @MatthiasBM in regards to active bases spawning on top of another active base it could be a bad config setup, but how someone would do this without knowing idk. invalid settings for Ignore Safe Checks, Spawn Bases X Distance Apart and Advanced Protection Radius might cause this in regards to active bases spawning on top of another INACTIVE base that failed to despawn. this is intentional and isn't a bug. the base not despawning is the issue. I have seen a dome persist, but never a map marker. a missing libgdiplus on Linux can cause these issues truepve versions under 2.1.6 can cause this issue other PVE plugins can cause this issue too. the developer would likely be oblivious to it too since the cause doesn't seem like it would be an issue
-
@Dr.D.Bug heya. newly created or edited zones require rb to be reloaded. rb can do most of what zonemanager does too so there isn't much need for it. in short, no, you can't do that in such a tight space except by using Spawns Database and adding points where you prefer them to be
-
@BadLandPVEhi, not possible until dynamic difficulty is implemented. though such a feature would move any difficulty settings from the config into the profiles should I implement it
-
it's a neat idea. I'll note it down @PistOffBastd
-
can anyone confirm if damage dealt by the PredatorMissile plugin to an npc is still being blocked? I tested and the damage is working. please DM your config if this is not the case.
-
no problem! @hid333
-
heya. it isn't allowed to spawn automatically or with buyraid because of this setting. manually would still work yes.
-
@hid333 heya, most common reasons are: 1. a json error is preventing the nightmare profile from being loaded 2. nightmare profile has Allow PVP set to true and Allow Players To Buy PVP Raids is set false but really I can't answer without the config and nightmare profile.
-
@hid333 yes, this is a setting. Block Plugins Which Prevent Item Durability Loss
-
@Wolf twig is immune because you've enabled the setting for it to be immune "СтроителЬные блоки устойчивы к урону": true, "СтроителЬные блоки устойчивы к урону (толЬко опора)": true, English translation "Building Blocks Are Immune To Damage": true, "Building Blocks Are Immune To Damage (Twig Only)": true, Is my Russian translation not correct for this setting?
-
you need to send the files I requested.
-
@Wolf this shouldn't be caused by RB (edit: unless configured to be). this is another plugin, a game bug that I'm not aware of, or the base itself is somehow corrupted which I can't explain either. send the base to me in a DM and I can check it later tonight. include the profile and config files.
-
@hid333 I don't understand this translation. Type it in your native language. if you're asking about loot bags that drop from boxes then yes you can remove them when the base despawns. Despawn Dropped Loot Bags From Raid Boxes When Base Despawns is in the profiles, oxide/data/RaidableBases/Profiles/
-
@Wolf Turrets is a physics isssue with the game. It was fixed a couple months ago in the Rust update, but is still broken with prison cell gate, prison cell wall, and just yesterday I had it happen where turrets were shooting from the floor above me somehow. Add wall.frame.cell.gate and wall.frame.cell to Kill These Prefabs After Paste in the profiles as a solution until Facepunch can fix it. "Kill These Prefabs After Paste": ["wall.frame.cell.gate", "wall.frame.cell"] I had this happen on vanilla, and sent the video to Facepunch but didn't receive a response.
-
@aimacak testing with this as the only plugin may not be helpful if the issue is server related. regardless, the loot is deleted from the sav file prior to every restart. it doesn't exist after a normal restart. I know that you do not have the issue, but you can test for yourself. this is how I know it is server related. spawn X number of bases. shut the server down. delete raidablebases so the bases cannot despawn. if you do not delete then Oxide will load it again during server startup. restart server. go look for loot inside of the existing bases. there won't be any because it is deleted prior to every restart. if it did not restart correctly, or another plugin restored it then this is no fault of the plugin. it may have crashed, the process was killed or terminated early, the sav file was not saved, or the sav file rolled back. any rollback, even 1 second, could cause this. there could be other reasons, but these are the most common for plugin issues and map rollbacks. results of the above test show that there is no loot as expected. this is what you will typically see when the plugin does not despawn the base, which is also caused by the above reasons.
-
@garz it is simply another plugin, a server crash or a bad restart such as killing the process or it being terminated early. there is nothing else to clarify regarding this specifically. all servers are compatible with the plugin so long as the host installs the operating system and the required software correctly. linux servers must have the libgdiplus library installed. all servers must have proper file permissions. control panels, scripts and plugins all must restart the server by using the quit or restart commands.
-
@garz the checks are sufficient, and the above code clearly shows this. the loot is cleared before the box is killed. we do not have this issue during restarts because there is no such issue with the plugin itself as I've stated 3 times now.
-
@garz that is not what I said. I said that your issue would be caused by a crash, a bad restart or a another plugin. unloading would likely stop it from happening, but would not fix whatever issue is causing it. you do not need to manually unload the plugin each time either. that can be scheduled with your restart, too. I recommend all servers to do this. it is beneficial for many reasons. it is not possible for me to fix issues outside of my control. it is common for there to be various issues with server restarts and this prevents the issue from occurring. besides, there are redundant checks so that no box is destroyed until the loot is cleared first. it would not be possible for the plugin to have dropped your loot. therefore, it must be caused by the above.
-
hi, this is not an issue with this plugin. 2.8.5 has implemented a second redundant check for this just in case, too. your issue might be caused by another plugin, a server crash or otherwise a bad restart. if this were an issue then I would have had multiple reports.
-
@Dr.D.Bugyou can see my response above. I'm not sure how else to check what each prefab has. otherwise I could just generate a list of every item for each prefab. I don't know how to iterate it as my results differ greatly from what AlphaLoot correctly shows.
-
@Dr.D.Bug heya, you might be able to find the loot table for heavy on corrosionhour. otherwise it is in the AlphaLoot default data files. @hid333 heya, the weapon (ANY weapon) loot cannot be disabled by itself. you must disable the entirety of the prefab loot, or use a prefab that has different loot. such as peacekeeper scientists, junkpile scientists, or roaming scientists. I think roam has the least amount of prefab loot but don't quote me on that. heavy scientist loot is used by default as every npc (scientist and murderers) is a heavy scientist Disable All Prefab Loot Spawns (set true and no prefab loot from the game will spawn) Prefab ID List (Enabled setting must be set to true to use this list of prefabs instead of the default heavy loot since every npcs (scientist and murderer) are heavy scientists.)
-
Allow Teleport Ignores Respawning setting in config @aimacakthat one is for player death
-
@aimacak this prevents the blue electrical glow on turrets (interference) config lets you choose between player turrets and non-player turrets. RB turrets have no interference (unless another plugin causes it) so you don't need this plugin for RB turrets
-
sure @PPlank NoInterference.cs
