ssue Identified in ver1.1.0!
We have confirmed a critical issue in ver1.1.0 where the game starts with an abnormal point value. This is a serious problem that should never have occurred...
We have now released ver1.1.1 to address this issue. However, I deeply apologize to the 74 players who purchased the game during the time ver1.1.0 was available and those who started playing during this period. Unfortunately, they experienced a flawed gameplay experience that did not meet expectations.
For players unable to obtain a refund through Steam's refund system, I am currently exploring solutions (I am committed to issuing refunds where appropriate and am investigating the best way to handle this situation).
I am sincerely sorry for the inconvenience caused by this issue. Rest assured that I will handle this matter with the utmost sincerity and care.
Currently, I am in contact with Steam Support to inquire whether refunds can be processed through Steam’s system.If this is not possible, I am also considering issuing refunds individually. However, since the developer, Uma, is an individual, I am carefully exploring methods to ensure the process does not involve exchanging personal information or cause any disadvantages to the players.
As a result of our investigation, we have determined that it would be problematic for an individual developer to provide refunds outside of Steam’s official system. For the time being, we kindly ask for your patience while we await a response from Steam Support regarding this matter.
Thank you for your patience and understanding.
umaaaaaa
--------------------------------------------------------------
Additional Note: Cause of the Issue and Countermeasures
Upon investigating the cause of the issue, we discovered that it was due to a long-unused debugging feature that remained in the build with its switch turned on. While we identified the problem, we had conducted debugging before releasing the version, so it remains unclear why the feature was activated or why it did not occur in our environment. In my haste to fix the issue, I failed to fully investigate these details.
To prevent such issues in the future, I plan to implement a notification system that will clearly alert me if such debugging features are active before packaging a version. I will continue to strive to ensure that such problems do not occur again.