nivex
-
Posts
4,791 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
hello, adjusting Maximum Elevation Level is the reason it is clipping it should never be set above 3.75, it is the literal land level of the surrounding terrain any issue with terrain partially clipping is because this setting explicitly allows it up to the level you configured it to to avoid it you would lower the level, and make sure the base is copied at the correct level to begin with improperly configuring the Height setting can also cause it to clip into the terrain. so can the AutoHeight option, however it is not supported by me as this plugin is always going to do it better when properly configured hope that clears it up for ya. gl!
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
that setting can be bypassed by profile settings. you can disable it in the nightmare profile. it's intentionally enabled because it's supposed to be a nightmare to raid it =P "Require Cupboard Access To Place Ladders": true,
-
@BetterDeadThanZedthats the maximum for everyone -
rubber banding would have time warnings in the oxide logs there's no issue with objects at 0,0,0 anymore. that would be another plugin there is an issue with bases despawning after a restart (fixed by unloading before a restart) but that's unrelated and fixed next update
-
that's not the default files. you put a profile in the base loot directory. =p loot files belong in base loot and difficulty loot folders and these are what you edit. difficulty loot is the primary file. base loot contains a few items that always spawn. they cannot be profiles - they must be loot tables. profiles belong in the profiles directory @Vengadorweb -
@exelonpt "Grids To Block Spawns At": ["A2", "AA1", "Z5"], etc=]
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
hi, this is fixed next update it happens during a server restart. you can avoid it by unloading the plugin before the restart happens
-
it really just varies map to map and what that map can handle. proc gen maps are usually pretty good about being able to spawn a lot of bases, but usually does not mean always the substation monuments really eat a lot of space you'll just have to wait for the next update for that fix, or add it in yourself case "Launch Site": case "Arctic Research Base": return 300f; change to case "Launch Site": case "Arctic Research Base": return 300f; case "Substation": return 35f; also you have the rbe debug command to see why its not spawning
-
@BeePssY yes, you can use the spawns database plugin and just set that filename under whatever event type in the config, "Spawns Database File (Optional)": "none", so if the filename is maintainedspawnpoints.jsosn then you would replace none with maintainedspawnpoints. don't include the .json extension
-
np @Emigo @Tiddy oh so I gotta do it. lol. ok ill try
-
@Tiddyit looks nice! can you have it scale down the size so it doesn't include lockouts with no time?
-
Changed Status from Pending to Closed
-
@Emigono, but that is fixed next update which will be out soon @Tiddytoo many complaints about users accidentally turning it off. just sick of dealing with that. the ui class needs a rewrite anyway. I would use a better UI yes. I suck at UI. =P
-
it should be fixed next update @chuck norris its most likely topology check blocking it. my bad =p if (!spq.spawns.IsCustomSpawn) { string topology; if (!SpawnsController.TopologyChecks(vector, spq.buildRadius, out topology)) { LastMessage = $"Spawn is on blocked topology ({topology})"; continue; } } this is the fix, the first line with its open and closed curly brackets go around the enclosed lines of code
-
you can look to see which tables didn't load with the plugin to know which are broken
-
actually it looks like 3 of them have the same json error
-
hey. its telling you that one of your loot tables has a json error
-
it is working. minus an issue where heads poke through blocks the npcs spawn fine. this issue is on your end.
-
read the update notes. its pre-release Changed Status from Pending to Closed
-
2.5.0 released you must wait until Rust releases the update! it will not compile until then if you have issues (including previously reported issues) then report them to me again
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
