-
Posts
5,322 -
Joined
-
Last visited
-
Days Won
185
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
@AdmFRP hi. the only reasons he wouldn't get points is from one of the following. 1. server is restarting and blocked by Block Rewards During Server Restart 2. uses noclip, vanish or Remove Admins From Raiders List 3. is inactive, Lock Treasure Max Inactive Time 4. blocked by Only Award Owner Of Raid 5. did not participate, Each Player Must Destroy An Entity For Reward Eligibility (false by default, and not compatible with Destroying The Cupboard Completes The Raid until 2.8.8) 6. blocked by Only Award First Attacker and Allies 7. blocked by Base Becomes Ineligible For Rewards On Despawn 8. Assign To Owner Of Raid Only will block Assign Rank After X Completions
-
1 no. it means you can't participate in more than one 2 no. it gives a lockout when the base loses ownership. Lock Treasure Max Inactive Time 3 internal. no one can buy multiple. it is not optional
-
you can change the buyraid command in the config then they won't know what it is. I'll consider the item, that's a good idea! no, that setting doesn't apply to the whole map. it applies to each individual raid. if you set easy to 1 and have 5 easy raids spawned then 1 player can enter each of those raids.
-
ignore any messages from the game about not being able to place ladders. these are client side and cannot be hidden. ladders can only be placed on "wall.frame.cell", "wall.doorway", "wall", "wall.frame", "wall.half", "wall.low", "wall.window", "foundation.triangle", "foundation", "wall.external.high.wood", "wall.external.high.stone", "wall.external.high.ice", "floor.triangle.frame", "floor.triangle", "floor.frame" if you see anything missing from this list then let me know and I will add it. this list and functionality is used in prevent building spheres where the game would normally block you from using a ladder. such as on roads. otherwise the game will place the ladder vanilla. Require Cupboard Access To Place Ladders setting in the profiles, oxide/data/RaidableBases/Profiles/ will restrict the use of ladders Allow Players To Use Ladders is in the config and is enabled by default.
-
@Deisel heya. normal mode is available in the free version only. this is why your paid settings were removed as they don't exist in the free version. please be careful to only download where you purchased from. if you're certain that you did not download the plugin from uMod, then an auto updater, manager or control panel updated from uMod. you should be able to block those from updating RB plugin @RigorousPizza97 hi, odd. possible reasons are Player Lockout in config, Eject Enemies From settings in profile (this has no message) raidablebases.banned permission, missing Permission Required To Enter set in the profiles, base is loading (this has no message for being ejected by it, but there is a message once the base has spawned) using fauxadmin while being blocked by raidablebases.block.fauxadmin permission, scavenging after raid is completed, Eject Scavengers When Raid Is Completed in config are hogging another raid, Prevent Players From Hogging Raids in config teleported into the raid, Allow Teleport in config the raid exceeds the allowed limit of players with Max Amount Of Players Allowed To Enter Each Difficulty. noclip and vanish bypasses most restrictions. some of these give a message.
-
ill take a look thanks
-
well, maybe the sam site hook that I am using isn't working again. though I tried on two servers without issue
-
np. I think it is 75 meters by default. that is reasonable imo. you could lower it to 35-50 though. if it doesn't work then I'd like at other plugins to see what might be causing it. can be difficult since plugins have such a wide range of options =/
-
glad you like it that is an option in the config Allow Npcs To Target Other Npcs
-
@Matheuss520 heya. that is a bit too vague. if all bases are easy then the difficulty is not set in the profiles this can happen if you install free then the paid version again. do not allow any plugins, managers or control panels to update raidable bases. do not update from uMod. raidable bases should only be manually updated by you
-
hi, Range (350.0 = Rust default) this controls the range of the sam sites. it can be found in the profiles, oxide/data/RaidableBases/Profiles/ if the sam site range is not applying then another plugin is overriding it
-
heya. this hasn't changed afaik, but Bypass Lock Treasure To First Attacker For PVP Bases should be set to true if you are limiting how many people can enter a raid then that will cause the issue too. Max Amount Of Players Allowed To Enter Each Difficulty should be set to 0 for each