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, 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- 599 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.
- 599 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
-
if you go here https://codefling.com/plugins/raidable-bases?tab=comments and scroll to the bottom then you will see this. is it not there on yours?
-
hi. post your config. I'm not sure why you can't post. you can ask an administrator in the cf discord
-
Option to spawn maintained base's amount based on X days after wipe
nivex replied to abcderanzi's Support Request in Support
no problem, do note that the second command is available in the next update -
Option to spawn maintained base's amount based on X days after wipe
nivex replied to abcderanzi's Support Request in Support
I've added the command rb.config mode amount type in the next update to edit Max Amount Allowed To Automatically Spawn Per Difficulty or Max Amount Purchasable Per Difficulty for example use with automated events only rb.config easy 4 rb.config medium 3 rb.config hard 2 rb.config expert -1 rb.config nightmare -1 or to set both automated and buyable rb.config easy 4 automated|buyable rb.config medium 3 automated|buyable rb.config hard 2 automated|buyable rb.config expert -1 automated|buyable rb.config nightmare -1 automated|buyable or only buyable rb.config easy 4 buyable rb.config medium 3 buyable rb.config hard 2 buyable rb.config expert -1 buyable rb.config nightmare -1 buyable -
Option to spawn maintained base's amount based on X days after wipe
nivex replied to abcderanzi's Support Request in Support
hi, thanks! unfortunately such a broad range of options would seriously bloat the config there are commands to toggle the days that bases are available though. rb.config medium tuesday true rb.config hard tuesday true etc however, there is no way to edit the limits with commands. I can add this if you want it. you could then use battlemetric scripts to automate this with both commands. -
hi, it might be possible to intercept this with the CanNetworkTo hook, but in my experience this hook has not been reliable for years.
-
@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.
- 599 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)