Databases no longer appear automatically after a server crash :(Solved

Hello, following a server crash, the plugin launches fine without any error, but no basis is set up. Only if I activate them by hand with the command / rbe basename
The crash was linked to a full disk space on the server, I put everything back in place and everything works without any hang-ups except this plugin.

Which drives me crazy because all the files are intact that I don't see any errors, just it doesn't start the automatic database spawn.
I also deleted all files (after stopping the plugin) :
- /config/RaidableBases.json
- /data/RaidableBases.json

All files and folders in :
- /data/RaidableBases

I relaunched the plugin, all files have been regenerated by default.
I edited the file: /data/RaidableBases/Profiles/RaidBases.json
To just change the name of the base: RaidBase1 with the name of one of my bases.
And reactivate in the RaidableBases.json file the minimum:

"Maintained Events": {
"Always Maintain Max Events": true,
"Chance To Randomly Spawn PVP Bases (0 = Ignore Setting)": 0.0,
"Convert PVE To PVP": false,
"Convert PVP To PVE": false,
"Include PVE Bases": true,
"Include PVP Bases": true,
"Ignore Safe Checks": false,
"Ignore Player Entities At Custom Spawn Locations": false,
"Minimum Required Players Online": 1,
"Max Maintained Events": 1,
"Spawn Bases X Distance Apart": 100.0,
"Spawns Database File (Optional)": "none",
"Time To Wait Between Spawns": 15.0
},


But nothing worked, here is what I got in the logs during all my operations and tests:
(22:15:43) | Unloaded plugin Raidable Bases v2.1.6 by nivex
(22:16:42) | [Raidable Bases] Loaded default configuration file
(22:16:42) | [Raidable Bases] Blocked spawn points in 4 zones.
(22:16:42) | [Raidable Bases] Loaded RaidBases profile
(22:16:42) | -
Loaded 29 items from RaidableBases/Default_Loot
(22:16:42) | [Raidable Bases] Free version initialized.
(22:16:42) | Loaded plugin Raidable Bases v2.1.6 by nivex
(22:17:48) | [Raidable Bases] Grid initialization completed in 5 seconds and 597 milliseconds on a 5000 size map. 8346 locations are on the grid.
(22:21:56) | Unloaded plugin Raidable Bases v2.1.6 by nivex
(22:23:11) | [Raidable Bases] Blocked spawn points in 4 zones.
(22:23:11) | [Raidable Bases] Loaded RaidBases profile
(22:23:11) | -
Loaded 35 items from RaidableBases/Default_Loot
(22:23:11) | [Raidable Bases] Free version initialized.
(22:23:11) | Loaded plugin Raidable Bases v2.1.6 by nivex
(22:24:15) | [Raidable Bases] Grid initialization completed in 4 seconds and 231 milliseconds on a 5000 size map. 8345 locations are on the grid.
(22:31:47) | [Raidable Bases] Blocked spawn points in 4 zones.
(22:31:47) | [Raidable Bases] Loaded RaidBases profile
(22:31:47) | -
Loaded 35 items from RaidableBases/Default_Loot
(22:32:51) | [Raidable Bases] Grid initialization completed in 3 seconds and 692 milliseconds on a 5000 size map. 8343 locations are on the grid.
(22:42:04) | [Raidable Bases] Blocked spawn points in 4 zones.
(22:42:04) | [Raidable Bases] Loaded RaidBases profile
(22:42:04) | -
Loaded 35 items from RaidableBases/Default_Loot
(22:43:07) | [Raidable Bases] Grid initialization completed in 2 seconds and 793 milliseconds on a 5000 size map. 8338 locations are on the grid.
(22:43:54) | Unloaded plugin Raidable Bases v2.1.6 by nivex
(22:43:54) | [Raidable Bases] Blocked spawn points in 4 zones.
(22:43:54) | [Raidable Bases] Loaded RaidBases profile
(22:43:54) | -
Loaded 35 items from RaidableBases/Default_Loot
(22:43:54) | [Raidable Bases] Free version initialized.
(22:43:54) | Loaded plugin Raidable Bases v2.1.6 by nivex
(22:44:58) | [Raidable Bases] Grid initialization completed in 3 seconds and 945 milliseconds on a 5000 size map. 8338 locations are on the grid.

At best, I have a message regarding the grid and nothing more ...

HELP! And thank you in advance.

and bravo mister NIVEX for this plugin !!!

Sorry, for the translator who replaced the words "Raidable Bases" with "Databases"!

I'm talking Raidable Bases that don't automatically appear...

Thanks.



Merged post

Are there other files than the ones I mentioned that are used by the plugin and which could if damaged cause this?
I turn around :(

what did you do to fix this, since you marked it as solved?

Locked automatically