You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Applies to opentdd 5.0.0 rc2 & 3, maybe even older versions:
When you call a train which is unloading its cargo into service INSTANTLY after you recieved the payment, mostly all of the cargo (e.g. 25/30tons)remains on the train (because it will stop unloading and leave for service immediately). Now you need to have a station built nearby, which does not accept your cargo, where you can send your train to load again. Of course it won't load anything and will leave for the next station on its route, which has to be the station which accepts your cargo, again. You will recieve money for your cargo once more, although the reduced cargo and extended time you need for deliviering will reduce the payment, as well (it still will be very good!). If you are fast enough, you can do this trick over and over again, untill your cargo is completely unloaded. This doesn't make any sense, though, since the time factor significantly reduces the income after 2 times or so.
Although this bug is a little complicated and time-consuming to carry out you have to keep in mind, that the longer the trail, the more it pays off to cheat in this way (shorter way to the fake-station, VERY short "reloading-time" (station has to be size of the train!), very good double, maybe triple income; example: I had a very long train running on a very long trail with coal, income around 480.000$ per load (once a year because it was so far away). With this cheat I earned 430.000$ EXTRA after only a few DAYS! This bug can give a significant advantage when playing in multiplayer!
Screenshot with example setup added. On such a short trail this does not make sense.
seismic opened the ticket and wrote:
Attachments
Reported version: trunk
Operating system: All
This issue was imported from FlySpray: https://bugs.openttd.org/task/539
The text was updated successfully, but these errors were encountered: