nivex
-
Posts
5,874 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
@Dead Nasty really not sure then. I'd look for a corrupted copypaste file. it could be a profile in that directory, a file with text that ends with null, a file with text that starts with null, or a file where a key is null can be hard to find when you have no error. I don't have issue with this on my servers so that's why I think it is a corrupted file but its hard to know with so many options changing its behavior. edit: you should use rbe debug when this happens and toggle it back off. you can DM me the text -
@Dead Nasty just to clear up any potential confusion. it would be normal for a player to see a message indicating they were added to the queue when there are no other events spawned. players will always be put into queue, even when there are no events spawned. the plugin must find a suitable location each time a base is to be spawned. if the queue stalls and requires a plugin reload then it could be a corrupt copypaste file. this can happen even if you have made no changes. there should be an error in the logs for this. I do try to prevent stalls but there are so many ways in which an error can occur. otherwise, check if there are any errors in the logs, and send me a screenshot.
-
@Dead Nasty you can't. use the below options player lockouts is for public raids buyable cooldowns are for private purchased raids
-
@Dead Nasty can you show a screenshot
-
@KingSizeKevin yep use stack size limit is an option in the config.
-
Wipe triggers when Rust protocol changes in the config is not working properly, and can cause your ranked ladder to reset the current wipe data, lifetime ladder is not affected. I will release an update to fix this later today. you can disable it for the time being.
-
@muhendisbeyhi, you need to update. @KingSizeKevinyes, you can set the stacksize in the loot table itself. { "shortname": "explosive.timed", "name": null, "blueprint": false, "skin": 0, "amount": 18, "amountMin": 18, "probability": 1.0, "stacksize": 6 },
-
@HunterZ the pvp delay will not expire until its duration has elapsed. that option has no bearing on it. it is there so that if the base despawns then the fight can continue until pvp delay expires. though as I mentioned it will not work if there are no events remaining after that despawn occurs I will go ahead and make it expire the pvp delay on despawn when that option is false even though its not what the option was initially for, but it is ideal that the pvp delay expire when the base despawns since it would have no functional use when that option is false
-
ok, the new hooks look good then @HunterZ?
-
@HunterZ ok, ya, you could use the exited hook, but I will add a hook when it resets the delay time. I just realized there is no hook when PVP delay starts, except from OnPlayerExitedRaidableBase like you suggested but it should have its own dedicated hook so ill add that too. lol no, it expired for me private void OnPlayerPvpDelayExpired(BasePlayer player, int mode, Vector3 v, bool pvp, string id, float a, float b, float c, ulong ownerid, string basename, DateTime spawn, DateTime despawn) { Puts(player.displayName + " delay expired"); } @Rustalia heya thanks for the compliment. it adds points: 1. when the event is completed which is when it is looted (and the amount of loot required is shown on the status UI inside of the event), or 2. if you change it to use Destroying The Cupboard Completes The Raid then it will add points at that time too, or 3. if you use Required Loot Percentage For Rewards and use Destroying The Cupboard Completes The Raid then it will add points once the required loot is met. winners are anyone that actively participated in the raid. Each Player Must Destroy An Entity For Reward Eligibility can further enforce this requirement. participants is anyone that uses explosives, fire, melee weapons, explosive ammo, anyone that loots a box, anyone that destroys an entity, and anyone that kills an npc.
-
@HunterZ PVP delay was changed to prevent an exploit. players will get PVP delay when engaging in PVP, and when leaving the event now. I can implement something if you have a suggestion. OnPlayerPvpDelayEntry is called on entry as intended, but it's not checking AllowPVP is true which is not intended. I don't know why this hook exists as it's useless. it's only purpose is to inform you that PVP delay is enabled in the config which is odd at best. it's the same exact hook as OnPlayerEnteredRaidableBase otherwise. I am going to remove it unless you have a use for it. OnPlayerPvpDelayExpired won't get called until it expires. if you want it to expire immediately on despawn then that can be implemented. PVP Delay Between Zone Hopping Persists After Despawn allows anyone still with the pvp delay to continue fighting until it expires. it will not work if all events are despawned though, because the hooks are unsubscribed when there are no events. I am seeing an issue with the UI not displaying the PVP delay some times though, which I will fix
-
@BetterDeadThanZed you can, configure profiles as PVE or PVP with the Allow PVP setting, but you have to set Convert PVE to PVP to false so it doesn't override it otherwise no. I can add the options next update
-
@BetterDeadThanZed heya, is this in the profiles not sufficient? they wouldn't be able to buy without the perm "Permission Required To Enter": { "Buyable Events": "", "Maintained Events": "", "Scheduled Events": "" },
-
@Vinni P. heya, that is because Allow Players To Build is set to false in the config file
-
ya. you need to update the plugin to 2.8.8 too [Info("Raidable Bases", "nivex", "2.8.8")] this is in the RaidableBases.cs file. if you see 2.8.7 then it's not updated
-
@Kaustic Rust, Oxide and the plugin all need to be updated for it to compile if steam isn't updating then use validate on it to force it.
-
@stev61 hi, it requires the Rust update to compile. it is available now.
-
@NoxiousPluK if someone authorizes that doesn't have that permission then it could convert. the exclude permission does as the name implies, it is excludes you from the search and only includes people without the permission. however, if EVERYONE has it then it is safe, but still not recommended as that is prone to user error. if you are certain this won't happen then you can use exclude and ignore the comment below. it is intended to use abandonedbases.immune for full immunity. anyone with this permission will protect the entire base. it can be a problem if you have plugins which automatically grant authorization to TC though. @Dead Nasty- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@PistOffBastd yup, it's noted down. I just need to figure out how to implement it so that it's not repetitive or annoying. @Marty852 yes, it would prevent you from repairing the weapon. it will not break it in 1 hit though. it will simply put the durability back to what it was, and it could break per normal vanilla. breaking in one hit would be caused by a conflict with something else. @Dead Nasty under Marker Name, but that's for the Abandoned Bases plugin not this one
-
2.1.4 has been released with support for Legacy Shelther, colored domes, UI to show time when TC is opened, support for multi-TC bases, and more. enjoy
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
2.8.8 has been released, enjoy this requires the Rust update to compile
-
@Dr.D.Bug no worries. config has a setting for Spawns Database file. if the file is drdbug.json then put drdbug only. this will work for bases of that type (maintained, scheduled or buyable) alternatively this same setting is available in the profiles if you want to use it for a specific profile instead. spawn points still need to be unobstructed though.
-
@HunterZ hi, this isn't intended. I will have this fixed in tomorrows update
-
@Marty852 heya. you can try disabling this in the profiles, Block Plugins Which Prevent Item Durability Loss I don't remember which plugins were causing this though
-
please note that all hook signatures will change in the next update and are documented now these changes should make it easier for developers to use
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
