-
Posts
4,808 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
hi, good to know that! well, if you are playing as an admin then several things can prevent rewards. 1. rewards are set within the profiles, oxide/data/RaidableBases/Profiles/, so I'd make sure it is configured as expected 2. Remove Admins From Raiders List will have you removed from everything 3. you cannot use noclip or vanish. these abilities are intended to bypass much of the functionality so you do not interfere with players
-
alright, may have a solution. change: to
-
many things in this plugin aren't in default rust, but I did say I'd try to block it =p
-
true, but you can deploy them normally to obstruct entry too I will see if I can block it though
-
@Snaplatack I just got a chance to look at the video you sent me. you can disregard everything I said above. I was mistaken in what you were telling me I thought you meant the ladders were rotating on walls horizontally, rather than being able to deploy them horizontally such as on roofs or ceilings. ya, I think this is fine, unless you see it as a problem?
-
ok. load up Raidable bases and copypaste only and try it out there
-
Changed Status from Pending to Closed
-
hi thanks for letting me know the cause. good luck
-
not necessarily, a plugin can modify the rotation by multiple means such as on spawn. do you have a test server
-
I dont see how that is possible. surely it is a plugin or mod breaking it
-
ok, let's try this then. edit the .cs change line 2365 from to and line 2375 from to
-
I'm not sure how you are able to do this then. is there some new ladder that I'm not aware of?
-
heya. ladders are placed vertically in raidable bases (up and down) which is how the game does it. it should not be possible to place them horizonally (left and right). I tested for you and it functions normally. perhaps you have a plugin altering this
-
if you want to know how much delay a user has then you can use float GetPVPDelay(player.userID.Get()) and the maximum time is float GetMaxPVPDelay() OnPlayerPvpDelayStart is triggered when they leave the event, or when they engage in PVP OnPlayerPvpDelayReset is triggered the same way, but the time is reset instead of the above hook being called OnPlayerPvpDelayExpired is called when it expires the parameters 0, 0, ID are old parameters and I left them in so I would not break plugins using my hooks loadTime is how long the raid took to setup ownerId is who owns the event BaseName is the copypaste file used spawnDateTime is the time when the raid completed setup despawnDateTime is the time when the raid will despawn GetLootAmountRemaining() is how much loot is required to complete the raid (the same amount is shown in the game status UI)
-
@bluelite73 I did find a separate issue in TruePVE and have released TruePVE 2.2.1 it might be related to this issue too. so please let me know if this fixes your issue. I don't think it will help since RB handles the behavior of TruePVE, but it is still beneficial to update TruePVE
-
I tried this on Linux server using Oxide, Windows server using Oxide, and Windows server using Carbon with the same results using molotovs and incendiary rockets spawned in via F1 game console and default TruePVE config with your RB files. server.pve was set to false
-
unfortunately I cannot reproduce this with your config and data files. molotovs and incendiary rockets hurt and continue to burn turrets and boxes as expected can you enable Trace To Player Console in the TruePVE config and try another trace with fire in RB? this is what I recommend to use for the TruePVE config if you see a trace, this means RB is bugged (not TruePVE) if you see no trace still, then we can proceed from there
-
can you zip your RB config and oxide/data/RaidableBases folder and send the archive in a private message?
-
loading truepve would require that you reload RaidableBases to avoid any potential issues. reloading truepve does not require this since it would have been loaded already. there was no trace for the damage so it cannot be caused by truepve. RaidableBases would block it for the above 11 reasons only, or it is another plugin or bug. I can test and see if I can reproduce it.
-
you add it to whichever of the two Marker Name that you want to have it
-
heya. zone pvx info needs to be updated to use the new hook provided by abandoned bases you add the {PVX} text to Marker Name in the config your message shows where it goes
-
@Komorebi heya. there's an issue with your server, but that might be a game bug. SamSite.ISamSiteTarget.serverList should not contain destroyed entities which is why this error is thrown. I can still fix it though. change line 12727 in the .cs file if (server is MLRSRocket || Vector3.Distance(server.CenterPoint(), v) > raid.Options.SamSite.Range) to if (server is MLRSRocket || server is not BaseEntity entity || entity.IsKilled() || Vector3.Distance(entity.CenterPoint(), v) > raid.Options.SamSite.Range)
-
I have never seen such an issue on windows. there were reports of this, but with far less entities. as far as I can tell this is not a plugin bug. very few have this issue. a plugin bug would affect most people and that's not the case. there are no reports of this happening before a server restart though. so there is an easy solution. i suggest unloading the plugin shortly before your scheduled server restarts. this should help avoid whatever issue on your server that is causing it. make sure you restart daily.
-
no problem. please do let me know. I do like to know the most common reasons and issue happens so I can better answer people. this issue does strike me a bit odd though. it still feels like a plugin might be causing it, but if you said not then I guess we will see what comes from your testing