nivex
-
Posts
5,932 -
Joined
-
Last visited
-
Days Won
200
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
Coming in 3.0.0: Upon popular request -- Dynamic support for adding your own custom difficulties with an easy to use command! I see this question often "Nightmare is difficult enough to create. Why would I want to create some abomination that's more difficult and is even more time consuming than a Nightmare base?" And I reply, "Because the players crave a challenge. But, how about something else entirely?" Be creative. Underwater Bases Use Water Settings in profiles, and set Chance For Underwater Bases To Spawn to 100 Ignore Land Level On Seabed should be false when using bases with foundations Ignore Land Level On Seabed should be true when using bases with no foundations (built out of floors and walls like submarines) Water Bases Use Water Settings in config, and set Chance For Underwater Bases To Spawn to 100 Set Spawn On The Surface Of Water to true Ignore Land Level On Seabed should be true Sky Bases Set Force All Bases To Spawn At Height Level (0 = Water) to 400 and all bases will spawn 400 meters up, or Alternatively, set Height Adjustment Applied To This Paste to 200 and all bases will spawn 200 meters off of the ground Set Foundations Immune To Damage When Forced Height Is Applied if desired Alternatively, set Foundations Immune To Damage if desired If using NPC they should be configured to spawn inside of the base if at all Underworld Bases Create your own prefab in RustEdit to use as a platform Add prefabs to this platform to be used as teleport positions Add said teleport prefabs to Map Prefabs For Buyable Teleport (this setting is for map prefabs added in RustEdit only) Use Spawns Database to create a spawn position for the base itself, and add this to Spawns Database File in the profile Floating Islands TBA -
@laodu sure, I will keep you in mind
-
@laodu hi, likely the 6th. it requires a lot of testing across multiple servers to work out any potential issues before release.
-
@laodu that looks like a Rust+ issue since it says CompanionServer
-
@Grumpy_old_man hi, it didn't change. something might be killing the game object associated with that event. another plugin most likely. I don't think the game would do that. otherwise, it should not be possible to despawn on its own like that as it uses a date time for it @Dead Nasty hi, yes. "oldID" is the key, and "1" is the value to the right of it in its own quotes. change that "oldID": "1", could just be 111 or something unique
-
@laodu hi, not yet. the only person I've let try this out is @Mabelbecause of how much he does for the Rust community. so this is my way of saying thanks to him, by letting him try something before anyone else that I think is really neat! that said, it needs a lot of testing so it will be several days before it's completed.
-
In the next update (3.0.0) To add a new difficulty: Use the command: rb.difficulty add Extreme (or any name of your choosing) Edit the configuration: Set the Difficulty Color (Inner) to E3963E Set the Economics Buy Raid Costs to 15000. Create an Extreme loot table and place it in the Difficulty_Loot and/or Base_Loot folders. Reload the plugin: Run the command: o.reload RaidableBases or c.reload RaidableBases Add a base to the newly created profile: Use the command: rb.config add "Extreme" nivex1 Spawn the newly added base: Use the command: /rbe nivex1 That's about all there is to it. It is no different than setting up any other difficulty. You can create as many difficulties as will fit within the Buyable Events UI. The UI auto resizes to try and fit them all into it.
-
dynamically added a new difficulty getting there
-
@Dead Nasty hi, that is probably an issue with oldID. you can edit the copypaste file and change each one to some unique number "oldID"
-
@Dead Nasty hi, initiator doesn't matter. only these settings can block the damage Cooldown Between Events Blocks PVP Damage Block Damage From Outside To Player Cooldown Between Events -
@NavyChief hi, I am not sure what it does since I do not use it. you would just have to try it. if you can damage the raid bases then it should be ok.
-
@NavyChief hi, it would need to ignore entities not owned by a player to not conflict with RB
-
@PhatBlinkie heya, that list excludes those entities from being blocked by Allow Players To Build when set false. it has no functionality when set true. remove your exclusions set Allow Players To Build to false set Allow Players To Deploy Barricades to false they will not be able to build anything then, except for ladders if you have Allow Players To Use Ladders enabled in the config
-
@vanzylquintin42 you can adjust height in the profiles, oxide/data/RaidableBases/Profiles/ { "Option": "height", "Value": "1.0" }
-
@Magnetos again it looks like an issue with your language file
-
@Magnetos hi, looks like the language file was changed for "RP"
-
@ChardaZAR hi, that doesn't increase the amount of items to spawn. it increases the loot amounts. so if you have explosive.timed 10/10 and use a 1.4 multiplier then it will spawn 14/14 instead.
-
@Wile E. hi, that has nothing to do with hours or time. 15 is the default. that's the max buyable events that can be active at any given time.
-
@Diesel heya, thanks for answering. player lockouts is for public events that spawn by Maintained or Scheduled Events buyable cooldowns is whats used for raids purchased with /buyraid
-
@Wile E. hi there I can't recommend any one-way, because it's all down to personal opinion, but I can try to expand on the details for you there are multiple ways to go about this using buyable cooldowns in the config "Easy": { "VIP Permission: raidablebases.vipcooldown": 1800.0, "Admin Permission: raidablebases.allow": 0.0, "Server Admins": 0.0, "Normal Users": 1800.0 }, VIP Permission - grant this permission to your vip group. then. anyone in this group would receive this cooldown for Easy raids Admin Permission - the raidablebases.allow permission is what you'd grant to your admins, moderators or staff only Server Admins - this is anyone with an admin flag which is generally auth level 1 or higher Normal Users - this is anyone that does not fall under the above, aka the default group the lowest cooldown time will be chosen based on the above four options. users who remain in vanish or noclip will not be given a cooldown the cooldown is applied when the event is purchased, and does not start to expire until the event despawns
-
@Fanatik that's not an error. it's debug, and is normal. post your config
-
@Fanatik perhaps I should remove the requirement for a TC during purge? edit .cs and change on line 4267 if (!hasPrivilege) to if (!hasPrivilege && !IsPurgeEnabled) and you must change this too on line 4217 a = entity.transform.position; to a = entity.transform.position; position = a;
-
@Fanatik hi, TC is required, that is why you see: No privilege found. this is intended yes, this is normal. it is required to restart the purge each time
