There's a hidden way to increase one point, but there's no actual use for it in the game yet, so you can look around and try to find it if you want, but you don't actually need to worry about it for now!
That's pretty much all the main content for now! (There was a message saying exactly this right after you leave Vaulty and Jenny, maybe you've missed it.)
You can check the Scene List.txt located on "\Lewd Falls v0.04\Extras", to make sure you didn't miss anything optional.
The Silk was for Vaulty's quest, it was supposed to trigger automatically on the next day after the fight, that didn't happen for you?
But if it did, and you are thinking there's something else to do with it because it is on your inventory, that's normal, it will stay there just like Mavis's blood.
If the save error is something like "Uncaught TypeError...", you can try using the keyboard menu to save the game (press X to open and arrow keys/Z to navigate).
If the save error is something like "Uncaught TypeError...", you can try using the keyboard menu to save the game (press X to open and arrow keys/Z to navigate).
Yeah, the current engine is pretty annoying to work with and a lot of the bugs are caused by some plugins not working too well with another, I'm trying my best to fix what I can but some bugs will probably have to stay until I move the game to Unity.
About the Hololive girls, I'm a fan of them, and I know a lot of people are too. I thought they would fit the theme of my game, so I added them, I'm glad it worked out too, from what I heard from some people.
And yes, I do have plans to add a few more girls from EN, JP and ID! (I've already briefly mentioned Ina on Calli/Gura's quest too!)
About the combat, I should be doing a few tweaks to balance it more since I've added new bats/skills this update, but overall it should stay the same for simplicity and due to limitations of the engine.
I do plan to make a few changes to the combat on Unity.
I've never seen this error happening with my game.
Lewd Falls usually have some trouble with Joiplay (although it's usually the same error, this one is new and seems like it only happened to you).
I can't really help with Joiplay problems, but since you were messing with some things for another game, it might be affecting mine too, so you can look into that!
I understand what you are saying, but that's pretty much what happens on every RPG, if you find my game annoying for doing this, you must hate every type of RPG.
But I agree on some parts, so what I will probably do is add a hint to what level should be good enough for this event and the next one, hopefully it will help some players in the future.
While I do try to take into account the people that like to rush (that's precisely why I will not let people save on this event, to avoid them bricking their save and complaining about it later), it's not my fault if they are ignoring all the warnings and end up getting their ass beat by some enemy.
Everything comes back to interpretation, if the player assumes that a "tough fight" can be won by killing a couple slimes and buying 2 heal items, failing it is entirely on them.
It's a gamble, for some people will work flawlessly, for others will crash, you can try but I can't really give you much support to the problems it may have.
The game warns you to proper prepare before going into the graveyard. (Buy items and level up), so not being able to save there is on purpose for two reasons:
There's a lot of people that may just rush and don't read that message, and then would save before the boss with 10% HP left and no items, essentially bricking their saves.
Without having a way to save there, it makes the whole event feel more like an actual challenge, otherwise everyone would just keep retrying the boss without any consequences for not properly preparing.
Sorry about this, this is an old known bug that affects some of Joiplay users.
While in theory my game is playable on mobile using these apps, it is pretty much a gamble, for some people it will work, while for others it will have this bug.
Sadly I can't really do anything about it for now, I know the reason for the bug, but I can't remove it, since it is an essential plugin.
