A Y2K Slip-Up by Access!
If you save a game now that we've entered the year 2000, you may notice something very odd on the date. See if you can find it:
![]()
Yes, you read it right. That date is 1/7/100. I myself can think of two reasons this my have happened. The game may have been programmed to, once the date hit January first each year, increment the year by 1. Unlikely though. More likely is that the last two digits in the date is calculated by taking the current year (2000) and subtracting 1900, giving you in this case 100. But I assure you, The Pandora Directive still runs perfectly fine, otherwise how could I have taken this shot? I have checked UAKM and Overseer for this bug, but they are both fine, saying that today's date (at least today when I wrote this) is 1/7/00.