nivex
-
Posts
5,873 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
@HunterZ sure np void OnPlayerPvpDelayStart(BasePlayer player, ulong userid, Vector3 eventPos, List<BasePlayer> intruders, List<BaseEntity> entities) void OnPlayerPvpDelayExpiredII(BasePlayer player, ulong userid, Vector3 eventPos, List<BasePlayer> intruders, List<BaseEntity> entities)- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@buckaru that's always fun! you can set Convert PVE to PVP for each relevant category to true in the config. make sure that Convert PVP to PVE is set to false. there are many settings which change how the plugin functions. here are some that you might want to set false in the config. you can set these to true if so desired other than that you really need to take a look at each setting to configure everything to your liking. I have tried to make each setting name to be self-explanatory. my use of "Treasure" is a bit confusing, but it means loot and/or base. -
@buckaru heya. PVP is Player versus Player. like a Call of Duty match where everyone kills each other. PVP is closest to a vanilla experience where everyone fights to take control and raid each other. in raid bases the players would be allowed to counter-raid other players. you should enable Bypass Lock Treasure To First Attacker For PVP Bases in the config to prevent any conflicts with this. PVE is Player versus Environment. like a World of Warcraft dungeon. players would destroy the npc's and loot everything. there is no PVP in these. the exception is that Allow Friendly Fire is enabled in the profiles by default and will allow friendly fire among team mates. however the Clans plugin (and others) can still block this damage if configured, or if it allows the player to enable or disable a separate friendly fire (which will override my friendly fire if it the damage is disabled).
-
@Bear Grills those settings are for lockouts. use these. Lock Treasure To First Attacker Lock Raid To Buyer And Friends
-
@KayKay hi. there's too much load on your server that it can't handle it. you need to reduce the amount of bases, reduce the amount plugins, or upgrade your server
-
no, protocol is still 252 from the 4th.
-
@Soller I will look into this some more, maybe it is the Rust protocol changes.
-
.
-
@Soller this information is not wrong. it is reset to 0 when you wipe your map. lifetime stats are not reset unless the file becomes corrupted.
-
@Soller hi, /rb ladder will show the number of bases counted + points for those bases /rb ladder 0 will show the number of easy bases + easy points /rb lifetime exists too
-
@Soller 2. I'm not sure about cheats 3. 10 minutes is the old default, and was changed to 20 because it is far too low and caused many issues like this one. no, it would not affect them if they were actively raiding again. 5. if the issue was present in 2.8.5 then this wouldn't be the cause. otherwise, it could be the fire game bug if the player is using only fire to raid. 7. no, this is specific when a player despawns their own purchased base using /rbe despawn yes, if you set those false then they cannot be the reason. there is no other reason that the plugin would not give them points. furthermore, they would receive a message if they were ineligible unless those messages were disabled in the config under Event Messages.
-
@Dead Nasty I've added this to the default config in the next update, but old configs will need to add this change manually after the update is released {PVX} will be replaced with the PVPFlag or PVEFlag message located in the language file
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@Dead Nasty sure, and sphere colors are implemented next update as well. it is limited to the same colors that raidable bases uses though.
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@KayKay what do you have Player Cupboard Detection Radius set to? it might be set too low if raidable bases are spawning close enough to abandoned bases to have conflicts. I suggest this be set no lower than 125. regardless, I will implement measures in both plugins to mitigate the chance of the bases spawning too close to each other. I would still need to know the rough cause of the conflict to determine where the conflict is in the code though
-
@KayKay if you're getting rubberbanding during a paste then edit the copypaste config and change this "Amount of entities to paste per batch. Use to tweak performance impact of pasting": 1, as for the conflict you'd have to be in-game and match it up with whatever is happening at the time
-
@KayKay I would need more info was it a player, an abandoned entity, an abandoned turret/samsite, a player entity, a tugboat, etc
-
@Magnumk hi, yes. I've moved it into the profiles in the next update
-
next update nearly ready. just waiting on my testers to confirm everything is in order. I tried to consider many features for shelters: 1. shelters decay rather quickly in vanilla, so seeing them become abandoned would be rare for lengthy requirements unless decay is disabled 2. if you cannot claim it then you must destroy locked shelters before you can loot the contents from within it 3. Legacy Shelter - Loot Required - any shelter not meeting this requirement during a scan will be deleted 4. Unlock Instead Of Destroying During Scans will allow shelters to become unlocked rather than destroyed during scans 5. Allow Claim Of Unlocked Shelters allows players to claim any shelter not belonging to a player with the /sar claim command 6. Allow Conversion With SAR allows players to convert their shelter into an abandoned base event using the /sar command 7. players can attack shelters with abandonedbases.attack and abandonedbases.attack.time to convert or see time left but nivex. what about exploiting? follow a player. drop shelter, deploy box, put 6 items in box, type /sar, event becomes PVP, exit shelter, kill player, loot player, /sar cancel no worries. I thought of that too. Block Conversions Within X Meters Of Enemy Player is 150 meters by default.
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@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
-
@RigorousPizza97 yea, the above reasons are the only reasons you wouldn't be able to enter. yes, it could prevent you from using ladders if you're not allowed in the event. @Chloe_Glano no, but I will move it to the profiles so you can in the next update
-
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.
-
@Matheuss520 yes, I understand that. though my answer is just as relevant and what you've said is too vague. can you elaborate.
-
@EvilDips I don't know then. 4.1.38 was just released a week ago, and it says it fixed that issue. probably another plugin since copypaste and raidablebase doesn't have that issue. I already delete them, and have no such messages
-
@EvilDips that is from CopyPaste, and was fixed in the last CopyPaste update
