crash
-
Posts
378 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by crash
-
Changed Fixed In to 2.0.0
-
Not sure whats ur problem since lack of information sir -
plugin config for deep sea plus
-
Thank you sir, deep sea its changing everyday so its not "stable" lets say it that way lmao
-
whats ur workflow and config?
-
Changed Status from Pending to Work in Progress
-
Hello, please try lastest version
-
Hello, please try lastest version
-
ill look further
-
compiling just right here
-
Hello, is this carbon?
-
Hey, im not sure why i didnt got a notification back then lmao. ill take a look into it -
On any island sir
-
hey, make sure you have both of the following true Control building (enables building controls) Allow building in Deep Sea
-
They would collide yup
-
fixed ^- 115 comments
-
- 1
-
-
- #restart
- #rustplugin
- (and 5 more)
-
Needs an update for March forced wipe game updates
crash replied to SlayersRust's Support Report in Support
Changed Status from Pending to Fixed Changed Fixed In to 3.8.1 -
Needs an update for March forced wipe game updates
crash replied to SlayersRust's Support Report in Support
Hey, on it -
Unfortunately that's not possible with the current setup. The "Disable Native Spawning" toggle is all-or-nothing. it blocks all ore types (stone, metal, sulfur) at once. Your options right now: Closest to what you want: Turn Disable Native Spawning OFF, enable only Sulfur in the plugin, and tweak the biome probabilities down to reduce it. Stone and metal stay fully vanilla. The downside is sulfur will get vanilla spawns plus plugin spawns stacked on top, so it might not reduce it as much as you'd like — it'd actually increase it. Full control route: Keep Disable Native Spawning ON, enable all three ores, and just set stone/metal to roughly match vanilla defaults while tuning sulfur down. Not truly vanilla for stone/metal but you get full control. Neither is a perfect solution for your use case. I'd suggest leaving a new feature request
