Console Command Conflict Help!

John Ben · January 17, 2022

RagePluginHook.logWheneer I go on duty I have a crash like you see on the photo. I checked script updates and everything should be fine, but it is still crashing. Could someone help me with it?

Edited January 17, 2022 by John Ben

WithLithum · January 17, 2022

This should be a bug in LSPDFR plugins, as LSPDFR itself does not register such command.

John Ben · January 18, 2022

6 hours ago, WithLithum said:

This should be a bug in LSPDFR plugins, as LSPDFR itself does not register such command.

So is it possible to find which one crashes game while on duty?

Edited January 18, 2022 by John Ben

Joe C Wilson · January 18, 2022

I had this same exact thing. I thought something was wrong because I was editing LSPDFR data files. Went crazy cross-checking files for 30 minutes just to realize Deadly Weapons "magically" created a second DLL file in the LSPDFR folder. Look there to see if you have that or any other plugin that may have created a second DLL file by itself.

John Ben · January 18, 2022

10 minutes ago, Joe C Wilson 017 said:

I had this same exact thing. I thought something was wrong because I was editing LSPDFR data files. Went crazy cross-checking files for 30 minutes just to realize Deadly Weapons "magically" created a second DLL file in the LSPDFR folder. Look there to see if you have that or any other plugin that may have created a second DLL file by itself.

OMG I love you. It was it. I would have never find this one file with the same name only with the number 2 at the end. Thank you very much!

WithLithum · January 19, 2022

On 1/18/2022 at 2:55 PM, Joe C Wilson 017 said:

Deadly Weapons "magically" created a second DLL file

The author often changes it's Assembly Name between updates.

Joe C Wilson · January 20, 2022

19 minutes ago, WithLithum said:

The author often changes it's Assembly Name between updates.

Maniac is the only guy I know of that does this for his plugins. Changing a file assembly name from its native name in a future update would break it unless the other DLL is removed by the user itself. You have the option to download the new update whenever you're ready, but why force change the name when it causes issues? I understand if renaming a file is accidental, but it just seems like more trouble than what it's worth to change the file name which can lead to crashing issues. If you go to the download page you'll see there's no DLL file with the name '2' on it for Deadly Weapons, so what's the point of doing it through an update checker? Something has to be broken for it to do that, it doesn't make sense to me for it to be considered a normal occurrence to experience. The only logical explanation is that Maniac forgot to advise to have us manually remove the original DLL from our game after the new update that was passed through update checker.