nivex
-
Posts
5,391 -
Joined
-
Last visited
-
Days Won
187
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
hi, edit the profiles, oxide/data/RaidableBases/Profiles/ change Despawn Dropped Loot Bags From Raid Boxes When Base Despawns to true
-
Items in lockers not included in the loot count
nivex replied to LandOfTheBlind's Support Request in Support
hi, not bugged. if you want lockers to be included as part of the box/tc requirement then you would need to add "locker" to Additional Containers To Include As Boxes "Additional Containers To Include As Boxes": [ "locker" ], like this -
hi, remove them from your loot tables. oxide/data/RaidableBases/Base_Loot and oxide/data/RaidableBases/Difficulty_Loot they should only be in the latter should delete the oxide/data/RaidableBases/Default_Loot.json if you haven't already.
-
@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 -
installed to where? I see no file paths. if it were installed then it would load every loot table when the plugin loads, but it loads the default file only so it is either installed in the wrong directories or your host does not have permissions configured correctly and you would need to contact them so they fix it on their end
-
@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
-
i said its in the config
-
that's not an error, and it is from RustCore. ignore it
-
you need to install them then there's no info to go off of here. I don't know what you have done and installed theres no loot tables installed theres no bases installed are there any profiles installed? what have you done
-
heya, use the rbe debug command. you can type it again to toggle it off.
-
Alpha Loot is for Loot Containers, not Storage Containers, so it can't work all resources should go into the TC. you can disable moving items to TC in the config, or you can blacklist which items you don't want going in there Move Resources Into Tool Cupboard Resources Not Moved To Cupboards
-
hi, this mean the stacksize will be ignored and it will use the servers stacksize instead.
-
hi, no, everything spawns into random containers. you can specify some options but not that.
-
I don't like how annoying it is that everything is above all windows anymore than anyone else, but nothing can be done about it. it used to be below the inventory window, and that caused even worse problems with other windows. we're limited to use "Overall", "Overlay", "Hud", "Hud.Menu" and "Under" layers. i've tried all of them, and changing the layer from "Overall" or "Overlay" to anything else will cause all raid windows to go behind chat, hot bar and metabolism windows should any player decide to move a raid window there. then they wouldn't be able to interact with that window anymore. if i leave it as is then you can't interact with the game window that's being covered up. this isn't a problem because you can move the raid window wherever you want. you cannot move the game windows. so it only makes sense that raid window be able to be moved at all times. when a better solution is available then it will be implemented. anyone who tells you otherwise should be ignored. they don't know what they're talking about. none of this applies to the buyable window however, because it enables your mouse cursor. this is key to understand for anyone reading this. I will set the buyable window back to Hud.
-
Changed Status from Pending to Closed
-
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
-
Changed Status from Pending to Closed
-
@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 =\
-
player.State.pointsOfInterest?.Remove(note); note.Dispose(); player.DirtyPlayerState(); player.SendMarkersToClient(); if you don't want the marker deleted then you can remove this code from OnMapMarkerAdded private void OnMapMarkerAdded(BasePlayer player, ProtoBuf.MapNote note) { if (player.IsAlive() && player.HasPermission("raidablebases.mapteleport")) { float y = GetSpawnHeight(note.worldPosition); if (player.IsFlying) y = Mathf.Max(y, player.transform.position.y); player.Teleport(note.worldPosition.WithY(y)); } } it should look like this when done i cannot change your keybinds. that is client side. best i could do is require you press an additional key with right-click if i don't remove the map marker then youll cap out and not be able to place any until you remove them.
-
ok guys 2.7.1 released, sorry for the rough update with 2.7.0!
-
cooldown is intended to reset so that it is effectively applied when the raid despawns. this is not configurable, its to prevent exploiting the mechanic and is why it was added lockouts do not reset though
-
awesome good to have a second confirmation!
