#"Jolly co-op" is breaking my game. Is there a way to fix it? (Black screen appears)

1 messages · Page 1 of 1 (latest)

livid summit
#

I am writing through a translator, sorry for the mistakes. Long before the update, I couldn't enter the game because of the black screen and stopped playing. With the release of "The Watcher", the game launched and I was able to play again. When I wanted to play with friends and turned on "Jolly co-op", the game froze (screenshot 1). After restarting, the black screen appeared again. Checking the files does not help, nothing is reinstalled (screenshot 2).
The black screen can be fixed by deleting the "jolly co-op" mod folder in the game files. After that, I enter the game for the changes to take effect. Then I reinstall the game, because DLS breaks. After that, I can enter the game and there is no black screen.
My friend and I tried to fix the mod and tried many methods (reinstalled the game several times, deleting in different ways; checked the files; inserted the files of the friend's game). I realized that the bug is related to my Steam account, because the same thing happens on another computer.
I really want to play with friends and I hope a solution will be found. rivboowomp

bug.jpg image.png
vague pulsar
#

;exceptionlog

molten glacierBOT
#

The exception log contains details about where in the code the exception occurred, useful to debug an error. It may be found in the game's root folder, along with the executable. Launching the game clears the file; if you have done so after getting the exception, you will need to trigger the error again to regenerate the log. If, even after doing so, the exception log doesn't exist, it's useful to provide this.

Default Steam path on Windows:
C:\Program Files (x86)\Steam\steamapps\common\Rain World
In Steam, you may open the game's folder with Right Click -> Properties -> Installed Files -> Browse..

To send the file, drag and drop it into the Discord window. Do not copy and paste the contents of the file.

The file provides the function which threw the exception in the code, as well as all of its ancestors down to the main. If the exception is generated by a mod or combination, typically they will be near the top, marked as modifying the recently-called functions. Disabling them may fix the issue.

livid summit
vague pulsar
#

this is a very strange exception. are you playing with linux?