A few days ago, I downloaded Grammar Police (with a plugin) and everything worked fine. Yesterday, I tried to request a backup manually, but it didn’t work and showed this message: “There is an issue with the backup configuration. Revert any changes.”

The strange thing is that this issue does not affect every unit, only some of them, such as EMS.

I have already tried uninstalling Grammar Police and its plugin, but I still have the same problem.

Does anyone know why and how i can solve it?

RagePluginHook.log

The backup configuration files are part of LSPDFR, so you can try reinstalling them.

Not sure why that would be happening though

[5/11/2026 6:10:52 PM.103] LSPD First Response: Error while initializing plugin: DeadlyWeapons.Main: Non è stato possibile caricare il file o l'assembly 'PyroCommon, Version=2.0.0.1, Culture=neutral, PublicKeyToken=null' o una delle relative dipendenze. Puntatore non valido. (Eccezione da HRESULT: 0x80004003 (E_POINTER)) at DeadlyWeapons.Main.Initialize()

You're also missing files for DeadlyWeapons

Thanks! I’m going to try it now.

So, I’ve just reinstalled the backup configuration files, but nothing has changed. Do you happen to have any idea why this might be happening? (I also fixed DeadlyWeapons.)

Aside from the PrisonGuard LSPDFR Plugin having a version checker issue, there is not entry in the log relating to this backup xml issue. Best you can do is revert any recent changes you made to xml's and test after each revision.

Thanks, I’ll try it now.

So, I tried to revert the XML, but I still have the same issue. Do you have any idea? Should I attach the XML file?

Is it normal to have a backup.xml both in lspdfr/data and in lspdfr/data/custom?

18 hours ago, C1ng4Gaming said:

Is it normal to have a backup.xml both in lspdfr/data and in lspdfr/data/custom?

If you had one installed there, yeah. Unfortunately, without any entry in the log, there is no way for me to tell which xml might be causing that message. Like I said before, you will have to backtrack through your xml's until you find the one causing it.

Hi, I wanted to update you on the situation: I deleted the data folder inside LSPDFR and replaced it with the original one from LSPDFR, and now everything works.

Glad you got it resolved!