I placed a HQ, maxed it. Noticing it was useless and generating high cost I removed it.
Wasnt there longer as 2 minutes.
But now I am stuck with a constant cash flow of 14,500. This is due to building and removing the HQ.
I mean... Its a positive cash flow, so I dont complain, but its a bug...
pak128 newest version
I can't reproduce this bug.
_ Create a new savegame
_ Build a HQ
_ Upgrade it
_ destroy it
... and end up with no cash flow (no maintenance, no anything), just less money than I started with.
Could you post a screenshot of your finance window before and after the operation ? By the way, can you confirm you are playing with pak128 2.5.1 ?
By the way, HQ are not completely useless (they are partly useless indeed since one can play very well without HQ), they generate a passenger (and mail) flow which is significant at high levels.
I also recall them adding a lot to the population of a city in pak64 112.3 if built within the boundary (unsure about pak128). But this is pretty insignificant in the long run once everything becomes heavily connected. I personally think that headquarters should be given a more important role one day than passenger and mail generation and showing how much money you have but that would be something outside the scope of a single pakset.
Quote from: DrSuperGood on October 28, 2014, 07:58:06 PM
I personally think that headquarters should be given a more important role one day than passenger and mail generation and showing how much money you have but that would be something outside the scope of a single pakset.
What about a limitation of lines to build, dependening on the HQ size. Biggest HQ ever with no limitation.
But that's a serprate subject, so please start a new one if you thing it qould make sense.
to the bug:
I can reproduce it on r7354 with pak128.r1487 (with old and new HQs)
First start with game break, build the HQs, then destroy them, make fast forward for several month.
The first set maintenance is exactly a positive number of cash flow.
This may be pakset independence bug , but it may be also a cheat modus.
I'm not sure to understand what "game break" is, are you talking about Pause ? I still can't reproduce the bug, I think I missed something in your explanations ...
sorry, "game break" = pause
second control with
r7354 and pak64 with same result -> there is a bug too. I'm still not sure if it is a pakset or simutrans bug. Maybe it is in simutrans, due to the fact that the "this month" at the right sight of the finance window shows a negativ number and the monthly table the same amount as positiv maintenance.
how to-do:
- start new simutrans game with a high starting_money
- use "pause" to be sure you are doing the next steps in the same month
- build up the first HQ
- exactly replace the first HQ with the second one, don't use the destroy tool manually
- open finance window, remember the maintenance cost (one will be unequal zero)
- destroy the HQ
- reopen the finance window again, the last number in the row maintenance is negative
- start fast forward to the next month and you get the maintenance as a positive cash flow.
Well, as written this is a bug, but it behaves like a
"cheat mode", I can live with it.
The only thing is that it will take more than 66 month to earn the cash of the HQ construction cost, so the effect is very low.
Finally achieved reproducing this bug. I'm pretty sure the bug happens that way :
When upgrading HQ by rebuilding it elsewhere :
_ build HQ, add maintenance cost (324 c/month)
_ upgrade HQ, upgrade maintance cost (-> 972 c/month)
_ destroy HQ, remove maintenance cost according to the HQ (-> 972-972=0 c/month)
When upgrading HQ by rebuilding it at the same place (=> bug)
_ build HQ, add maintenance cost (324 c/month)
_ upgrade HQ, upgrade maintenance cost (this part is forgotten) (-> still 324 c/month)
_ destroy HQ, remove maintenance cost according to the HQ (-> 324-972= -648 c/month)
This is obviously a bug in the code, not in the pakset. This thread should be moved to the general bug reports section.
Moving :)
Please try r7356.
tested in r7356, bug is fixed, thanks.