The International Simutrans Forum

Simutrans Extended => Simutrans-Extended development => Topic started by: killwater on December 09, 2012, 03:35:34 PM

Title: RC going bankrupt
Post by: killwater on December 09, 2012, 03:35:34 PM
Hello
Is possibility to go bunkrupt intended?
Title: Re: RC going bankrupt
Post by: jamespetts on December 09, 2012, 04:43:03 PM
It is indeed intended that one ought be able to go bankrupt, yes. Do you think that you have found a bug in this respect?
Title: Re: RC going bankrupt
Post by: killwater on December 09, 2012, 04:55:18 PM
As I remember in Experimental when you went below 0$ there was no new game menu. It appeared for me when I went bankrupt, but only for the first month. Next month it was usual: "You have been overdrawn for XX months intrest is accumulating..."
Title: Re: RC going bankrupt
Post by: jamespetts on December 09, 2012, 05:10:47 PM
Bankruptcy is optional in Experimental: it is a useful thing to have in an online game, where it leads to liquidation. Is this behaviour different to the released 10.15?
Title: Re: RC going bankrupt
Post by: killwater on December 09, 2012, 05:38:29 PM
Well it looks like the same in 10.15. My bad. This should be ok then.
One more thing invalid order in vehicle schedule crashes the game (when I change stop level above sea). But I suspect that it is pretty old bug.
Title: Re: RC going bankrupt
Post by: jamespetts on December 09, 2012, 05:43:58 PM
Can you give more detailed steps to reproduce and let me know whether this can be reproduced in 10.15?
Title: Re: RC going bankrupt
Post by: killwater on December 09, 2012, 06:41:59 PM
Yes it can be reproduced in 10.15.
1. Make flat road  (z=1).
2. Place two stops (A and B).
3. Make a schedule between stops and start a vehicle.
4. Pause the game.
5. Remove stop A and ground under it.
6. Terraform to decrease level to z=0 under the stop A(non-existent now).
7. Press play.
8. Enjoy your crash.
Title: Re: RC going bankrupt
Post by: jamespetts on December 09, 2012, 07:10:35 PM
Thank you very much for that report - that is most helpful. I have fond and fixed that bug on the 10.x branch.