All the work we’re doing will ultimately allow us to recreate an authentic classic experience on a platform that is much more optimized and stable, helping us avoid latency and stability issues. Additional improvements will include modern anti-cheat/botting detection, customer service and integration, and similar conveniences that do not affect the core gameplay experience.
Once we had our starting point, we began taking stock of what we had in the source code and what we could make available, which included restoring the original development database from archival backups. After stitching various key pieces together, we had a locally rebuilt version of Patch 1.12 running internally. The team could create characters and do basic questing and leveling—and dying, which we did many times. For testing purposes. Obviously. 

While our initial effort helped us determine the experience we wanted to provide, this second prototype really defined how we’d get there. Starting from a modern architecture—with all its security and stability changes—means the team’s efforts can be focused on pursuing an authentic classic experience. Any differences in behavior between our development builds and the patch 1.12 reference can be systematically cataloged and corrected, while still operating from a foundation that’s stable and secure.
 ":"  -  Any time a step ends in a ":" instead of a "." means that the next step is part of the current step you are on.  This generally means the next step should be done while working on the current step.  This means every "start working on" or "continue working on" will end in a ":".  But this is used with other occasions as well, so keep this in mind.