phoenixofdark
Newbie
- Aug 13, 2020
- 34
- 9
YOU ARE A FUCKING SAINT <39.1 Dev Bugfix-2 Mega
BF-1 Black screen after christmas scene fixed, and kat now moves to lulu instead of lux Cleaning sparkle moved to correct location, and image removed properly once finished Lux should no longer tell you to get back to work once a chore is completed Vacant room above blacksmith fixed Progress skipping feature at game start now gives the player gold too.
BF-2 Lux will now properly go to bed Should now be able to exit her room after finishing cleaning or book finding chores Blue book in bottom left no longer causes collision with player Lux will now still allow you to do chores once DP>37 Defeating a champion in battle will no longer allow that champion to win the day, except in a few cases where they are scripted to always win that specific day. This means you have some level of control over who wins the weeks, too.
Still bugged and progress-locked, it's honestly laughable how lousy the dev is being at this point9.1 Dev Bugfix-2 Mega
BF-1 Black screen after christmas scene fixed, and kat now moves to lulu instead of lux Cleaning sparkle moved to correct location, and image removed properly once finished Lux should no longer tell you to get back to work once a chore is completed Vacant room above blacksmith fixed Progress skipping feature at game start now gives the player gold too.
BF-2 Lux will now properly go to bed Should now be able to exit her room after finishing cleaning or book finding chores Blue book in bottom left no longer causes collision with player Lux will now still allow you to do chores once DP>37 Defeating a champion in battle will no longer allow that champion to win the day, except in a few cases where they are scripted to always win that specific day. This means you have some level of control over who wins the weeks, too.
Hmm if you started cleaning room on old version and now lux only says "get back to work" then you need to have save from before starting it if thats your problem.Still bugged and progress-locked, it's honestly laughable how lousy the dev is being at this point
Problem is with the book chore, she gets stuck at the "get back to work" after it again. I found a workaround though, apparently the chores are randomized so just save scum until you get a different chore, it's annoying since the book chore keep showing more often but at least it works.Hmm if you started cleaning room on old version and now lux only says "get back to work" then you need to have save from before starting it if thats your problem.
I got other bug tho when doing laundry i pick it up from her room but when i try to exit the doors are closed. I dont have key and i dunno if it can be found?
even the room cleaning chore is still bugged with the "get back to work"Yea book dont work for me too so it seems laundry and book are bugged
I wonder if the dev hired some new noobs to help or something, cuz I don't recall any of the previous builds being this constantly brokenI think Morderkaiser opus chore is still causing "get to work" bug. I finished it with both option and on next day lux was stuck at "get to work". So if you get this chore just reload cause it will lock lux again.
I guess its more of engine problem, when many events are stack at each other in rpg maker. You fix one thing and other gets bugged and with more and more content its becoming bigger spaggethi program codeI wonder if the dev hired some new noobs to help or something, cuz I don't recall any of the previous builds being this constantly broken
I'd understand that if it was a matter of various content here and there, but this specific update was focused solely on one thing, yet that very thing itself is unplayably broken, it's a total "you had one job" moment. Of course bugs are a natural part of the process, that's totally reasonable and understandable, but the same soft-locking bug on the one and only core element of the update even after 3 bug fixes, that's just lousy if I'm being honestI guess its more of engine problem, when many events are stack at each other in rpg maker. You fix one thing and other gets bugged and with more and more content its becoming bigger spaggethi program code
I understand the frustration, but this is a DEV build. Ie, it is supposed to be buggy. This is an early access test build given out to Patreons for Christmas. If you guys stopped using leaked dev build links and just waited for me to post updates here myself when they are ready, there would be significantly less issues.I'd understand that if it was a matter of various content here and there, but this specific update was focused solely on one thing, yet that very thing itself is unplayably broken, it's a total "you had one job" moment. Of course bugs are a natural part of the process, that's totally reasonable and understandable, but the same soft-locking bug on the one and only core element of the update even after 3 bug fixes, that's just lousy if I'm being honest
Fair enough. And while it's not my place to tell you how to do your job, all I'm saying is even for a test build meant solely for playtesters, some amount of dev testing is necessary beforehand, wouldn't you agree? After all, playtesters are meant to be the second pass, to catch the type of bugs that a proper first pass wouldn't have missed. But Anyway, I completely agree with you on waiting for a proper public release insteadI understand the frustration, but this is a DEV build. Ie, it is supposed to be buggy. This is an early access test build given out to Patreons for Christmas. If you guys stopped using leaked dev build links and just waited for me to post updates here myself when they are ready, there would be significantly less issues.