Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+2)

Hi, I got the task "lose all your happiness", but it's nearly impossible: once your happinness is too low, you can't do any more happiness losing task, and thus, except if you are very lucky with the number, you have 1 or so in happiness at the end.

I would suggest to either make that the task is successful if you are under the minimum value for stat reducing task or that you can do a task reducing a little a stat if you are not at 0

(+1)

Also, bug: if you put R points in a stat, at the end of the next run, the cost of the upgrade will be the total of the invested points (ex: if I invested 4R in Shoulder Cricket, in the next run, I would need to invest 4R or 40Z to upgrade it by 1, instead of just 1R or 10Z). Resetting the upgrades fix that

Thank you for the bug report! I'll see about figuring out a fix to that since that would be really annoying to complete ^^;

And I'll look at the investment bug since it could be a calculation error on my part. Though if you could double check for me, that it isn't already leveled with R. Z points reset after a run but R points do not so the stat could be leveled up, if I understand your description correctly.

(+1)

I didn't try since then if the bug was fixed but here is the problem I had: example: I get 4R in run 1 and invest them to upgrade something 4 times (1R for each level), the 5th level is also indicated to be just 1R;

I complete run 2: instead of costing just 1R, the 5th level costs 4R (or 40Z) now; so reaching the 5th level cost a total of 8R; but if I reset the R, it would only cost 5R in total.

Basically, what I had was: if I invested R in an upgrade in a previous run, the next levels of this upgrade would cost the total of R already invested in it in the following runs instead of the normal cost.

I tested the bug multiple times and it always appeared

I haven't looked into bug patching this specific issue yet, but thank you for the detailed report! It'll help me with debugging and what behavior to look for 👍