nivex
-
Posts
5,564 -
Joined
-
Last visited
-
Days Won
193
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
heya, either the nighmare profile is set to easy, or the base is in a easy profile by default, easy is level 0 nightmare is level 4
-
hi, that option despawns loot bags dropped from containers when the base despawns but not before then
-
hi, I don't know what it is that you're asking Custom Buy Raid Cost has payment set to use scrap, not gold coins. The skin is 0, and there is no name configured with either. If you set a name and your currency has no name, then it will not work. If you do not set a name and your currency has a name, then it will not work. If you specify the wrong name, then it will not work So, if the currency has a name, then set it to the exact name of the currency. If the currency has no name, then don't set a name example (change the name to your name, and the skin to your skin) "Enabled": true, "Item Shortname": "scrap", "Item Name": "Gold Coin", "Amount": 100, "Skin": 3486046244
-
heya NivexPoolReset.cs commands are np.info - use this when you notice the issue, if ItemsInUse is in the negative then a item pool issue np.reset - you can use this to reset when ItemsInUse is in the negative, but it will just occur again until you remove or update the plugin causing it. for an item pool issue, you must either restart the server or use this command to temporarily fix it. if you remove the bad plugin then it will not happen again. if you remove the wrong plugin then it could take upwards of a day to notice the issue again. if this is caused by a plugin deleting the loot instead, then that requires its own separate steps. the above will not help with that. I seriously doubt a plugin is removing the loot though.
-
hi, that is caused by another plugin. it is a item pool leak, or a plugin outright deleting it. serverrewards had this issue but fixed it long ago so it would be something else this time.
-
hi, youll have to show me the config. are you talking about payment using items?
-
hi, Convert PVP to PVE is still set to false under Maintained Events Scheduled Events: Not enabled (line 464) but you have wipe hours and PVE configured properly Maintained Events: Set to spawn 50 bases (line 434) Only 5 out of the 50 are configured to spawn (line 63) No wipe hours are configured (line 435) Set incorrectly to spawn as PVP (change line 450 to true) Buyable Events (line 412) 1 base is allowed to be purchased (line 416) Allow Players To Buy PVP Raids (line 413) is set to false when it should be true, the bases are not going to be PVP because they're being converted to PVE. Convert PVP to PVE (line 425) is set to true, so again, there's no need to block PVP raids when you have no PVE profiles. Using a convert option doesn't make a profile PVE, it makes the event type PVE where you configured it. If you want a profile to be PVE then change Allow PVP to false in the profiles, but there's no reason to do this until you have PVE and PVP profiles. That is what the Allow Players To Buy PVP Raids option exists for, to distinguish between the two. Otherwise, Convert PVP to PVE will always override Allow PVP. Only a permission or Chance To Randomly Spawn PVP Bases can override a convert option. Yes, a very complicated but feature rich plugin
-
that's fine, but partial configs aren't helpful if you're still having issues, I'd need the full config. its a few settings to get it all PVE for each event type
-
@Trick hi, I would need the full error. that alone only says there were errors but not where it came from -
hi, use the convert options in the config. they're under each event type, Buyable Events, Maintained Events, Scheduled Events and if you are spawning by command then you must set it under Manual Events too. "Convert PVE To PVP": false, "Convert PVP To PVE": true, maintained and scheduled events have another option, leave it at 0 "Chance To Randomly Spawn PVP Bases (0 = Ignore Setting)": 0.0,
-
I don't think I can help you with that. it's more likely that you have a plugin causing the issue, there should be no reason that the game would fail LoS checks. something would have to break physics or use its own target selection and shooting
-
@ROCKETBOT SERVERShi you need to update the plugin
-
heya, body bag does not disappear. it turns into a backpack and is ejected 5 meters outside of the event. if messages are enabled you will get the EjectedYourCorpse message, and it's drawn on your screen if Draw Corpse Time is above 0 (it's 300 by default) Eject Corpses From Enemy Raids Eject Corpses From PVE Instantly both of these are in the profiles, oxide/data/RaidableBases/Profiles/ if this doesn't happen and your loot is truly disappearing then that would be some other plugin
-
hi, not sure. RB doesn't select the target or shoot the gun. physics would have to be broken to shoot through the ground, or caused by another plugin. RB only allows the targeting and the damage. the game is supposed to handle the selection and shooting.
-
Changed Status from Pending to Closed
-
@Sollerand others Fixed "finish your last raid" messages, player lockouts and related issues in 3.0.9 !
-
@SirApesALot I created a base, built a window frame, added a door shutter, added a door controller to the shutter, deployed a test gen, wired up the door controller, closed the door shutter that sprang open after being wired, copied the base, spawned it with RB and the shutter remains closed. I guess you'll have to send me a base with this issue
-
@Kaustic @Nubie ya, increasing Max Amount Allowed To Automatically Spawn Per Difficulty will work, but make sure you increase Max Maintained Events to the total of those too. don't set Chance To Automatically Spawn Each Difficulty to 100 each. that will work, but it is not how it should be configured. the total of all difficulty should be 100, and if you want every difficulty to have an equal chance then leave each option at -1
-
@Soller i commented on this already
-
@Soller hi it's in seconds I know, it's annoying that some are minutes and some are seconds. just assume seconds if it does not state minutes instead
-
@Kk @SirApesALot @VENIQQ @Elke Mahy and anyone else... Im aware of the issue about raids that players didn't start. I'll check it out. dont open more tickets about it thanks I think this is caused by Facepunch reusing an npc userID when the NPC dies. that can be ANY npc on the map lol.
