nivex
-
Posts
5,322 -
Joined
-
Last visited
-
Days Won
185
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
no problem. if you can't resolve your issues then a fresh server install might help you.
-
"Force All Bases To Spawn At Height Level (0 = Water)": -1.3, heya, this should be -1.0 in your easy profile not spawning properly would be the copypaste file or an error that you'd see in the server console. there's no issue with my tier bases that would cause this unless a file became corrupted on the server. try reuploading all of your copypaste files, and look for any errors if this continues to happen. if it's a despawn issue instead of a spawn issue then it's best to use a plugin such as Timed Execute to unload the plugin a few minutes before each server restart. any number of things can go wrong when raidablebases is no longer loaded, other plugins can interfere, the server might have experienced an issue during restart, etc. those are out of my control.
-
hi. its probably a json error. it wont load the profile if there's an error in it make sure the easy profile exists make sure Allow PVP is configured the same as your other profiles or that its set correctly. can't say much else without a config and the profile.
-
@hid333 yes, this is a setting. Block Plugins Which Prevent Item Durability Loss -
no problem. it is not guaranteed to spawn with 1.0 probability as stated above. if you want it to spawn then it belongs in the base loot table with Always Spawn Base Loot Table enabled in the profiles. oxide/data/RaidableBases/Base_Loot - you should have a few items in here that you always want to spawn. enable Always Spawn Base Loot Table in the profiles so that this happens. such as boom or resources. oxide/data/RaidableBases/Difficulty_Loot - the majority of your items (up to some 800 in rust now) should be in this file. these items will be picked randomly to spawn. 1.0 or 100% probability does not guarantee an item to spawn. all 800+ items in the game have 1.0 or 100% probability by default. items must be pooled like in a lottery, and then the probability is rolled on for each item.
-
Changed Status from Pending to Closed
-
ok no problem
-
hi the message settings are in the config. if you don't want any messages then turn it off. Send Messages To Player. "Event Messages": { "Ineligible For Rewards": { "Flying": false, "Vanished": false, "Inactive": true, "Not An Ally": true, "Not The Owner": true, "Not A Participant": true, "Remove Admins From Raiders List": false }, "Announce Raid Unlocked": true, "Announce Buy Base Messages": true, "Announce Thief Message": true, "Announce PVE/PVP Enter/Exit Messages": true, "Show Destroy Warning": true, "Show Opened Message For PVE Bases": true, "Show Opened Message For PVP Bases": true, "Show Opened Message For Paid Bases": true, "Show Message For Block Damage Outside Of The Dome To Players Inside": false, "Show Message When Purchase Becomes Available": true, "Show Prefix": true, "Notify Plugin - Type (-1 = disabled)": -1, "Notification Interval": 1.0, "Send Messages To Player": true, "Save Thieves To Log File": false },
-
heya. this is not a 100% chance. 1.0 probability is set by default for every item in the game. everything works like a lottery. it is put into a pool and then rolled on (based on its probability) and if hits then it's picked and you win yay =p if you want certain items to always spawn then put those specific items in the base loot and enable Always Spawn Base Loot Table in that profile. the majority of your loot items belong in the difficulty loot table. it's putting 9 items in each box because you're only spawning 130 to 180 items. it isn't supposed to spawn the entire loot table. it's supposed to spawn the number that you configured (130 to 180)
-
@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
