Raidable Bases 2.9.5

all my bases are now showing as "normal raidable base", various difficulties now not showing (easy to nightmare). all coloured green like easy bases.

any thoughts?

8 minutes ago, Deisel said:

all my bases are now showing as "normal raidable base", various difficulties now not showing (easy to nightmare). all coloured green like easy bases.

 

any thoughts?

upon rechecking, i feel like the option for "number of bases to spawn for each type" is removed from config?

@Deisel Sometimes after an update the profile numbers change to all "0". Look at each profile and make sure it matches the difficulty. Its at the top of each profile numbers 0 to 4. Its in the data folder under profiles.  "Difficulty (0 = easy, 1 = medium, 2 = hard, 3 = expert, 4 = nightmare)": 0,

1 hour ago, Kapco411 said:

@Deisel Sometimes after an update the profile numbers change to all "0". Look at each profile and make sure it matches the difficulty. Its at the top of each profile numbers 0 to 4. Its in the data folder under profiles.  "Difficulty (0 = easy, 1 = medium, 2 = hard, 3 = expert, 4 = nightmare)": 0,

 

 

 

thanks ill look into it

},
      "Max Amount Allowed To Automatically Spawn Per Difficulty (0 = infinite, -1 = disabled)": {
        "Allow Max Amount Increase From Difficulties Disabled On A Specific Day Of The Week": false,
        "Easy": 4,
        "Medium": 4,
        "Hard": 4,
        "Expert": 2,
        "Nightmare": 2
      },

this whole section is missing from updated config????

Hey guys,

Having a minor issue where we keep getting teleported out of different nightmare/hard bases when we walk onto certain spots randomly specific to each one. Teleports us outside the base as if we are not supposed to be in it. Other bases flat out will not let us walk up to it without being teleported and easy/medium ones don't block us at all. Have bought and am using the plugin + Tier 2 pack thanks.

Just now, RigorousPizza97 said:

Hey guys,

Having a minor issue where we keep getting teleported out of different nightmare/hard bases when we walk onto certain spots randomly specific to each one. Teleports us outside the base as if we are not supposed to be in it. Other bases flat out will not let us walk up to it without being teleported and easy/medium ones don't block us at all. Have bought and am using the plugin + Tier 2 pack thanks.

Also I have the ladder using parameter set to true and it won't let me place ladders towards the centre of the bases, only the outside.

@Deisel

heya. normal mode is available in the free version only. this is why your paid settings were removed as they don't exist in the free version. please be careful to only download where you purchased from. if you're certain that you did not download the plugin from uMod, then an auto updater, manager or control panel updated from uMod. you should be able to block those from updating RB plugin

@RigorousPizza97

hi, odd. possible reasons are

1. Player Lockout in config,
2. Eject Enemies From settings in profile (this has no message)
3. raidablebases.banned permission,
4. missing Permission Required To Enter set in the profiles,
5. base is loading (this has no message for being ejected by it, but there is a message once the base has spawned)
6. using fauxadmin while being blocked by raidablebases.block.fauxadmin permission,
7. scavenging after raid is completed, Eject Scavengers When Raid Is Completed in config
8. are hogging another raid, Prevent Players From Hogging Raids in config
9. teleported into the raid, Allow Teleport in config
10. the raid exceeds the allowed limit of players with Max Amount Of Players Allowed To Enter Each Difficulty.

noclip and vanish bypasses most restrictions. some of these give a message.

4 hours ago, RigorousPizza97 said:

Also I have the ladder using parameter set to true and it won't let me place ladders towards the centre of the bases, only the outside.

ignore any messages from the game about not being able to place ladders. these are client side and cannot be hidden.

ladders can only be placed on "wall.frame.cell", "wall.doorway", "wall", "wall.frame", "wall.half", "wall.low", "wall.window", "foundation.triangle", "foundation", "wall.external.high.wood", "wall.external.high.stone", "wall.external.high.ice", "floor.triangle.frame", "floor.triangle", "floor.frame"

if you see anything missing from this list then let me know and I will add it. this list and functionality is used in prevent building spheres where the game would normally block you from using a ladder. such as on roads. otherwise the game will place the ladder vanilla.

Require Cupboard Access To Place Ladders setting in the profiles, oxide/data/RaidableBases/Profiles/ will restrict the use of ladders

Allow Players To Use Ladders is in the config and is enabled by default.

13 hours ago, nivex said:

@Deisel

heya. normal mode is available in the free version only. this is why your paid settings were removed as they don't exist in the free version. please be careful to only download where you purchased from. if you're certain that you did not download the plugin from uMod, then an auto updater, manager or control panel updated from uMod. you should be able to block those from updating RB plugin

@RigorousPizza97

hi, odd. possible reasons are

1. Player Lockout in config,
2. Eject Enemies From settings in profile (this has no message)
3. raidablebases.banned permission,
4. missing Permission Required To Enter set in the profiles,
5. base is loading (this has no message for being ejected by it, but there is a message once the base has spawned)
6. using fauxadmin while being blocked by raidablebases.block.fauxadmin permission,
7. scavenging after raid is completed, Eject Scavengers When Raid Is Completed in config
8. are hogging another raid, Prevent Players From Hogging Raids in config
9. teleported into the raid, Allow Teleport in config
10. the raid exceeds the allowed limit of players with Max Amount Of Players Allowed To Enter Each Difficulty.

noclip and vanish bypasses most restrictions. some of these give a message.

 

quite possible rust admin downloaded from umod. thanks'

15 hours ago, nivex said:

ignore any messages from the game about not being able to place ladders. these are client side and cannot be hidden.

ladders can only be placed on "wall.frame.cell", "wall.doorway", "wall", "wall.frame", "wall.half", "wall.low", "wall.window", "foundation.triangle", "foundation", "wall.external.high.wood", "wall.external.high.stone", "wall.external.high.ice", "floor.triangle.frame", "floor.triangle", "floor.frame"

if you see anything missing from this list then let me know and I will add it. this list and functionality is used in prevent building spheres where the game would normally block you from using a ladder. such as on roads. otherwise the game will place the ladder vanilla.

Require Cupboard Access To Place Ladders setting in the profiles, oxide/data/RaidableBases/Profiles/ will restrict the use of ladders

Allow Players To Use Ladders is in the config and is enabled by default.

Hey Nivex,

Definitely have the "require cupboard access to place ladders" set as false in all of my profiles. "Allow Players to Use Ladders" is true as well. Placing ladders on the correct structure type as well. I believe this might be something to do with base corruption? Otherwise most likely linked to whatever is causing my first issue. I can enter all structures using vanish and then I can stay in them fine, but entering hard, expert or nightmare without vanish is impossible, but once I use vanish in them I can enter and exit as I please normally. I will update if I figure it out. 

Is it possible to set IQDronePatrol by difficulty level?

@RigorousPizza97

yea, the above reasons are the only reasons you wouldn't be able to enter. yes, it could prevent you from using ladders if you're not allowed in the event.

@Chloe_Glano

no, but I will move it to the profiles so you can in the next update

 What could be the reason that not all raidet bases are counted for players? Approximately 20-25 players do not experience any problems. But two players complained that they had raided more than 10 medium-level bases, but at the same time they could not raid the hard level.
I looked in the logs of one of these players, indeed he had logged more than 10 medium-level databases, but in the data/RaidableBases file.The following is written in json:
      "Raids": 4,
      "Points": 7,
      "Easy": 1,
      "Medium": 3,
      "Hard": 0,
      "Expert": 0,
      "Nightmare": 0,
      "EasyPoints": 1,
      "MediumPoints": 6,
      "HardPoints": 0,
      "ExpertPoints": 0,
      "NightmarePoints": 0,
      "TotalRaids": 4,
      "TotalPoints": 7,
      "TotalEasy": 1,
      "TotalMedium": 3,
      "TotalHard": 0,
      "TotalExpert": 0,
      "TotalNightmare": 0,
      "TotalEasyPoints": 1,
      "TotalMediumPoints": 6,
      "TotalHardPoints": 0,
      "TotalExpertPoints": 0,
      "TotalNightmarePoints": 0,
      "ExpiredDate": "2024-09-08T02:16:29.8496682+03:00"

"Ranked Ladder": {
    "Award Top X Players On Wipe": 0,
    "Enabled": true,
    "Show Top X Ladder": 10,
    "Assign Rank After X Completions": {
      "Assign To Owner Of Raid Only": false,
      "Easy": 5,
      "Medium": 10,
      "Hard": 15,
      "Expert": 3,
      "Nightmare": 0
    },

This player has logged approximately 16 medium-level bases. But he has not been given the hardraid group. For what reason are not all databases counted?

@AdmFRP

hi. the only reasons he wouldn't get points is from one of the following. 

1. server is restarting and blocked by Block Rewards During Server Restart

2. uses noclip, vanish or Remove Admins From Raiders List

3. is inactive, Lock Treasure Max Inactive Time

4. blocked by Only Award Owner Of Raid

5. did not participate, Each Player Must Destroy An Entity For Reward Eligibility (false by default, and not compatible with Destroying The Cupboard Completes The Raid until 2.8.8)

6. blocked by Only Award First Attacker and Allies

7. blocked by Base Becomes Ineligible For Rewards On Despawn

8. Assign To Owner Of Raid Only will block Assign Rank After X Completions

@nivex Are you planning to include the IQDronePatrol parameter for each raid profile?

@Magnumk

hi, yes. I've moved it into the profiles in the next update

Calling hook CanEntityTakeDamage resulted in a conflict between the following plugins: AbandonedBases - False (Boolean), RaidableBases (True (Boolean))

:)) Please look into this

@KayKay

I would need more info

was it a player, an abandoned entity, an abandoned turret/samsite, a player entity, a tugboat, etc

55 minutes ago, nivex said:

@KayKay

I would need more info

was it a player, an abandoned entity, an abandoned turret/samsite, a player entity, a tugboat, etc

(21:48:52) | You've successfully pasted the structure

(21:48:53) | : rubber banding

(21:48:56) |: same

(21:48:59) | : you're good! its all groovy

(21:49:11) | [: lol

(21:49:14) | [RaidableBases] raidnightmare11 @ W3 : 180 items

(21:49:26) | You've successfully pasted the structure

(21:49:29) | i: 2024 base

(21:49:41) | : 2024 base is the next one

(21:49:42) | Calling hook CanEntityTakeDamage resulted in a conflict between the following plugins: AbandonedBases - False (Boolean), RaidableBases (True (Boolean))

(21:49:43) | [RaidableBases] raidnightmareimp2 @ Y11 : 180 items

I will keep a closer eye next time it happens

@KayKay

if you're getting rubberbanding during a paste then edit the copypaste config and change this

"Amount of entities to paste per batch. Use to tweak performance impact of pasting": 1,

as for the conflict you'd have to be in-game and match it up with whatever is happening at the time

@KayKay

what do you have Player Cupboard Detection Radius set to? it might be set too low if raidable bases are spawning close enough to abandoned bases to have conflicts. I suggest this be set no lower than 125. regardless, I will implement measures in both plugins to mitigate the chance of the bases spawning too close to each other. I would still need to know the rough cause of the conflict to determine where the conflict is in the code though

On 7/11/2024 at 1:56 AM, nivex said:

@AdmFRP

hi. the only reasons he wouldn't get points is from one of the following. 

1. server is restarting and blocked by Block Rewards During Server Restart

2. uses noclip, vanish or Remove Admins From Raiders List

3. is inactive, Lock Treasure Max Inactive Time

4. blocked by Only Award Owner Of Raid

5. did not participate, Each Player Must Destroy An Entity For Reward Eligibility (false by default, and not compatible with Destroying The Cupboard Completes The Raid until 2.8.8)

6. blocked by Only Award First Attacker and Allies

7. blocked by Base Becomes Ineligible For Rewards On Despawn

8. Assign To Owner Of Raid Only will block Assign Rank After X Completions

I will make a few clarifications to be sure that I understood everything correctly.

1. "Block Rewards During Server Restart": false,

2. The players are not administrators, they do not have access to noclip and vanish. Can the use of cheats similar to noclip and vanish be affected?

3. "Lock Treasure Max Inactive Time (Minutes)": 10.0, If a player was inactive for more than 10 minutes, but then continued the raid again and became the owner of the base again, can this affect the fact that the raid is not counted?

4. "Only Award Owner Of Raid": false,

5. Players with this problem raid alone, I think that's not the problem.

6. "Only Award First Attacker and Allies": false,

7. "Base Becomes Ineligible For Rewards On Despawn": true,

8. "Assign To Owner Of Raid Only": false,

If I understood correctly, then all the points in which I have set the value to false cannot be the reason that the bases are not counted?

"Base Becomes Ineligible For Rewards On Despawn": true, - And this may be the reason that the bases are not counted? But if so, it is unclear why there are only a few players whose bases do not count. For most players, everything counts fine.

@Soller

2. I'm not sure about cheats 

3. 10 minutes is the old default, and was changed to 20 because it is far too low and caused many issues like this one. no, it would not affect them if they were actively raiding again.

5. if the issue was present in 2.8.5 then this wouldn't be the cause. otherwise, it could be the fire game bug if the player is using only fire to raid.

7. no, this is specific when a player despawns their own purchased base using /rbe despawn

yes, if you set those false then they cannot be the reason. there is no other reason that the plugin would not give them points. furthermore, they would receive a message if they were ineligible unless those messages were disabled in the config under Event Messages.

Another suggestion, is it possible to make a command with which players can see the number of bases counted?