nivex
-
Posts
5,303 -
Joined
-
Last visited
-
Days Won
184
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
heya, these are in the profiles, not the config 1. Look for the block damage outside options, and prevent npcs from leaving the dome. set true, Block Damage Outside Of The Dome To Npcs Inside set true, Block Damage Outside To Npcs When Not Allowed To Leave Dome set false, Allow Npcs To Leave Dome When Attacking set false, Allow Npcs To Shoot Players Outside Of The Dome 2. Yes, but adjust this with caution. Setting it too high will cause turrets to shoot very far away, 45 meters is more than sufficient leave at default 30, or increase to 45, Sight Range if you set this to true, then it can double (eg: from 30 to 60) when attacked by players, Double Sight Range When Shot these are all in the profiles, oxide/data/RaidableBases/Profiles/ I'm glad you enjoy the plugin
-
Hi, I can't really tell from the photo, but it appears to be a vanilla feature
-
@KingSizeKevin hi, I'll have it fixed next update thanks -
There are multiple tools available (RB loot table editor, and various websites) to help you with removing paid content. In the next update, I will have two additional ways to handle this for Raidable Bases: An option, which is enabled by default, and will remove paid content without modifying any files. A command, generated at random, that will permanently remove all paid content from your copypaste and loot table files. The command name is randomly generated and stored in the configuration file. Only those with access to your configuration files will be able to see the command name. This can be used as a server command, or by those with auth level 2. It will never be permission based. Example output with tier 1, tier 2 and tier 3 packags installed.
-
@SunShine ツ heya, yes. there will be a new option in RB, and several developers have website tools. see the above responses where it's discussed at length already
-
@Dead Nasty Hi, sorry but no, there's simply too much bloat with cooldowns as is and you'll need to cap it with the cooldowns and lockouts instead. If you set it to every 24 hours then that's once per day. Set it to every 12 hours and that's twice per day. You'll have to make do with this. If I can reduce the bloat of the code, then I'll reconsider it, but not right now.
-
@Amadeus.pve Hi, do not worry, turrets will be addressed in the next plugin update. All paid content will be blocked from spawning by the new option until Facepunch is able to clearly outline specific exceptions. I've asked them to comment further on this, but haven't gotten a response other than to wait for the dev blog.
-
@Amadeus.pve Hi, no, you cannot keep paid content. Free content is still allowed. Use Random Skins spawns free content. Use Workshop Skins spawns paid content, and will be disabled in the next plugin update.
-
@Dead Nasty To clarify, this tugboat was the event? It could be the float to shore code implemented by Facepunch Test by setting the do_shore_drift convar to false, then you can enable it again afterwards If so, it is an easy fix but don't want to go down a rabbit hole trying to figure out what it is if you can confirm with the convar first -
A new option will be added in the next plugin update, to be released before the game update—enabled by default—will block paid content: Paid items from copypaste files (these will be automatically despawned) Paid items in loot tables (they will be skipped in favor of non-paid content) Paid skins from copypaste files (these skins will be removed) Paid skins from any file within the RaidableBases data folder Moving forward, only non-paid skins should be added to either ImportedWorkshopSkins or SkinsPlugin files in the RaidableBases data folder. Paid skins are not allowed when this option is enabled. Note: Third-party plugins may bypass these restrictions. This option will attempt to block pickup and looting in such cases. Be sure to only use plugins that comply with Facepunch’s Terms of Service. It remains unclear what exceptions are permitted, so these restrictions will remain until Facepunch can respond with an official statement clarifying what is allowed.
-
@Grumpy Old Man Hi, this is discussed at length above, and is in the top of the plugin's documentation. Yes, there will be a new option (DIsable Paid Content in the config) but it is still your responsibility to remove any paid content from the files on your server. You can already disable "Use Workshop Skins" setting (boxes, npcs, loot items, and deployables) to prevent workshop skins being applied. This will not remove any skins already in your copypaste files. It prevents new skins from being applied only. My tier packages will be updated when I have time. Stay tuned.
-
@miniMe_rust Hi, I will provide an update to include new items which are missing from the loot tables, and to provide additional loot tables that do not include any paid content in them. Though anyone not wanting to update to the new package will not have to do so. Removing the paid content without updating to the new pack will not result in less loot spawning in bases if "Allow Duplicate Items" is still enabled, it will still ensure the correct amount of loot is generated. It will be possible for the Raidable Bases plugin to filter out any paid content using a new option that will be added in the next plugin update. The plugin update will be released before the game update. My warning in the documentation, in short, explains that this might require more than one plugin update to fix any issues with this option or otherwise. -
For those that want to remove paid content from your loot tables so you can comply with the recent Facepunch TOS changes, @beee has updated his editor with an option to do this. I recommend his editor for ease of editing loot tables, which he continuously updates. Please, show your love and support for his work if you like it. Open your loot table, right click in an empty space under LOOT TABLES, and choose "Delete all DLC items" or "Delete all prohibited skins" Please understand that you must verify nothing was missed. https://codefling.com/tools/raidable-bases-loot-table-editor
-
@Tay Hi, Player Lockout, hard to say without seeing your updated configuration. If you see no UI then you do not have a lockout, the base has not despawned yet, or you have Lockouts UI disabled in the config. The UI shows after the base despawns. When a player tries to enter a raid while having a lockout, they are forcibly ejected and messaged with the time remaining of that lockout. If this does not happen then you are using vanish, noclip, do not have a lockout yet, or have a lockout for a different difficulty. Lockouts are applied after the base despawns. If you're receiving two messages then you've enabled two options to do this. Such as having both "Notify Plugin - Type" and "Send Messages To Player" enabled. "Send Messages To Player" will cause Raidable Bases to send messages. Enabling Notify Plugin will cause that plugin to send a message, or notification, depending on the type. Type 0 is message iirc.
-
@Cargonia Ah, they have sphere in both of the names because they're spheres from the SphereEntity class with sphere in each of the prefab paths. I use a combination of these prefabs to create each available color, which is why the name is Sphere Colors "assets/bundled/prefabs/modding/events/twitch/br_sphere.prefab" "assets/bundled/prefabs/modding/events/twitch/br_sphere_green.prefab" "assets/bundled/prefabs/modding/events/twitch/br_sphere_purple.prefab", "assets/bundled/prefabs/modding/events/twitch/br_sphere_red.prefab" Ok, let me know if you have the problem and can provide the exact message next time. Screenshots are best
-
@Cargonia 1. I don't know what you're referring to, sorry. Domes and colored spheres are separate options, and do not require the other option to be enabled/used. 2. No, Prevent Players From Hogging Raids is the option for Maintained/Scheduled Events that will prevent him from doing another raid when he is still part of an existing raid that hasn't despawned yet. There are other options, but again, he would have received a message about what prevented him from joining another raid. I need to see that message to know exactly which option it is.
-
Hi, When it pertains to other plugins, some developers have implemented functionality so that paid content is only given to those that own the content. This is not practical with Raidable Bases. The plugin closely mirrors raiding found in normal gameplay, where many issues make this feature impractical. Namely, such content could easily be distributed by the owner to players that do not own the content. Either by invitation, or acquaintance (team mates, clan members, or friends), and when events are not locked to players. For these reasons alone, you should remove any such content from your files. I can add an option that does this, but it will likely require updates to fix any edge cases. You should not rely on such an option due to this. You can add unapproved (non-paid) skins manually to your ImportedWorkshopSkins.json file found in the Profiles directory, which has an example provided already. (oxide/data/RaidableBases/Profiles, or for Carbon users this can be found in carbon/data/RaidableBases/Profiles) @ninco90 has created a tool to help with this which he has posted about above. He’s still actively working on this, so please be patient while he fixes issue with it. https://app.rustspain.com/facepunch/checkitems
-
@Dead Nasty Generally if the tugboat acts strangely like this then it has something parented to it. It might be due to doubling up of map markers, so you could try disabling them in the Abandoned Bases plugin to see if it still happens. I wouldn't know otherwise.
- 594 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
Hi @Tay Owners are assigned based on participation, not when you enter the event. This requires: Looting Killing an NPC Destroying a part of the building Using explosive ammo, explosives, or melee weapons Some options require you to be inside of the event. If this doesn't happen, then it's not enabled to use an owner in the config, or there's some miscommunication. Hi @Cargonia You can use Sphere Colors in the profiles. Use the "When Locked" and "When Active" options. oxide/data/RaidableBases/Profiles/ As for the lockout, no, he would not be blocked under those conditions. If he owns another raid, he can be blocked. If he is participating in another raid, he can be blocked. If his raid has not despawned, he can be blocked. These all have messages that he would've seen if they were enabled, which they are by default.
-
No worries, it's good to discuss important issues like this
-
@ninco90 Thank you for your help and contributions to the community, it is greatly appreciated.
-
@PhatBlinkie hi, sure, I can change it so they're not required to be online/alive anymore.
-
@Tay in most cases, 1. vanish or noclip, 2. if he owns a base elsewhere 3. if he's participated in a raid elsewhere 4. if he has a lockout otherwise, I would need more information.
-
@Tay Timers start when the event despawns, not when it's completed. It's intended to work this way, and depending on the configuration, to block them from raiding other events when they still have an event spawned already. Bases should be copied while standing and looking at the center foundation. Use /paste to verify the /copy worked properly.
-
@Tay If you set 60 minutes with a Buyable Cooldown, then players will not be allowed to BUY the same difficulty again until that time elapses. This does not prevent them from entering any raid, public or purchased. There is no option to block their entry since they or a team mate are required to buy the event first. If you set 60 minutes with a lockout from Player Lockouts, then players will not be allowed to ENTER or RAID the same difficulty again until that time expires. Player Lockouts will not block players from entering purchased events, applying only to Maintained or Scheduled Events. If this is not working, then you've given permission that is bypassing it, or it is not configured.
