Raidable Bases 3.1.1

@MEO-01

I suppose it could be the base ya. recopy the base.

not sure about the respawns, but that is like the 7th report I've received in a few weeks now. this should not be possible - every respawn requires an invoke to elapse first using the min/max time (120-240), no exceptions. are you using Oxide or Carbon? I'm looking at the code now, and it's not possible for this time to be bypassed or to elapse early so I'm stumped.

the respawn issue seems to be an issue with game time on your server. one of the only ways for an invoke to expire early, and thus npcs to respawn early, is if the time was altered. the only other way is so unlikely that it's not even worth mentioning. I will just implement a different solution that does not depend on that. I will use the server date time instead. 

9 hours ago, MEO-01 said:

they just go through wall in only one base so i think it's the base problem, but NPC just keep respawn too fast even i already set respawn to 120-240 min-max in profile file but they just keep respawn like 3-5s

Depends, for me works good, if you have 25 npcs there the timer will count for each npc that you kill in order, not the last one. 120 seconds is little, increase the minimum timer, that should work.

Can the author add an API to query the current number of active raid bases?

@laodu

hi, api or a command?

rbe active is the command

GetAllEvents API will return a list of every event, API

I can add GetActiveEventCount and GetAllEventsCount API next update to return the number only.

7 minutes ago, nivex said:

@laodu

hi, api or a command?

rbe active is the command

GetAllEvents API will return a list of every event, API

I can add GetActiveEventCount and GetAllEventsCount API next update to return the number only.

api,Thank you very much for your reply. I really need the GetActiveEventCount and GetAllEventsCount API.

hello Nivex, i am wondering if theres some way to know how many raidable bases has been bought via the /buyraid command during a wipe?

@Demo_71

heya, not really a "look here to see an exact count" way, but thats logged in the server console. so you could view logs from each day. download the logs, open them all at once in notepad++ and search for "has paid for the" text without quotes using notepad++ find all in all open documents. its easier than it sounds. literally download your logs, open them all, use search and it will tell you the count

@Demo_71

almost forgot...its not buyable only, but if you want to know the total amount spawned from all maintained, manual, buyable and scheduled then that amount is in the data file under TotalEvents.

oxide/data/RaidableBases.json

Hello Nivex, when players on the server I play on enter RaidableBase locations they encounter this. (see attachment)
What controls this? They're naturally spawning bases that haven't been spawned in with /buyraid. They can't deal damage to the base or npcs until they Claim the base via that UI

@Bagel1133hi, not sure, that might be a realpve option

hey nivex i am having a weird issue with the buyable events, for some reason on some of them, players from the inside of the dome can damage players outside, and sometimes not, do you know why that could be happening?

@Demo_71

hi, no, not unless it was from Allow Friendly Fire or PVP delay. 

8 hours ago, nivex said:

@Bagel1133hi, not sure, that might be a realpve option

It was RealPvE, ty for the suggestions. They have a RaidableBases config

what does the "text" mean, like: 

shortname": "tarp",
    "name": null,
    "text": null,
 ty

20 minutes ago, Dead Nasty said:

what does the "text" mean, like: 

shortname": "tarp",
    "name": null,
    "text": null,
 ty

This is just a property of an Item, for example, the Item Perks plugin uses it, in fact it is an analog of customization using SkinID, correct me if I made a mistake somewhere.

that's correct, it changes the text of the item, and is generally used with a custom skin. you shouldn't alter it unless you have a custom item that depends on it.

Hello. We followed all the instructions, but the plugin is still not working. We placed all 22 base files into both 'oxide/data/CopyPaste' and 'oxide/data/RaidableBases/Profiles/Nightmare'. We updated the 'Base Filenames' in the profile config. We granted the 'raidablebases.allowed' permission.

Despite this, the plugin says 'Unknown command' or 'You cannot spawn a raid base that has not been configured'. We have already spent several hours trying to fix this. Could you please check our config and tell us exactly what is wrong? Why isn't it working?

@bizon1tv

hi, what command is unknown? 

the copypaste folder must be all lowercase. oxide/data/copypaste/ not CopyPaste

Hi @nivex,

Thanks for replying. We have already done the following:

All 22 base files are placed in oxide/data/copypaste/ (all lowercase) and also in oxide/data/RaidableBases/Profiles/Nightmare.

We updated the “Base Filenames” / “Paste Files” list in the Nightmare profile config to include all the base files.

The server user has the raidablebases.allowed permission.

We verified the filenames match exactly (without .json) and are all lowercase.

We tried reloading CopyPaste and RaidableBases multiple times.

Despite all this, the plugin still gives either:

“Unknown command” when trying to run /rbe spawn Nightmare

“You cannot spawn a raid base that has not been configured” when using the console command

We have spent several hours troubleshooting, and it still does not work. Could it be that some additional settings in the config are required to enable the Nightmare bases? Could you please check and advise exactly what might be missing?

Thank you for your help.

@bizon1tv

Heya, there is a setup guide in the documentation with a few steps for basic functionality to spawn bases. see Step 1: Obtain Your Bases in the documentation if you still have trouble afterwards.

Nightmare base files go in the copypaste folder only (not the profiles directory), oxide/data/copypaste/
Nightmare base filenames go inside the Nightmare Bases profile, oxide/data/RaidableBases/Profiles/Nightmare Bases.json

Specifying rbe spawn Nightmare is invalid.

• the rbe command has many purposes, one of them is to spawn bases wherever you are looking.
• do not type this command inside of or near other bases.
• if you accidentally spawn a base, you can despawn it after it has spawned using /rbe despawn if you are close enough to that event.
• to spawn by filename, /rbe nightmare001
• to spawn by difficulty, /rbe Nightmare
• to spawn by difficulty level, /rbe 4
• rbe is a console command. you can type this in the F1 game console or the server console. do not use this command to spawn bases from the server console.
• /rbe is a chat command. you can type this in the game chat only. do not type it in any console (note that the forward slash prevents use of this command in the console)
• /rbe is not an unknown command unless it has been changed under Event Command in the config file

Specifying rbevent spawn Nightmare is invalid

• the rbevent command has many purposes, one of them is to safely spawn bases somewhere random on the map (you can use this command anywhere).
• to spawn by filename, rbevent nightmare001
• to spawn by difficulty, rbevent Nightmare
• to spawn by difficulty level, rbevent 4
• /rbevent is a chat command, you can type this in the game chat only. do not type it in any console (note that the forward slash prevents use of this command in the console)
• rbevent is a console command. you can type this in the F1 game console or the server console.

If it still says the base is not configured then it's not. either the file does not exist in the copypaste folder or the filename does not exist in the profile. 
you can verify which by using the rb.config list command (ignore any files that don't pertain to you)

Quote

(12:39:16) | Easy Bases > Profile

raideasy1, raideasy2, raideasy3, raideasy4, raideasy5, raideasy6, raideasy7, raideasy8, raideasy9, raideasy10
EasyBase1 > This file does not exist
EasyBase2 > This file does not exist
EasyBase3 > This file does not exist
EasyBase4 > This file does not exist
EasyBase5 > This file does not exist

That example shows files that exist on a single line, followed by individual files on separate lines that do not exist.

• if you do not see your files listed at all, then they need to be added to the profiles. example, replace with your own filenames (still without .json):
  rb.config add "Nightmare Bases" nightmare1 nightmare2
• if you see your files listed, but it says each of them does not exist on separate lines then they must be added to the copypaste folder.
• ignore any files that do not pertain to you. if you want to remove such files then use the command
  rb.config remove EasyBase1 EasyBase2 EasyBase3 EasyBase4 EasyBase5