120 High Quality Raidable Bases Pack & Loot Table + Config + Profiles (Easy to Nightmare) 1.0.0

how can i fix that

 

11/3 11:07:37 PM [Command] o.reload RaidableBases

11/3 11:07:37 PM [Info] [CSharp] Started Oxide.Compiler v successfully

11/3 11:07:42 PM [Info] RaidableBases was compiled successfully in 2150ms

11/3 11:07:42 PM [Info] [RaidableBases] STOP: The paid version files are installed, and you are attempting to install the FREE version over the top it.

11/3 11:07:42 PM [Info] Installing FREE on top of PAID will remove paid-only options as they do not exist in the free plugin.

11/3 11:07:42 PM [Info] - If you intend to use the free plugin with paid files, then open a support ticket for the correct steps.

11/3 11:07:42 PM [Info] - If you intended to install the PAID plugin, then download it from the site you purchased it from only.

11/3 11:07:42 PM [Info] This protection exists solely to prevent accidental data loss. You can override this protection by renaming Buyable Events to ANYTHING in the config.

11/3 11:07:42 PM [Info] Loaded plugin Raidable Bases v3.2.2 by nivex

11/3 11:07:42 PM [Info] Unloaded plugin Raidable Bases v3.2.2 by nivex

That’s not the base pack — it’s the plugin itself. You have the FREE version of RaidableBases installed in oxide/plugins/, but the config and profiles from my pack are the paid format. The plugin detects that and refuses to load so it doesn’t wipe your paid-only settings. It’s a safety check, nothing is broken.

The fix: replace the plugin file with the paid one.

Go to where you bought RaidableBases (Codefling — https://codefling.com/plugins/raidable-bases) and download it from your purchases.

In your server console run: o.unload RaidableBases

Replace oxide/plugins/RaidableBases.cs with the paid file you just downloaded.

Run: o.load RaidableBases

It should load without that message.

Important — do NOT use the workaround the error suggests. It tells you that you can override the protection by renaming “Buyable Events” in the config. Don’t. That only lets the free plugin load by hiding the paid settings from it, and you’d lose the buyable raids and other paid-only options my config sets up. The check is there exactly to stop that happening by accident.

If you haven’t actually bought RaidableBases: my pack needs the paid version, it says so in the requirements. The free plugin doesn’t support the profile and config format the pack ships with.

One thing worth checking either way — if you have both files sitting in oxide/plugins/ (for example RaidableBases.cs and a second copy with a different name), delete the free one. Oxide will keep loading whichever it finds.

Let me know how it goes and send me the console output if it still complains.