Thread:RickGT/@comment-35537717-20180509184247/@comment-34804319-20180509194201

While it indeed was implemented originally as an opponent, and it exists in the global table as a potential opponent in events, it is not called as there is no internal pointer specifically referencing the Polo's hex address as a valid value when the game searches for the specific range of opponent cars. For lack of an easy way to explain it, the Polo is not "enabled" if that makes any sense, although interestingly, if a cheat device is used to force it as an opponent, the game will not crash, which is usually does while forcing other invalid reference values, such as the various garbage data "No Name No Name" cars. Using a hex editor, you can watch this behaviour as the game reads the global list when selecting Event Synthesizer.

Now, as a side note, I cannot validate this in the NTSC-J 1.0 version as of this moment, however, I will fire it up once I get a chance.