Search the Community

My US History scenario is coming along nicely. Having started in the 1820s, I have entered events part way into the great depression. I have over 180 events already in, and I have about that many more to go (including all of the presidential election headlines). My objective is to teach some history by having players experience it. Most of the events are one-time headliners, but most of those cascade effects via variables to about 30 events I'll have at the bottom of the stack to do the heavy lifting against companies and territories. I've read elsewhere that too many events can cause crashes, but I've also read about track destruction under moving trains doing likewise. In my testing so far, having a long list of events does not crash the game as long as I am careful to always stop trains before disasters. I'll offer up my scenario to y'all later to replicate my testing. I've also read that having many events can slow the game. As a programmer with experience going back to the 70s, I have an eye for efficiency. Besides collapsing many events into simple one-timers backed up by a few generics, I am also distributing event load among year-start, month-start, month-end, year-end and company-start. I am also confident that hardware improvements in the decade since RRT2's release will render performance issues moot. Expect an alpha release before Christmas! :) (It will be bundled with a modded v1.56 that enables military industries and cargoes in time for the civil war) EDIT: Since it's easy to find, this is the place to find updated US History maps attached