nivex
-
Posts
5,899 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
@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)
-
@HunterZ np currently:
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@HunterZ sure np void OnPlayerPvpDelayStart(BasePlayer player, ulong userid, Vector3 eventPos, List<BasePlayer> intruders, List<BaseEntity> entities) void OnPlayerPvpDelayExpiredII(BasePlayer player, ulong userid, Vector3 eventPos, List<BasePlayer> intruders, List<BaseEntity> entities)
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@buckaru that's always fun! you can set Convert PVE to PVP for each relevant category to true in the config. make sure that Convert PVP to PVE is set to false. there are many settings which change how the plugin functions. here are some that you might want to set false in the config. you can set these to true if so desired other than that you really need to take a look at each setting to configure everything to your liking. I have tried to make each setting name to be self-explanatory. my use of "Treasure" is a bit confusing, but it means loot and/or base.
-
@buckaru heya. PVP is Player versus Player. like a Call of Duty match where everyone kills each other. PVP is closest to a vanilla experience where everyone fights to take control and raid each other. in raid bases the players would be allowed to counter-raid other players. you should enable Bypass Lock Treasure To First Attacker For PVP Bases in the config to prevent any conflicts with this. PVE is Player versus Environment. like a World of Warcraft dungeon. players would destroy the npc's and loot everything. there is no PVP in these. the exception is that Allow Friendly Fire is enabled in the profiles by default and will allow friendly fire among team mates. however the Clans plugin (and others) can still block this damage if configured, or if it allows the player to enable or disable a separate friendly fire (which will override my friendly fire if it the damage is disabled).
-
@Bear Grills those settings are for lockouts. use these. Lock Treasure To First Attacker Lock Raid To Buyer And Friends
-
@KayKay hi. there's too much load on your server that it can't handle it. you need to reduce the amount of bases, reduce the amount plugins, or upgrade your server
-
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
