nivex
-
Posts
5,154 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
i was not able to strike the base with Allow Players To Use MLRS set to false as seen by the "You are not allowed to target this location!" messages next i moved the strike zone outside of the boundary, and the impact area was not close enough to damage the base either which you can see by the dust cloud in the center of the image so it may be SkillTree or something else, but we've tested it before and it worked just fine with that too verify that Allow Players To Use MLRS is actually set false in those profiles, and that the difficulty is set properly (very first setting of each profile) too -
@Stark ill check it out
-
i'll have to add more specific messages for these issues then =p
-
@406_Gromit haha that sounds awesome. how is it on performance though?
-
make sure difficulty is set properly in each profile, oxide/data/RaidableBases/Profiles/ otherwise either install the copypaste files, or if they exist then add them to the profiles if using my package then just reinstall it if you can't figure it out.
-
no problem enjoy!
-
Changed Status from Pending to Closed
-
no problem glad it works and that you enjoy the help. have a nice day.
-
@Stark you create your groups in the Better Chat plugin you assign my groups to said Better Chat groups my groups are raideasy, raidmedium, raidhard, raidexpert, raidnightmare you then assign your title in the Better Chat group setting once you've done this save it, then add yourself to a group to test. o.usergroup add nivex raideasy type in chat. if you did it correctly then you will see the title. from this point the plugin will do this automatically based on your Ranked Ladder settings in the raid bases config file
-
what does it say when you try to load it? there is no compile issue with 2.7.2 check the .cs and verify it says 2.7.2 and not 2.7.1 if it says 2.7.1 then you did not clear your browsers cache properly
-
alright try this. if i did it right then during the day and night it will allow at raidable bases: 1. raiding 2. pvp at pvp bases 3. pvp if flagged with PVP Delay Between Zone Hopping NightPVP.cs
-
no such error, clear your browser cache and download again
-
if you only have easy bases spawning then you need to configure the difficulty setting in each profile again i do not know why this happens - i didn't change anything regarding it that i'm aware of oxide/data/RaidableBases/Profiles/ very first option is difficulty setting.
-
@Rubiks-Q-Bert yes, sorry, I fixed CopyPaste in 4.1.36 so you can use that and Raidable Bases now.
-
@Stark you may need to type /rb wipe because the plugin did not load with the server startup when the server first wiped. it won't know that you wiped if the plugin isn't loaded. that command will award players their titles too. just make sure Ranked Ladder -> Enabled is true first. ya you can spawn as many as you want. but it will hurt performance if you spawn too many. 80 is quite impressive @406_Gromitwhy do you spawn so many btw?
-
hm, set the difficulty in each profile again. I must've broken it somehow. this is the 4th complaint about it. that should be all you need to change. oxide/data/RaidableBases/Profiles/ first line in each file
-
you can enable Always Maintain Max Events, and set the player limit to the desired value.
-
its a bug with that plugin and it has not been maintained for 4 years i have tried to fix it for you but i do not support this plugin. i am only trying to help you. download the attached version of NightPVP.cs below NightPVP.cs
-
clear your browser cache and download it again
-
@Emigo no, they can move the ui by clicking the arrows in the top of the ui
-
Changed Status from Pending to Closed
-
no problem. ive already added a null check for you anyway.
-
does reloading fix the issue?
-
"Buyable Events": -1, set all 5 of these settings back to 0 I forgot to fix it
-
no problem as i stated in the rb thread there is an issue with copypaste so i advise not using either plugin until the issue is fixed. seems to be an issue with Rust or Oxide
