Jump to content

nivex

Creator
  • Posts

    5,154
  • Joined

  • Last visited

Everything posted by nivex

  1. nivex

    UI issues during looting

    Changed Status from Pending to Closed
  2. ok, make sure the plugin is unloaded and delete this file: oxide/data/RaidableBasesUID.json make sure the file name is exactly as shown this should fix any issues.
  3. nivex

    Raidable Bases

    disable it in the config =p
  4. type version in console and post back with what steam update it responds with
  5. hi, the update is not going to change the difficulties of the profiles you would've had to installed the free version and then the premium version sometime afterwards make sure you have auto update turned off from any auto update plugins including rust server manager you will have to reinstall the package as this would've wiped any premium settings you can verify this by checking the profiles to see if all difficulties are set to 0 again oxide/data/RaidableBases/Profiles/
  6. nivex

    Raidable Bases

    Destroying The Cupboard Completes The Raid is a little buggy in 2.7.0 your players just need to loot or destroy a box after destroying the TC to get around this issue until its fixed I changed the check to end the raid to only check when something is looted or destroyed, rather than every second. this helps performance a tad bit. unfortunately i didn't account for the entity not being destroyed in the same frame so it does not work properly atm. it is fixed in next update I've looked into the reported performance issues and do not see any changes that would cause this. I have this running on quite a few servers with no issue aside from the above TC bug. I suggest updating your servers to revert the Facepunch pool changes and see if that resolves the issue for you. if you're having performance issues when the base is pasting via CopyPaste but not afterwards then you need to reduce the paste batch limit in CopyPaste config from its default of 15 to 3-5. this is not a plugin issue if it continues to happen after making this config change. though this issue may have been fixed by the forced update.
  7. NextTick(PurgeTemporaryRespawns); remove this code from the .cs, and update your server with the latest steam and oxide updates there's nothing else that I can see that would cause this. i believe it to be the facepunch update to pooling that they reverted afterwards.
  8. nivex

    update

    Changed Status from Pending to Closed
  9. nivex

    update

    yep np
  10. ok i will check it out now
  11. nivex

    update

    its the site, you can clear your cache to fix it
  12. nivex

    plugin errors

    Changed Status from Pending to Closed
  13. nivex

    Raidable Bases

    2.7.0 released you do not have to wait to update enjoy!
  14. nivex

    Raidable Bases

    oh I'm not doubting that you saw walls, but you're certain there was a raid base there beforehand? I mean I know the walls were definitely there, but sometimes annoying questions need to be asked to be sure. just like a tech that asks you, "is it plugged in?" "did you turn it on?" "is the issue between the keyboard and chair?"
  15. nivex

    Raidable Bases

    @Hawkhill walls: when a raid ends the entities despawn in the order of walls, blocks and then deployables last. they're all in the same list, so if the walls don't despawn then the base won't either. this means that the kill messages were sent to those walls, because your base despawned afterwards. its unknown why this happened. any number of things can break it such as bad server performance, other plugins blocking the kill, the server canceling the invokes, oxide throwing errors, etc. i would need more information. i suspect its an oxide issue as i have seen IOCore exceptions being thrown from OnEntityKill which can't happen unless oxide is bugged or another plugin is bugging out oxide. this was from one other report. other than that i've heard nothing else about this, and that one was bases not walls. @Aussie4life floaters: bases won't float unless you've modified a autoheight or height setting, or if the base was not copied properly to begin with. many other packages did not copy the bases properly. my packages were all copied at 1.5 meters so they will paste as intended
  16. nivex

    Raidable Bases

    @byond1991 lmao ya thatll do it
  17. Changed Status from Pending to Closed
  18. hi, no problem
  19. nivex

    Abandoned Bases

    @TheRiddledNote sorry I meant to say disable Do Not Destroy Manually Converted Base When Despawn Timer Expires to prevent base despawning for /sar convert bases
  20. nivex

    Raidable Bases

    @Aussie4lifeset the radius back to 25-45. you're trying to spawn it on top of the base and thats not gonna work
  21. nivex

    Abandoned Bases

    ya they can use /sar convert they need abandonedbases.convert perm to use the command you need to set Despawn Timer to 0 if you dont want the base to despawn afterwards they can use /sar cancel to cancel the raid there is a cooldown before they can cancel, and you can require the raid be completed before canceling too. it requires abandonedbases.convert.cancel you need to configure everything. @TheRiddledNote
  22. nivex

    Raidable Bases

    @aussie4life its either disabled, theres an error, or you have a plugin deleting them i tested with 65.0 and it spawns fine, though it should not have a radius higher than the protection radius - 5, or 45.0
  23. nivex

    Base Loot

    oxide/data/RaidableBases/Default_Loot.json you don't need to add it. it's already there. just replace the text in the file with [] and reload the plugin
  24. nivex

    Base Loot

    edit the default loot table and replace it with []
  25. nivex

    Max amount of raid bases

    Changed Status from Pending to Closed
1.8m

Downloads

Total number of downloads.

8.4k

Customers

Total customers served.

127.3k

Files Sold

Total number of files sold.

2.6m

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.