nivex
-
Posts
5,681 -
Joined
-
Last visited
-
Days Won
195
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
heya, these are fun. it's the Sphere Colors in the profiles, oxide/data/RaidableBases/Profiles/ they're in pairs. "Sphere Colors (0 None, 1 Blue, 2 Cyan, 3 Green, 4 Magenta, 5 Purple, 6 Red, 7 Yellow)": { "When Locked": 0, "When Unlocked": 0, "When PVP": 0, "When PVE": 0, "When Active": 0, "When Inactive": 0 }, "When Locked" and "When Unlocked" are useful if you lock bases to the player. bases don't lock in PVP by default, so this will not apply to them "When Active" and "When Inactive" are as the name implies, when the event is active or inactive. this will apply to PVE and PVP as it requires no such lock, only activity. if you want PVE and PVP to have the sphere colors then you should configure both of those pairs. there's no reason to configure "When PVP" or "When PVE" when using the other options. just ignore them. these are the only available colors, subject to change only if Facepunch adds more possible colors. so for easy, I'd recommend something like this to be consistent across PVE and PVP: "Sphere Colors (0 None, 1 Blue, 2 Cyan, 3 Green, 4 Magenta, 5 Purple, 6 Red, 7 Yellow)": { "When Locked": 3, "When Unlocked": 0, "When PVP": 0, "When PVE": 0, "When Active": 3, "When Inactive": 0 }, if you want to make PVP distinct from the rest, then you could set it to its own color.
-
@miniMe_rust i feel like most players would vote based on how much they like the base or how easy it is for them, rather than how good the base actually is. this is common enough when watching players, they'll gun for the "easy" bases and ignore anything that isn't time efficient for them, even if that base is well designed. it would be too biased of a system and require a large amount of votes per base to get any real useful data from it. I'll have to pass for now my best advice? pay attention to complaints people have regarding a specific base, and make adjustments to it instead. players can use /rb to see the name of the base. -
hi, i answered that. nothing has changed regarding this. i said you have too many zones. they are taking all available space. please read my response.
-
@miniMe_rust hi, np, I've included the guid at the end of each hook call in the next update Guid guid example private void OnAbandonedBaseStart(Vector3 center, float radius, bool AllowPVP, List<BasePlayer> intruders, List<ulong> intruderIds, List<BaseEntity> entities, bool CanDropBackpack, bool AutomatedEvent, bool AttackEvent, Guid guid) { // attack event means someone started the event by attacking the base with the abandonedbases.attack permission. this will only convert a base when it has become abandoned }- 627 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@miniMe_rust heya, use the vector3 center as the unique ID for bases. use the network ID for tugboats. I can add a guid to the hooks but its really not necessary with those I can add a hook to be called before any ownerid changes. you will still need to get the privs from the entities list. private void OnAbandonedBaseStart(Vector3 center, float radius, bool AllowPVP, List<BasePlayer> intruders, List<ulong> intruderIds, List<BaseEntity> entities, bool CanDropBackpack, bool AutomatedEvent, bool AttackEvent) { // attack event means someone started the event by attacking the base with the abandonedbases.attack permission. this will only convert a base when it has become abandoned } Im glad you are learning!
- 627 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@Ortiga I could add something simple, but that would be about it. it makes sense for it to be in another plugin because of how many hooks there are though.
-
hi, you have 33 zones blocking nearly every spawn point. only 100 points remain when it requires at least 1000 to function. those are clusters and all the zones are blocking them. this has not changed btw. that will vary map to map but your zones are the cause. find zones that are too large and reduce the size or remove them. or, if you want bases inside of some zones then the zone needs to be added to Allowed Zone Manager Zones
-
@Cargonia heya, the default behavior prevents anyone from entering another persons raid. someone would've had to change this, or players were given a permission they shouldn't have such as raidablebases.allow which is for staff/mods/admins. players don't need any permissions by default. these are default: Lock Treasure To First Attacker in the config needs to be true Bypass Lock Treasure To First Attacker For PVE Bases in the config needs to be false Eject Enemies From Purchased PVE Raids in the profiles needs to be true Eject Enemies From Locked PVE Raids in the profiles needs to be true noclip and vanish will bypass
-
@miniMe_rust hi, the hook is called too soon for privs. Ill move it. you can find the privs in the entities list though.
- 627 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
hi, there are folders for the English version and the Russian version in that zip. install the English version. also, please remove that file attachment. you are sharing the paid version with anyone who reads this.
-
heya, if you want to install RU then you need to convert it otherwise install the EN plugin file instead
-
@Hawkhill you can add the skin 10430 to Random Building Skin List or you can configure it under Additional Rust Shop Building Skins in the profile, oxide/data/RaidableBases/Profiles/ "Additional Rust Shop Building Skins": [ { "Name": "Space Station", "Enabled": true, "Skin": 10430, "Grade": 4 } ],
-
@MegaPihar hi, I don't support crates, not yet anyway. players cannot use the spawn command and if they had admin then it's not suitable as it would spawn wherever they are looking. either find a way to copy it with the CopyPaste plugin, or use a command provided by another plugin to give it to the player on event completion.
-
@miniMe_rust hi, it's only called when the base is skipped by an automated event. owners are included in the OnAbandonedBaseSkipped hook. owners are provided for all other hooks too. yes, the owner can be removed from the entity. this is unavoidable when the config option is enabled to remove the owner.
-
@Ryan Branham hi, the only way is if the profile is easy or if the base is in the wrong profile. if both are correct then you have a duplicate that is not.
-
@Ryan Branhamhi, that'll happen when the Difficulty or Difficulty Level is set to Easy to 0 in the profiles, oxide/data/RaidableBases/Profiles/
-
@XiuNooB hi, there is no functional difference that would cause this in free vs paid. I use both, and if configured properly, it will work in both. thanks for purchasing the paid version. if you cannot figure it out, send the files in private. @Alpha28 hi. not that I'm aware of, it uses the rotation in the copypaste file / plugin.
-
@Alpha28 happy new year! the ore is spawned randomly from your loot tables, determined by what ore is in them. bases spawn randomly too, and that includes repeating randomly. if you don't want this repeating, then enable in the config: Require All Bases To Spawn Before Respawning An Existing Base
-
@XiuNooB thats a good amount of items, but my answer above is the solution. it is very easy to check, so dont worry. 1) ensure the 400 items are in the messages when the plugin loads. if true, go to step 2. if you dont see this then you need to fix it. either the filename is spelled wrong or you have a json error. 2) ensure Amount Of Items To Spawn is set high enough. if its at the default of 30 and you have 20 boxes then you will get approx 1 per box, as the TC will hoard some. the amount you have in the loot tables does not determine how many spawn, only that option does. 3) if both step 1 and step 2 are good then its likely a stacksize, in a loot table itself, is set incorrectly aka too low. ex: spawning 1000 hqm in stacks of 1 or 2 or such is very bad. 4) another possibility is lockers hoarding the items. the divide option for lockers should not be disabled. Divide Locker Loot When Enabled, in the config, not the profiles. if you cant figure it out then send me the files in private. i encourage you to learn how to use the plugin by figuring it out yourself though. i understand its a complicated plugin, but those steps are not complicated unless its a stacksize issue. again, stacksize in the loot table, not the servers stacksize.
-
heya, use Enable X Hours After Wipe to configure that per difficulty. it is under buyable, maintained and scheduled events, separately.
-
hi, update the copypaste plugin if using linux, then the libgdiplus library must be installed on the machine by the host (see documentation) otherwise you have some broken copypaste files that need to be removed, but it seems one of the above is the issue. something is missing.
-
Changed Status from Pending to Closed
-
you're welcome, enjoy.
-
hi, Maximum Respawn Npc X Seconds After Death is in the profiles. this determines how frequently they respawn. set to 0 to not respawn.
