nivex
-
Posts
5,176 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
@PhatBlinkie heya, that list excludes those entities from being blocked by Allow Players To Build when set false. it has no functionality when set true. remove your exclusions set Allow Players To Build to false set Allow Players To Deploy Barricades to false they will not be able to build anything then, except for ladders if you have Allow Players To Use Ladders enabled in the config -
Changed Status from Pending to Closed
-
I see you solved it by updating have fun
-
Changed Status from Pending to Closed
-
haha, that's awesome! maybe they had it and it got revoked accidentally at some point, or it was just VIP players that it was working for. glad it's sorted! I will improve the debug to look for this issue moving forward
-
I missed something originally... VIP has permission, but default group does not (abandonedbases.vip, abandonedbases.veteran or abandonedbases.basic) so the bases will not convert until default is granted a permission too. this is why it says 0 seconds in your first screenshot. sorry for missing that, but reading the wall of text from the image is very difficult. if you grant default a permission then players will be able to attack the base to convert it with the abandonedbases.attack permission, but the plugin will not automatically convert anything because thats disabled "Run Once On Server Startup": false, "Run Every X Seconds": 0.0, I included debug steps in my edited post, but that's not necessary now. just granting permission to default group will solve the issue.
-
heya. no, I'm not able to reproduce this on any server I still need debug information using the ab.debug information followed by sab command debug steps, from the server console type: ab.debug sab read server console output
-
@vanzylquintin42 you can adjust height in the profiles, oxide/data/RaidableBases/Profiles/ { "Option": "height", "Value": "1.0" }
-
@Magnetos again it looks like an issue with your language file
-
hi, your host needs to install the libgdiplus library on your machine.
-
@Magnetos hi, looks like the language file was changed for "RP"
-
Kick AFK player if raidbase is not being attacked for X amount of time
nivex replied to abcderanzi's Support Request in Support
Changed Status from Pending to Closed -
Kick AFK player if raidbase is not being attacked for X amount of time
nivex replied to abcderanzi's Support Request in Support
hi, you can set this in the config, Lock Treasure Max Inactive Time (Minutes) this is not going to kick them out. it will only remove their ownership after AFK for this period of time. -
@ChardaZAR hi, that doesn't increase the amount of items to spawn. it increases the loot amounts. so if you have explosive.timed 10/10 and use a 1.4 multiplier then it will spawn 14/14 instead.
-
@Wile E. hi, that has nothing to do with hours or time. 15 is the default. that's the max buyable events that can be active at any given time.
-
@Diesel heya, thanks for answering. player lockouts is for public events that spawn by Maintained or Scheduled Events buyable cooldowns is whats used for raids purchased with /buyraid
-
@Wile E. hi there I can't recommend any one-way, because it's all down to personal opinion, but I can try to expand on the details for you there are multiple ways to go about this using buyable cooldowns in the config "Easy": { "VIP Permission: raidablebases.vipcooldown": 1800.0, "Admin Permission: raidablebases.allow": 0.0, "Server Admins": 0.0, "Normal Users": 1800.0 }, VIP Permission - grant this permission to your vip group. then. anyone in this group would receive this cooldown for Easy raids Admin Permission - the raidablebases.allow permission is what you'd grant to your admins, moderators or staff only Server Admins - this is anyone with an admin flag which is generally auth level 1 or higher Normal Users - this is anyone that does not fall under the above, aka the default group the lowest cooldown time will be chosen based on the above four options. users who remain in vanish or noclip will not be given a cooldown the cooldown is applied when the event is purchased, and does not start to expire until the event despawns
-
@Fanatik that's not an error. it's debug, and is normal. post your config -
@Fanatik perhaps I should remove the requirement for a TC during purge? edit .cs and change on line 4267 if (!hasPrivilege) to if (!hasPrivilege && !IsPurgeEnabled) and you must change this too on line 4217 a = entity.transform.position; to a = entity.transform.position; position = a;
-
@Fanatik hi, TC is required, that is why you see: No privilege found. this is intended yes, this is normal. it is required to restart the purge each time
-
@Fanatik hi, I'm not aware of any known issues. use the commands sar purge to enable purge. you must enable this for purge. if you restart or reload the plugin then it must be enabled again ab.debug to enable debug sab to run a scan for conversions none of these bases can be within a zone manager zone, either, or it will be blocked unless configured properly post the results in a new ticket
-
heya 1. Arena Walls in the profiles, set Enabled to false, oxide/data/RaidableBases/Profiles/ 2. set Convert PVP to PVE to true, and Convert PVE to PVP to false, in the config 3. edit Marker Name in the config 4. increase the amount in the config. Max Maintained Events
-
Changed Status from Pending to Closed
-
hi, yes, if you delete the difficulty loot files (they're not profiles) then it will spawn base loot only this is not recommended when you have a few items that you want to always spawn. if you don't want that then you could use base loot tables only
