nivex
-
Posts
5,185 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
hi, that plugin would need to ignore entities not belonging to a player so with OwnerID 0 or using the bool HasEventEntity(entity) API from RaidableBases it should just ignore OwnerID 0 really.
-
hi, @CsaszyKJ the priority for the options is rug, bed, floor, roof and then outside. npcs are spawned based on this order, but the location for each is random. if they do not spawn in any particular area then you're not spawning enough of them. I either use a priority for the options, or I make it completely random like the locations, but I won't do both, it would be too much bloat -
@aimacak don't know what plugin it could be then. you will have to find the plugin conflicting with mine Armor Not Forever seems like the most obvious plugin to unload first.
-
@aimacakI tested the semi rifle auto turret again and it continues to reload. I believe its another plugin since you've stated this happens only with some guns. please post any plugin names you're using that is relevant. such as ammo, turret or item plugins. if you're not sure if its relevant then post the plugins name anyway.
-
@Dr.D.BugI used your config with version 2.6.7 and received the cooldown. very odd, to reiterate these are the reasons the cooldown will not apply: admin/developer, flying, raidablebases.allow, raidablebases.buyraid.bypass.cooldown permission, or Lock Raid To Buyer And Friends I am a bit confused by what you mean by "playermode" if that entails authlevel 0 and no admin or developer flag then I understand. if a plugin is removing this status then it's likely not working properly. you can replace lines 19176 to 19248 with this code: https://pastebin.com/cNrx14WP change those lines RaidableBases.cs. this should help you debug what is going on. it will send messages to whoever buys the base when it starts and again when it ends.
-
Lock Raid To Buyer And Friends is this enabled? it will not set the cooldown when the raid ends. if not just send me your config @aimacakyour message is confusing. you use NeverWear, and it only prevents loss for items in your whitelist? @MaxxxEdge Ill see what I can do about items breaking or losing too much condition but its not caused by this plugin
-
@Shneid there's no config option. in order for the ladder to work properly it must reset itself each wipe, but it will never reset ALL lifetime stats lifetime stats start with the name Total. e.g: TotalRaids, TotalPoints, TotalEasy, etc. so this code would reset the ladder, but never lifetime. public void Reset() { Raids = Points = Easy = Medium = Hard = Expert = Nightmare = EasyPoints = MediumPoints = HardPoints = ExpertPoints = NightmarePoints = 0; } lifetime does not expire until 60 days of inactivity, or if they have a grand total of 0 raids, data.Players.RemoveAll((userid, playerInfo) => playerInfo.TotalRaids == 0 || playerInfo.IsExpired()); you would need to view the datafile after a server wipe. if there is an empty file then it got corrupted somehow. if all players are there but all of their stats are 0 then i'm wrong and it's bugged. latter should be impossible given the above @aimacak @MaxxxEdgedo you guys use SkillTree?
-
@CM1234 you can remove the turret from the copypaste file by using /paste and then recopy it with /copy
-
check for the raidablebases.buyraid.bypass.cooldown permission. i just tested for you and everything appears to work in 2.6.7 @aimacak 1. the time starts after a base has spawned and is how long in seconds until the next base can spawn. minimum of 1 second. 2. Block Plugins Which Prevent Item Durability Loss tries to force all items to take condition loss, but it's not going to break an item in 3~ hits UNLESS there's a conflict with something else. which plugins are you two using for condition loss? there is NeverWear and NoDurability that I'm aware of. @MaxxxEdge these are not convars, where are they from? conditionloss.damagemultiplier "0" conditionloss.armorhealthmult "0" 3. I will look again for you. 4. gun damage modifier is for every gun. there is no setting to adjust individual gun damage modifiers. i suggest removing pistols as some are wicked OP and a modifier isn't going to do it justice imo
-
Changed Status from Pending to Closed
-
@Dr.D.Bugthe raidablebases.allow permission and admin cooldowns are set to 0 so the cooldowns won't apply to you since they are 0. even more importantly, they will not apply if you are in noclip @aimacakif you set Always Maintain Max Events to false then it's not going to spawn them Time To Wait Between Spawns is how long it waits before it consecutively spawns another base it sounds like you should be using Scheduled Events if you want to space them out more, and configure Max To Spawn At Once to 1 and the Min and Max times to the amount of time you want them spread out to. I could add your request but I think Scheduled Events is better suited for what you're describing
-
as I said, this exists already. if you want a specific base to use a specific loot file then put that base in its own profile and put the loot you want to spawn in its own Base Loot table example: if the base is oxide/data/copypaste/aimacakhard111.json then you create a profile: rb.config add hard111 aimacakhard111 2 this will create the file oxide/data/RaidableBases/Profiles/hard111.json with the base aimacakhard111 and set the difficulty to 2 (hard) then you create oxide/data/RaidableBases/Base_Loot/hard111.json and put your loot table in this file. if you want the base loot to always spawn then enable Always Spawn Base Loot Table in the oxide/data/RaidableBases/Profiles/hard111.json profile. bonjour. this is not in the Raidable Bases plugin. it is an exclusive plugin that I've written for the Zombie Land server that interacts with the Raidable Bases plugin.
-
few things that could do this: 1. those specific bases were not copied properly. those would need recopied with half of the foundation (1.5 meters) visible above ground while the remaining half is underground. this is key. 2. if not all, but only if a small portion of the base tends to spawn slightly underground then this is unavoidable. 3. the profile heights were modified. there are multiple settings for this: 4. autoheight was enabled in the profiles. it is false by default and should generally not be enabled. most commonly the reason is #1, but #2 could apply here since you did not clarify how much of the base is underground. here are the settings for #3 and #4 "Height Adjustment Applied To This Paste": 0.0, "Force All Bases To Spawn At Height Level (0 = Water)": -1.0, { "Option": "height", "Value": "1.0" } { "Option": "autoheight", "Value": "false" }, you are either missing libgdiplus if using a linux machine, or another plugin is preventing the kill from happening
-
@MNfreakTim @HowlingWolfI removed that option in 2.6.7 btw, you just need to change stability in the profiles for each of the bases as originally intended now
-
ya, oxide/data/RaidableBases/Profiles/ "Arena Walls": { "Enabled": true, "Stacks": 1, "Ignore Stack Limit When Clipping Terrain": true, "Use Stone Walls": true, "Use Iced Walls": false, "Use Least Amount Of Walls": true, "Use UFO Walls": false, "Radius": 25.0 },
-
this cooldown applies to the player who bought the event. there will be an option to apply it to all ally in the next update. if ownership changes then the new owner will not receive this specific cooldown when the event ends. the short answer is that the cooldown starts when the event ends. the long answer is that in order for this to happen the cooldown must be set when the event starts and reset back to the full cooldown when the event ends. this prevents any exploitation of the cooldown.
-
which cooldown @Dr.D.Bug
-
@Dr.D.Bugsure, added in next update @TwoShoesnp @Shneidhello. are you using 2.6.7? ill check it out. edit: the turret will not fill or refill ammo if one of the following conditions is triggered: 1. if anyone tries to loot it at ANY point when Allow Players To Loot Traps is enabled, or 2. if you become authorized on the turret or TC by any means, including by another plugin such as DynamicCupShare or other Auto Auth plugins. either condition will completely prevent the fill/refill method from being used. this is intentional to stop any infinite ammo exploits. admins and users with the raidablebases.canbypass permission are excluded in the next update. if this isn't the case then I can look into it further just keep in mind that #1 will stop the turret from refilling if you try to loot the turret at any point, as will authing.
-
nah i removed that sometime ago. i will reimplement it in the future though
-
lol ive seen my fair share of nightmare configs. i don't recommend it but if it works for you then thats what matters.
-
Changed Status from Pending to Closed
-
nice! no problem
-
yes, that would be the free version. make sure Rust Server Manager, some host web panel uMod updater, or whatever updater you have is not overwriting the paid version =\ unfortunately, that wiped out your premium settings. the free version does not have those settings so they would not exist anymore. you can simply reinstall your tier package to fix that. only the oxide/config/RaidableBases.json and oxide/data/RaidableBases/Profiles would need reinstalled. @MrChubbyFingerz thanks @GamingHQ
