Hey all,

Since W7K is a simulation, we’re going to spend much more time in the design doc phase this time around than the actual building phase. The idea is to work backwards: We start with W7K’s original set of 25 jobs, which should hopefully inform us of some potential event ideas. We then worry about crafting 100 events (enough to add spice to the sim loop) and then based on the events we can figure out what we need for all the events to make sense. When I made the python version I started the other way around (building the game loop then worrying about events) but what happened was that there was a ton of scope creep as I’d think of a cool idea but then would have to implement it in the loop itself. Now we’ll have all our cool ideas BEFORE the loop, which allows us to understand what the workload is at the front and cut if necessary.