Jump to content

nivex

Creator
  • Posts

    5,324
  • Joined

  • Last visited

  • Days Won

    185

Everything posted by nivex

  1. heya, this is known and will be fixed in the next update. thanks
  2. nivex

    noSpawn Bases

    heya. if it is working on your old server then it will work if you copy it over properly to your new server. download from your old server to your computer, upload those files to the new server, and then reload the plugin manually adding is not ideal as you will be missing all of the settings from your above files, and your loot tables. that's why it should be copied over.
  3. nivex

    noSpawn Bases

    sorry, but I am going to sleep. please do not send really, it is quite simple: oxide/config/RaidableBases.json oxide/data/RaidableBases/ you need to copy these files and folders from your other installation over to your new server so that it can work with your copypaste files that you copied over already. then reload the plugin, and that is all you need to do. if you've done it correctly then it will show in rb.config list and everything will work exactly as it did on the old server
  4. nivex

    noSpawn Bases

    hi. no, all files are created by default when they dont exist. it means the files are not where they belong restart isn't needed. just a reload when the rb.config list command shows the raideasy1 raidmed1 etc files then it's installed
  5. nivex

    noSpawn Bases

    hi, it just means it was not copied where it should be either that or you need to reload the plugin if you havent
  6. nivex

    noSpawn Bases

    well you still need to copy the files over to the new server. those are default profiles.
  7. nivex

    noSpawn Bases

    hi, sure np oxide/data/copypaste folder needs to be all.lowercase use the command to validate the profiles rb.config list
  8. nivex

    Raidable Bases

    @Deicide hi, same response, that's caused by an outdated copypaste file. rust has changed horses to the new horse. you can remove the existing horse, or update it to the new prefab. oxide/data/copypaste/ change: assets/rust.ai/nextai/testridablehorse.prefab to: assets/content/vehicles/horse/ridablehorse2.prefab
  9. nivex

    Raidable Bases

    @miniMe_rust thanks, that's good info, and it makes sense why they can walk through in those conditions. i'll see what i can do @Hakkai hi, that's caused by an outdated copypaste file. rust has changed horses to the new horse. you can remove the existing horse, or update it to the new prefab. oxide/data/copypaste/perfecttower.json change: assets/rust.ai/nextai/testridablehorse.prefab to: assets/content/vehicles/horse/ridablehorse2.prefab @Vasilyi Yrupin hi, this is fixed in the next update, in .cs change: s to: if (!Has(entity) && !raid.BuiltList.Contains(entity))
  10. nivex

    Raidable Bases

    @miniMe_rust very strange that the debris spawned after death would have anything to do with physics before death. please let me know if it happens again. I think it is coincidence
  11. nivex

    Raidable Bases

    @miniMe_rust heya, what you're explaining is how it should work. if you disable Divide Rewards Among All Raiders then everyone should get the total reward, not a divided amount. Only Award Owner Of Raid will grant the reward to a single player, the owner, but this is not fair as no one else will get the ladder reward. I don't see a reason for that, so I'll make sure they get the ladder reward next update if that's enabled. you will need to disable Not The Owner under Event Messages or it will tell them they didn't get a reward because they're not the owner.
  12. nivex

    Turrets

    this is the most recent NoInterference.cs
  13. nivex

    Turrets

    yes, that version is very old. what is wrong with it?
  14. nivex

    Turrets

    RB has no interference integrated by default, by the way so a no interference plugin would only help with player turrets
  15. nivex

    Turrets

    i would have to see it chances are its outdated though
  16. nivex

    Turrets

    please let me know what you find out np
  17. nivex

    Raidable Bases

    @Deicide nah, I understand what is happening, but not how
  18. nivex

    Raidable Bases

    @Kaedence what do you mean? this can be configured for that already @Deicide if I could reproduce it then I could fix it but I do not have this issue and no servers I have access to do either
  19. nivex

    Raidable Bases

    @urbanviking i've got several reports of it, but nothing was changed that should cause this.. it could be debris as minime suggests, but that should have no affect @miniMe_rust hi, you can delete this from the .cs if you think it's causing it and let me know decay.debrisPrefab.guid = null; @TeaGuy Jordan hi, yes. use the Spawns Database File in the Expert and Nightmare profiles with the Spawns Database plugin.
  20. @ciri np, it won't be an issue. i was confused is all
  21. @ciri ah great! ya, it will show the message, but it will draw on your screen too the location of each RB event and the name
  22. /rb shows the name of the base. it draws it on your screen that one looks like raidmed17, so i'd just use the stability command in my last post
  23. @ciri maybe I misunderstand do you mean stability when you say floating? that screenshot looks like it's stability that you're asking about actually, not height rb.config stability true you can turn stability on with that
  24. which, type /rb and give me the name of the base @ciri
  25. @ciri yes, but that is the plugin file. you don't want to look there. changing that won't do anything its in the profiles oxide/data/RaidableBases/Profiles/ it is likely not an issue for every profile. just some. seems to be some Oxide bug causing it to be reset to 0 when it should be -1
1.9m

Downloads

Total number of downloads.

9k

Customers

Total customers served.

132.1k

Files Sold

Total number of files sold.

2.8m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.