nivex
-
Posts
5,932 -
Joined
-
Last visited
-
Days Won
200
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
@ChardaZAR they spawn everywhere. if they're focused more on the beach then its your map. you can disable beach in the config, but if the map is not good enough then you will have issues with bases not spawning -
you have to enable Run Once On Server Startup, or set Run Every X Seconds to 3600 or higher if the time resets then someone is active on the base. it is going to print in chat who that is, too.- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
i can note this down @Adam Lewis depending on how much code it requires will determine if it's added or not
-
use the abandonedbases.convert.nocooldown perm @Architect
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
please don't post the same question multiple times. I answered you on uMod already
-
@Robert Stevens disable it in the profiles. set spheres to 0. there is no way to disable it saying multiple unless you disable one of the vending map markers.
-
@Ondraasek ok, thanks for clarifying. you should mention any issues to the Carbon team and they'll fix them when they can
-
it makes the base raidable after its inactive for the configured time. no loot is spawned. it uses whatever loot the players had in their base, and whatever loot is on the players. it does not spawn loot.
-
@CsaszyKJ those are player lockouts not buyable cooldowns. as for player lockouts you can only receive them when a raid is completed or when it despawns. he received it when it despawned. immediately followed by another base spawning. so while he thought he received it when a base spawned he didn't and it isn't possible. furthermore, he received a second lockout because the first expired right before the base despawned. that is intended. extend the lockout time so that it is longer than the despawn time and it won't happen. as i've already mentioned before i may flag players so this doesn't happen anymore, but its not a bug. @Nakotix @Ondraasek That is an issue with Carbon then, and they will need to address any backwards compatibility issues in their platform
-
@Nakotixtry deleting the language file
-
lower all the font sizes for Buyable Events UI and Status UI to 10 and see if that fixes it. there's no reason this should happen when It works fine on all of my servers. @Ondraasek@Nakotix
-
@Killeroox it works. I just tried it. @Nakotix DM the config and language file
-
i never suggest using "easy" because of language barriers, but yes it should work too
-
@Killeroox buyraid 0 pvp - buys an easy base 1 for medium, etc can also specify buyraid 0 pve
-
@BoyFrary yes, you would use the id number setting it to 0 will allow it to be random per Skins => Loot Items in the config file not sure what -1 would do but looks like it may prevent it from being skinned
-
name - the display name of the item. like turning paper into cash by using a skin and changing the name to "Cash" name "Cash" shortname "paper" skin - any skin to change how the item looks, https://steamcommunity.com/workshop/browse/?appid=252490 amount - max amount - how many of this item to spawn using a random value between min and max amountMin - min amount probability (0.0 to 1.0) - items must be pooled and randomly picked first, and only after that will this modifier determine if it spawns or not stacksize - this option ignores the servers stacksize limit when above -1. if you have ammo.rifle with min/max of 1024 and a stacksize of 256 then you will get 4 stacks of 256. this will count as 4 items @BoyFraryglad you all are having fun with it
-
@The Real Butter I don't know what plugin would be doing that. damage isn't blocked on my end.
-
@CsaszyKJnot possible - the time starts when he buys a raid, is reset when he completes the raid and again when the raid despawns. it effectively begins when the raid ends. a new raid showing up is not going to reset the time. @J2click the arrow and move the ui
-
@Ariola596 "Chat Steam64ID": 0, this is in the config to change the icon. set the image on any steam profile and put that steam id here. you have to edit the language file to change any text messages. you can disable most messages by changing the text to "" you can disable a few specific messages in config under Event Messages, too
-
@aaronman1 yes, it can cause many issues because it is required by Rust to convert byte array to bitmap. you would need to ask your host to install libgdiplus if its not installed though you can safely ignore the RustCore warning. it isn't an error
-
that's not an error, and it is from RustCore. ignore it
-
it works, and that warning is from RustCore, not Raidable Bases
-
@Hawkhill no idea without an error, unless you're using linux and your host didn't install libgdiplus send me the server log in DM
-
@Rubiks-Q-Bert Lockout timers (public raids) - starts when the raid is completed, and is checked a second time when the raid despawns. this time cannot reset itself while active, but it can be applied a second time should it expire before the raid despawns. it was originally intended that the lockout time exceed the despawn time so that this does not happen, but a lot has changed since then so perhaps it should be flagged to not happen now. I don't know that i want to change what everyone is accustomed to though. Cooldown timers are different (purchased raids) - applied for the full duration of the raid and reset when the raid ends. the exploit is buying another raid before the current raid despawns. blocking someone from entering multiple raids is not the same as blocking them from purchasing multiple raids
-
this code deletes the map marker after you place it. if you don't like that then delete the code above in the .cs please don't bother me with this otherwise. there is no good solution that everyone will like. no i cant make you use a different keybind. all i can do is make you have to press a second keybind to use it and thats dumb too. deal with it i guess idk im tired of it already =\
