nivex
-
Posts
4,802 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
hi, these are not the same plugins. meaning that one has nothing to do with raid bases plugin.
-
@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)- 572 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
-
yes. the loot is in the copypaste files. this option will delete it before rb spawns loot.
-
@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
-
hi, this wouldn't be from the plugin. the loot is in the copypaste files (most likely) or from another plugin (unlikely) "Empty All Containers Before Spawning Loot": true, oxide/data/RaidableBases/Profiles/ this should fix it. I would complain to whoever you bought the base pack from if the loot is in the copypaste file... I am constantly having to deal with this issue a lot from third party sellers
-
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
-
Nightmare despawn causing rubberbanding
nivex replied to Castiel the Shield's Support Request in Support
heya, glad to see that you guys love it! yes, there exists a setting in the profiles for this, oxide/data/RaidableBases/Profiles/ "Amount Of Entities To Despawn Per Batch": 10, you can lower this value to reduce the impact on performance. though rubber banding would be because your server is overloaded by too many plugins, or the hardware is not capable of handling the load. the latter is typical of shared machines unfortunately. -
@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
- 572 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
heya, it could be that the difficulty setting was reset somehow. you can reconfigure it in the profiles, oxide/data/RaidableBases/Profiles/ "Difficulty (0 = easy, 1 = medium, 2 = hard, 3 = expert, 4 = nightmare)": 0,
-
@Dead Nasty sure, and sphere colors are implemented next update as well. it is limited to the same colors that raidable bases uses though.
- 572 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
if no price is set to purchase then it is disabled. no problem
-
@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
-
hi, I tested this for you and was given completion and points for each raid. though I see several issues that can contribute to your problem I see that you have both of these enabled. this will not work as the second option will override the first: "Only Award First Attacker and Allies": true, "Only Award Owner Of Raid": true, Each Player Must Destroy An Entity For Reward Eligibility is a new option in the profiles, which is false by default. it is not compatible with Destroying The Cupboard Completes The Raid which you have set to true. it will be compatible in 2.8.8 both of these are set to 20 minutes. I suggest setting the second option to 25 minutes. this way the player would still receive credit if they had to go AFK suddenly "Minutes Until Despawn After Inactive (0 = disabled)": 20, "Lock Treasure Max Inactive Time (Minutes)": 20.0, this is an oversight by me. this option is too short, and is misleading. this is how long the player can be inactive at any given time. not how long they can be inactive after going offline. offline will be taken out of the name in 2.8.8 and the default will be set to 20.0. the above option is for public events (maintained/scheduled/manual), while this option is for private events (buyraid) "Reset Purchased Owner After X Minutes Offline": 10.0,
-
ill do some testing later with your config to confirm everything is working. do note my previous response about points being restricted to the owner though
-
there's no issue with /rb ladder 4 that I see. however points will increase for the owner only because Assign To Owner Of Raid Only is enabled and to quote my previous response