-
Posts
5,342 -
Joined
-
Last visited
-
Days Won
185
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
you're welcome. good luck, and nice job delving into it. it can be fun to figure it out if you think of it like solving a puzzle instead of cleaning up a mess.
-
Stopping difficulties from spawning makes them not purchaseable
nivex replied to Bear Grills's Support Request in Support
Hi, it's possible. I can create 2 options for the "Can Spawn On" days and fix one for buyable, and the other for the rest. -
Ah, well, you can ask the CopyPaste dev to see what might be going on then It has to be something simple then. I don't think you would need to recopy your bases (yet) if old and new have the wrong size. Did you try without any other plugins, only CopyPaste?
-
heya, welcome back! try /paste on a base known to have the issue (if you're unsure what the name of the base is then use the /rb command, look at the base and you'll see it's name with other information drawn on your screen) if the base is brand new and the dimensions are wrong, then it’s likely the CopyPaste plugin. if the base is old and it’s broken, do this: create a new base with the same picture frame, copy it, paste it down, and compare. if the new base works fine, then your old base was the problem. if the new base shows the same issue, then it’s most likely the CopyPaste plugin. if it is the CopyPaste plugin, there are two common reasons: Facepunch updated the dimensions and the plugin hasn’t been adjusted yet. _signSizes in the .cs file doesn’t include the dimensions for your picture frame. to check, open the .cs, search for _signSizes, and look through the list of items with their shortnames. if your picture frame is listed, its dimensions might just be wrong. if it’s missing entirely, that’s your culprit.
-
heya, I can't say without your config file. TL;DR, it's likely your config as your map has an abundance of available spawn points given how flat some of the areas on your map are. you've likely changed the biome settings, or have forced everything elsewhere. General information - Map Terrain Flat terrain only, I do not support spawning bases on bumpy terrain—design them on flat terrain only. Fortify on Steam is perfect for this, and there are plenty of bases available there. Be careful when downloading bases from ANY source: vet them first, and remember that bases are not all designed equally. Stability can be shaky in some, causing them to crumble as they paste in. Inventories may contain items the designer forgot to remove. Worst of all, some bases aren’t copied properly from their centermost foundation—copying at the wrong height can make them spawn below the map or way above it. If you look at the ground, paste it in, and it appears elsewhere, it was not copied properly. Recopy it—don’t rely on ANY height settings in profiles! Those settings are for MINOR adjustments, not for bases that got yeeted halfway around the world. If the plugin is ignoring terrain, it's usually due to one of three reasons: The terrain is not flat enough for bases to spawn on- bases should be designed on unobstructed flat and equal terrain. You've modified a setting in your config or profiles, use compare in Notepad++ or diff on the default config file, and your config file, and see what changes are different. This is the EASIEST way to see what you've changed! The spawn point is blocked by a worldy or invisible entity. Just because you can't see it does not mean it's not there. RBE DEBUG (see documentation) exists solely so you can spot issues like this on-the-fly. Understand that debug contains GOOD and BAD information, use your common sense to narrow it down weighing the highest number occurrences of BAD debug at the most likely causes. Easier than it sounds. No worries. If your map’s terrain is bad, you’ve still got options: the beach, the water, or custom spawn points. Shagadelic, baby. Custom spawn points - use Spawns Database plugin, create spawn points yourself, and put the name of the file (eg: nivexspawnpoints10 - note that .json is NOT appended to the end of the filename, do not append it, using the filename without its path or extension as I've shown) in your config OR profile (not both, highly recommend profile only). Allow Raid Bases On Beaches - in the config, not the profiles. This is for the beach and all beach terrain under the water within its vicinity, usually a very short distance out from the shore. Water Settings - In the profiles, not the config. Highly recommended: Water is abundant in the ocean, surprise! Enable within your profiles, force them on top of the waters surface. Highly recommended for maps with bad terrain. Allow Bases To Float Above Water: true Chance For Underwater Bases To Spawn: 100 Spawn On The Surface Of Water: true Ignore Land Level On Seabed: true Prevent Bases From Floating Above Water By Also Checking Surrounding Area: false Maximum Water Depth Level Used For Float Above Water Option: 1 Minimum Water Depth Level Used For Seabed Option: -20 (forcing the spawn points AWAY from the shoreline) Keep these settings enabled (true), knowing that changing them can and will break the plugin depending on the maps you use. Some maps may embrace these changes, while others will feel like a distant echo—terrain reduced to nothing, the memory abandoned entirely, lost to the abyss for all eternity. Just kidding—use the damn water settings and quit pouting. Bad spawns are notoriously brutal on custom maps. Allow Raid Bases On Beaches Allow Raid Bases Inland Allow Raid Bases On Building Topology Enable (true) these settings if you're in desperate need of more spawn points: Allow Raid Bases On Roads Allow Raid Bases On Rivers Do not use these options if you have high traffic on railroads Allow Raid Bases On Railroads Do not modify Allow Raid Bases In Biomes without understanding that disable a biome will prevent all bases from spawning within that biome! Allow Raid Bases In Biomes Arctic: true Arid: true Temperate: true Tundra: true or false Jungle: true or false Last but not least, the most important of them all for anyone not using custom spawn points from Spawns Database plugin (see documentation): The number of potential spawn points is displayed when the grid loads. First, the plugin must initialize, then it generates potential spawn points across your map. Once this process is complete—usually within a few minutes—it will output the results to your server console. If potential points are under 1000, the map has poor terrain, or you’ve disabled too many options in the config. If potential points are above 1500, you’ll have a reliable amount of spawns. This number will naturally decline as players build more bases on the server. If potential points are above 2500 but nothing spawns, your config and/or profiles are set up incorrectly. Read the documentation. Do not disable biome options in the config. Doing so blocks all spawns in those biomes.
-
hi, use the option toward the bottom of the Change Building Material Tier To. HQM, Metal, stone, wood. set one to true and all bases in that profile will be changed to that tier
-
Changed Status from Pending to Closed
-
you're welcome, make sure to keep copypaste plugin updated have fun
-
Changed Status from Pending to Closed
-
good to know
-
yeah, wish I could be of more help, but it just boils down to a conflict with another plugin or some server-side issue. i know, that's vague but I can't tell you without literally logging into the web panel with full access and debugging it myself. that's time consuming. though each time i've done that, in the past 2? years, it's always been one of those two causing it.
-
@Chloe_Glano deployables that are skinned that cannot be picked up are not in violation; they're decorative only. no one should be able to loot an item, or pickup a deployable, if they don't own the skin/dlc. there's a known issue with pickup of skinned deployables not being blocked, fixed soon (you can reload post-restart to temporarily fix until the next restart, too) to clarify: Items are either loose in boxes or on the ground, and deployables are placed in the world by a player (or by a plugin)
-
heya, sure seems like another plugin causing that conflict. i have no other reports of it, though I'm sure others will have same issue if using the same plugin it's conflicting with. could be an issue with your io queue too but doubtful
-
haha understandable, there are over 600 options so that's easy to do !
-
Ah, I see, you can set Requires A Power Source to true under Tesla Coil in the profiles, oxide/data/RaidableBases/Profiles/ the line number will vary, just search for it in each of the profiles.
-
heya, welcome back to Rust! I have not heard of such a problem, make sure you have updated copypaste plugin. if this does not solve it, please specify in detail exactly what issue it is that you are having
-
hi, please see the update notes. this behavior is intended, minus the wallpaper, to comply with the changes to the Facepunch Terms of Service. I make no exceptions to this at the moment (except admins in vanish/noclip can loot, as always). I have posted this multiple times in the discussion tab if you want to read about it in length there. copypaste plugin has its own new options for any base that spawn, to block skins and paid content in its files. I do not block those. everyone is required to use the ImportedWorkshopSkins file if they want skins now, in order to comply with the Facepunch TOS. wallpaper is an issue in truepve, ill release a fix for that when I can
-
hi, the in-game ui shows what's required to complete the raid, including TC even if not a requirement, and items in TC can stack. it does not reflect the loot in other containers. if you want to see the total number of items generated then it will be output in the server console (rcon)
-
not without seeing your files, DM them to me, and please leave this thread closed. config + easy profile + 1 easy base from the copypaste folder.
-
@Tay Hi, I tested those exact steps for you using your config, once with Maintained Events, and again with Scheduled Events. Both times the base unlocks (Lock Treasure Max Inactive Time) after the configured time, the owner's name is removed from the map marker, and I received the lockout. There is no such functionality with purchased / Buyable Events, that was removed. Is that what you're asking about? Your messages are too vague.