-
Posts
5,540 -
Joined
-
Last visited
-
Days Won
192
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
@aimacakprobably just buggy. set height back to 1.0 and do not adjust elevation level above 2.5. setting it to 6.5 means it can float off the ground. @byond1991ask again if it happens in 2.6.0 please yes that means 2.6.0 is released and many things are fixed. PLEASE READ THE NOTES I TOOK A LOT OF TIME FOR ALL OF THIS
-
using the colors you posted for the buttons colors and the default white for the text colors, along with the alpha being set to 0.7 here i've swapped the text colors with the button colors, the panel and button alpha to 0.1 and the text alpha is 1.0 (no option to change it) but it is a bit hard to see. so i opted to use bold text instead for better readability either way itll be more configurable
-
@aimacakthere aren't settings for each label text color unless you use contrast, otherwise only the button colors can be changed and Text Color is used for the labels. you're meant to only change the buttons color and have the contrast adjusted if necessary. i will see if i can add support for all labels to use their own color i've fixed the alpha in next update spawning issues are fixed next update. i'm just trying to work out one last issue with the elevation level. you definitely cannot use 4.0 next update.
-
Changed Status from Pending to Closed
-
np, next update will fix quite a few issues with topology checks and Substation monuments blocking spawns too.
-
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,
-
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
-
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
-
Newtonsoft.Json.JsonReaderException: Additional text encountered after finished reading JSON content:
nivex replied to World_Gamerz's Support Request in Support
Changed Status from Pending to Closed -
Newtonsoft.Json.JsonReaderException: Additional text encountered after finished reading JSON content:
nivex replied to World_Gamerz's Support Request in Support
good stuff -
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
-
Newtonsoft.Json.JsonReaderException: Additional text encountered after finished reading JSON content:
nivex replied to World_Gamerz's Support Request in Support
you can look to see which tables didn't load with the plugin to know which are broken
