Business bug

[tamika]

Where does the bug appear: Server
When did the bug appear: Today
Describe the bug: It displays incoming bankrupt state when it shouldn't
https://www.youtube.com/watch?v=Bhc4M6uGo58
Frequency: I don't know
Severity: Major
Steps to reproduce: Steps to reproduce would be fixing the bug where we don't get to lose our business by going bankrupt when business isn't meant to be bankrupt. Common sense in business guide topic tells me that as soon as my vault's capacity isn't -500$, it should reset the bankrupt cooldown to 5 days because guide says so:
2. Bankrupt - you can go bankrupt if you have -$500 in your vault & and you have 0 supplies, basically the business not being maintained. Whenever you reach these conditions the bankrupt state will be active meaning you have 5 days to up your supplies & vault, else the business will be set for sale.

My business began producing money which means it shouldn't have active bankruptcy status. Thank you very much.

[tamika]

So basically based on your "business" system and how it functions, I might have my business go bankrupt in a day because that is what notifies me despite upping my supplies and not having -500$ in business' vault anymore even though it clearly says, I quote:

2. Bankrupt - you can go bankrupt if you have -$500 in your vault & and you have 0 supplies, basically the business not being maintained. Whenever you reach these conditions the bankrupt state will be active meaning you have 5 days to up your supplies & vault, else the business will be set for sale.

So logically, as soon as I make a single delivery, for example upping my supplies for 8% (when I have -500$), I should immediately have bankruptcy status removed (cooldown refreshed to 5 days) till the moment my vault's capacity drops back to -500$ and starts 5 day bankruptcy timer again.

[Hiresh]

I rewrote/removed some business logic. An update will be released soon (took longer than expected). If this still happens after the update, please reply so I can check out if something else might be causing this then.

(update is already live)

If this is still an issue, you may reply on this topic: viewtopic.php?p=1120381