Hello, I've found a bug when messing around with the graves on the latest beta version.
The bug disconnects me from the world without saving after I try to beckon the grave with the active Pipspook quest or shortly after finishing it (I waited couple minutes after the Pipspook finished the ending animation). I don't get any error message, it just disconnects me. It happened every time I tried doing it, even on a save that I played without any commands (I had some mods)
I tried it with only the two graves insight skills and also with the pipspook related ones and it happened both times. I don't get this bug when trying to beckon a grave without Pipspook (I am able to relocate them completely fine,=.
Below I attached how the disconnect screen looks like. I also put two client_log.txt files. The "client_log.txt" is for beckoning before finishing the quest and the "client_log_after.txt" is after finishing the quest.
- Go into a world or create a new one
- Spawn as Wendy with "Gravestones By Wendy" insight
- Go to a graves with a gravestone (I used "c_gonext("gravestone"))
- Get the spirit vessel (I used "c_freecraft()")
- Wait for the Pipspook to spawn (I used "c_skip(1)" until it spawned)
- Assist the Pipspook
- Before completing the minigame, try to beckon the grave with the spirit vessel
- The game should freeze and the "Disconnected" screen should appear after a little bit
Another way I got disconnected had the same steps as above, with a small change. After step 6. the new steps are:
- 7. Complete the Pipspook quest (I crafter magiluminescence and a walking cane to speed it up. I also enabled "c_supergodmode()" to not die)
- 8. Go back to the gravestone and try to beckon it
- 9. The game should freeze and the "Disconnected" screen should appear after a little bit
I tested it on couple new world, all were using default settings except the player limit was set to 1. I had only the two gravestone related insight active and no skins (if that matters).
-
1
A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now