Nazrin

I had a similar problem in https://github.com/Grasscutters/Grasscutter/pull/2163 where some code was killing config.id 0 in a scene, which happens to be the player.

A stack trace on the kill code (in player.java)? Might find where and why the player is being killed.

If you do a /pos in the location it happens, I might be able to help you. Error codes would be nice too.

Group 133103009 and 133315201 have suite_disk instead of normal suites.

Make sure you have something newer than https://github.com/Grasscutters/Grasscutter/commit/84e1371499717849dee662f781e9139a24ef03e7 . I did a overhaul with seelies so that they actually work. Did you get any grasscutter errors? If something says something...

Also, be warned that absolutely no one has been looking at individual chests and if they work or not (focus right now is on quests). You're going to have a...

I did all three monuments in that order and got nothing. No chest for me. (this group is group 133001146 BTW) I got: 06:24:02 [LUA] call trigger failed in group...

This might be the same bug as https://github.com/Anime-Game-Servers/Grasscutter-Quests/issues/109

Same thing happens to the geo formations in Surreptitious Seven-Star Seal Sundering 70330021 is the rock 70330145 is the "lantern" /q finish 7104410 /q finish 7104414 /q finish 7104416 /q...

This might be the same bug as https://github.com/Anime-Game-Servers/Grasscutter-Quests/issues/118