nivex

@ChardaZAR "Use Workshop Skins": true, These should be set to false in your config, and it will prevent approved skins I don't modify files. So for copypaste files you'll need an option in that plugin, or to remove the paid content manually @Tay Hi, it is intended that admins bypass entry to events with noclip, vanish and permissions like raidablebases.canbypass which are in the documentation Options for cooldowns: Public events: Player Lockouts, none of which are configured by default Purchased events: Buyable Cooldowns, none of which apply a cooldown to admins or admins/staff/moderators that have raidablebases.allow by default

@PhatBlinkie You're welcome, and I understand your frustration. Let's wait and see what their next response is. They're going to clear up some concerns that have been raised. In the mean time, you could try writing your concerns to them. You can use this resource to search for any questionable skins or DLC content. It's still being actively updated to include any that might've been missed. I know it's difficult to use, but might prove helpful when using the search functionality on specific skins. https://api.rusthelp.com/v1/facepunch/skins Make sure you put a checkmark in the "Pretty-print" checkbox.

@PhatBlinkie Heya, thanks for responding with valuable feedback. I can understand that perspective, and it might hold more weight if raid bases were rare, risky or difficult to access. However, in practice—especially on PvE servers—players can freely and repeatedly access raid bases with minimal effort and walk away with a large amount of skinned or DLC items. That kind of accessibility significantly undercuts the value of content and contributes to Facepunch's reduced sales. From a developer’s standpoint, I have to consider both the player experience and the broader impact on Facepunch’s monetization model. Given how widely used this plugin is—and how easily it enables access to premium content—I think it’s reasonable to expect Facepunch would take issue with that. Personally, I’ve never supported the idea of plugins handing out paid skins or DLC content freely. These features were implemented purely in response to community demand. At the end of the day, I build for you—the community—but I also have to respect the boundaries set by the game’s creators.

Heya, I hope this message finds everyone well. Please help spread the word should someone ask about this. Please ensure that any paid content, DLC items or workshop skins, are removed from your files to avoid breaching the recent Facepunch TOS changes. I’m working on a solution, but I can’t promise it will be flawless right away—expect a revision or two to resolve any edge cases. Realistically, the first iteration may just offer a blanket blacklist for all DLC and workshop skins—we’ll see what happens. Unlike solutions already implemented by other plugins, RaidableBases has multiple other issues to account for: Players looting and moving items, where some player might try to loot content that they do not own. This can happen under several different conditions, and would require another hook that which impacts performance. Skinning items for public events, where the owner is not set beforehand. This seems easy enough to solve, except the fact of the first issue. Skinning items for purchased events, where the owner is determined beforehand, but it's unclear if it would be in violation should other players join after the fact, when they do not own the same content. Items contained in your CopyPaste files (oxide/data/copypaste or carbon/data/copypaste), which could violate TOS when players do not own that content. Direct item spawns from other plugins, and more. Ultimately, it’s each server owner’s responsibility to keep their own files in order. I know it can be a time-consuming job, but that’s simply part of running servers. Facepunch is right to tighten the rules, even if enforcement won’t be simple. The sooner we clean things up, the fewer headaches we create for them—so they can focus on making new content and fixing existing content, instead of policing avoidable TOS violations.

@Cargonia heya, it will be fixed next update. the prefab name was changed from frontier to legacy. if you want to fix it now then change "assets/prefabs/building/wall.external.high.frontier/wall.external.high.frontier.prefab" to "assets/prefabs/building/wall.external.high.legacy/wall.external.high.legacy.prefab" in the .cs on lines 7235, 7242 and 7245.

@devnull I don't know. that's not my plugin, but if it still uses the PVE hooks then it should.

@mikezexter hi, 884 is a bit low for points so you will start running out of space fairly quick. disable Allow Raid Bases On Beaches in the config and theyll spawn more inland. note this is on the beach, not on the water, which Water Settings are in the profiles Allow Bases To Float Above Water, set false Maximum Water Depth Level Used For Float Above Water Option, set to 0 Prevent Bases From Floating Above Water By Also Checking Surrounding Area, set true