nivex
-
Posts
5,907 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
I think I've fixed the issue with "Status UI" and "Ladders" not working, but awaiting further testing to verify before I release an update. just have your players re-enter the event a second time after they die. in addition to the next update: I've added a new option to set how many hours after a wipe each difficulty level can spawn. For example, you could set Nightmare difficulty to 72 hours, so Nightmare raids won't spawn until 72 hours have passed after a wipe. This option is available separately for Scheduled and Maintained Events. For Buyable Events, there's added flexibility for VIP groups and permissions. For instance, if Nightmare is set to 72 hours, you could set a VIP permission to 48 hours and another VIP group to 24 hours. A player with the 24-hour VIP group would be able to purchase a Nightmare event after 24 hours instead of waiting the full 72. Note that these restrictions apply only to the spawning of events, not entering them. -
@Todays Ambitions yes, if Amount Of Items To Spawn is less than the total amount of loot items in your loot tables then it will pick from them randomly. typically you would put such items that you always want to spawn in the Base Loot table and enable Always Spawn Base Loot Table in the profiles. then allow everything else (Difficulty Loot) to spawn randomly.
-
@fullwiped heya 1. sure, I can add the option to delay spawning after a wipe 2. it's intentionally not allowed for anyone to build a foundation onto the base due to exploits where players would extend the foundations from the base to outside of the bubble to bypass other restrictions. @ChardaZAR odd that "shortname" was null. are you mistaking that with "name" ? not sure how "shortname" would be null, but "name" should be unless you have a specific custom item that you're adding btw, if you want base loot to always spawn then you can enable Always Spawn Base Loot Table in the profiles. otherwise it will be picked randomly with Difficulty Loot. that is the purpose of base loot (to spawn with a specific profile, always, or randomly, depending on that option) I suggest using this to edit your loot tables, https://codefling.com/tools/raidable-bases-loot-table-editor Destroying The Cupboard Completes The Raid is in the config. you can set it false if you don't want the event to end when it's destroyed/looted.
-
i'm aware there's still an issue and I'm looking into it. if anyone can provide step by step on how to reproduce it would go quicker. players can re-enter the event for the time being to fix it (status ui not showing, not able to place ladders, etc. it's all caused by a single issue)
-
@Burrito hi, in the profiles, oxide/data/RaidableBases/Profiles/ look for Amount Of Items To Spawn
-
2.9.7 released to fix all known issues introduced in 2.9.6. enjoy
-
I'm still working on these issues. almost done.
-
yes I am aware of the issues. will be fixed soon
-
i'm aware of some issues with this update and I'm working to resolve them
-
@vanzylquintin42 heya. it's likely another plugin blocking it. otherwise, there are very few options that would do that. Block Damage From Outside To Base (true by default) Cooldown Between Events Blocks Base Damage (true by default) Cooldown Between Events (3600 by default) otherwise it's another plugin. TruePVE requires no modification. AB will override that plugin. -
2.1.8 released to fix several issues. enjoy
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
2.9.6 has been released - this requires the Rust update to compile. enjoy
-
@S0TR I wasn't able to get the weaponrack method exposed, so I have disabled my code for weaponrack support. I have made it possible to re-enable it using reflection though. if you edit the (new) .cs file and remove all references of //REM: then it will work. just be careful to not remove the rest of the code on any line with a reference to that. I think it's safe to use that code, but I don't know for certain without someone to test it.
-
@Fanatik hi, 'it is a bug and will be fixed with tomorrow's Rust update.
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@NoxiousPluK no problem lol yeah everything should despawn including the mounts. I will have to add an option to not despawn it, like I did with RB.
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@NoxiousPluK hi, your error is from the French language file (oxide/lang/fr/AbandonedBases.json) should be I will ask the translator to fix it in the next revision. thanks
-
@Ned Flanders hi, it is compatible. carbon has backwards support for oxide.
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@Oldbtchsgaming hi, WarMode is not my plugin so I don't know what that's about. you can set permissions in the profiles, but there are no permissions by default. this should be unrelated. "Permission Required To Enter": { "Buyable Events": "", "Maintained Events": "", "Scheduled Events": "" },
-
@S0TR hi, somehow your entities are being destroyed in the same frame. not sure how that's possible in that specific hook but it doesn't really matter. easy fix. it's fixed in the next update, thanks to misticos. public static bool IsKilled(this BaseNetworkable a) => (object)a == null || a.IsDestroyed || !a.isSpawned; on line 23983 is being changed to public static bool IsKilled(this BaseNetworkable a) => a == null || a.IsDestroyed || !a.isSpawned;
-
@Kk hi, that would be caused by something else. RB does not move items to the corpse, which is what the warning message shows. also, that message should never show anyway. rock.entity[108735382] is a WorldItem which should override SwitchParent. so you have a deeper issue going on.
-
@Chloe_Glano hi, yes that is how it works. you cannot buy, loot or enter the event without permission.
-
@Kobani yes, set Award Top X Players On Wipe to 0
-
@0g.Ghost.7373 hi, not if Remove Admins From Raiders List is enabled and you cannot use noclip or vanish
-
@Magnumk I can add it in the next update. so that you can add {basename} to Marker Name in the config, or you can add it to the MapMarkerOrderWithMode and MapMarkerOrderWithoutMode messages in the language file. though I advise against it. it'll get to a point where some players won't go to specific bases in favor of others. think of it like doing quests in a MMORPG where you can just look at the map to see what quests are available. if none seem interesting then you are more inclined to log off sooner than later. that hurts player retention. otherwise if they don't know what's available then they must invest time to travel which keeps them engaged, and they're more inclined to raid to avoid boredom and because they've dedicated time and effort.
-
@Magnumk hi, no. base name isn't shown in the marker.
