cmooref17 / Lethal-Company-TooManyEmotes

https://thunderstore.io/c/lethal-company/p/FlipMods/TooManyEmotes/
MIT License
14 stars 5 forks source link

Can't do/see any emote #122

Closed thetyta closed 2 months ago

thetyta commented 2 months ago

image

When I join the Lobby, I can't use or see any emotes that others do, and then this screen pops up, even when I deleted other mods and tried it by itself.

cmooref17 commented 2 months ago

You most likely got an error in your console/logs. Maybe a mod conflicting? WOuld you be able to share it if you can find that error?

thetyta commented 2 months ago

You most likely got an error in your console/logs. Maybe a mod conflicting? WOuld you be able to share it if you can find that error?

As I stated before, even with only this mod, the bug remains and no error pops up on console Also, I can't close this screen or move my character

https://github.com/cmooref17/Lethal-Company-TooManyEmotes/assets/162638906/9762ce63-3373-4878-b67e-c68946443e69

image

and this shows every milisecond

cmooref17 commented 2 months ago

Sorry, I see where you said that you tried this with only this mod enabled. It seems like there's definitely an error in the logs. The error should be right before all that spam I'm guessing, so if it is possible you can get that, that would be very helpful. It is very strange that you would be getting this error with only this mod installed. What version of the game are you on? V49? V50?

thetyta commented 2 months ago

image

I'm on V50

cmooref17 commented 2 months ago

Ah, there it is. These cryptographic errors are going to be the existence. I fixed some of them, but apparently not all of them. Thanks so much for this! I will try to get this fixed today and have an update pushed out later.

thetyta commented 2 months ago

Thank you so much!! Also, when I close the game through ALT + F4 (I can't close through pause menu) this shows up as well

image

cmooref17 commented 2 months ago

Okay, good to know! I'll see if I can prevent this error as well, just in case it is causing other issues.

cmooref17 commented 2 months ago

I updated the mod to 2.1.12, and this version should automatically fix this bug. The bug is related to some form of file corruption, I believe. If this still doesn't solve your issue, let me know, and I can show you how to delete the corrupted file.

thetyta commented 2 months ago

image image

even updating the mod hasn't fixed the issue

MrNuckMAn commented 2 months ago

I updated the mod to 2.1.12, and this version should automatically fix this bug. The bug is related to some form of file corruption, I believe. If this still doesn't solve your issue, let me know, and I can show you how to delete the corrupted file.

Hello! I'm having this same issue as well. If you say it's a corrupted file, may you help me delete it? Thanks in advance!

cmooref17 commented 2 months ago

Ah, sorry about that.

I would head to this directory: C:\Users\YOUR_USER\AppData\LocalLow\ZeekerssRBLX\Lethal Company

And delete this file: SaveFile.es3

Don't delete the TooManyEmotes file. That one isn't causing the issue.

Also, to help me test this issue, and figure out why this is happening, would you be able to send me this file? Maybe attach it here, or if you would rather email it to me, email it to me at cmooref17@gmail.com.

But if deleting this file doesn't fix the issue, you could try deleting "LCGeneralSaveData".

I will update this mod again soon to fix the error you received. I'm really not sure why the error is still appearing, but this time, it's related to deleting a key instead of checking if a key exists.

thetyta commented 2 months ago

Deleting the file fixed the issue! thank you so much!

I will send it to your email since github don't support the file type

MrNuckMAn commented 2 months ago

It fixed removing the file, thank you s much!

cmooref17 commented 2 months ago

Okay, I'm glad to hear it! And thanks to you both. I received your save files, so hopefully I can do some testing to see if I can find a better solution for this error. I will close this issue for now.

I will also push out an update soon with more automatic fixes which might fix this more recent error you shared.