Cyan

It isn't as clear as it could be, but there is an option called 'Discard pending changes' which should have been in the File Actions menu whilst your new version was pending approval.

In your specific case, it looks your file was held for approval as it was a .RAR file that contained two other .RAR files. Our security check process does not support archive recursion, so archives that contain other archives will always trigger our approval process. To prevent this in future, upload multiple archives separately instead of inside another archive.

@GrunteliciousHello, I've added a self-service repair process for this. If you go to your character's LSPDFR Sync profile on the website, you should now see a message saying your character name may be corrupt. Click the 'Fix this' button and you should be walked through our new automatic repair process for this.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

This issue is caused by an LSPDFR plugin you've installed that has changed your characters' Persona. Ultimately the damage is done, your characters' Persona will have been altered on your side and then sent to LSPDFR Sync. LSPDFR Sync is showing the old name because we store the character name separately and it is not normally changeable. In a future LSPDFR release, we will prevent plugins from being able to modify this, as this is not what we expect plugins to do with the API. We can, on our side, modify the character data however we cannot continue to do this on a case by case basis. I will see if I can add a process into LSPDFR Sync on the website to automatically fix this.

Can you post your RPH log?

This issue should be fixed now.

I pushed an update yesterday which contained a few bug fixes, one of them was to fix a few issues with author permissions on their own files (their was a bug that caused authors not to be able to download their own hidden files). It looks like I've broken something in the process. I'm looking into it!

The option to mark a file update as minor (and therefore not send notifications) is now fixed.

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

If you feel this topic has been closed in error, please report this post.

What do you mean by blocking? A screenshot could help here.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

If you feel this topic has been closed in error, please report this post.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Hi @Quasar, Not sure if you have already contacted someone, but your best bet if this is moderation related is our Community Manager.

If you feel this topic has been closed in error, please report this post.

You don't. It's a PC mod.

At this time, there is no translation capability in LSPDFR. This is on the internal roadmap of things to consider in the future.

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.