I asked about the M250 and am awaiting an answer. I suspect that it will be Type 118.

One thing to note about M-codes is that they are internal project code, not chassis/product codes in the sense of the IMCDb section.

Another thing - all of the chassis/product code entries of the form <number>/R<number> or <number>/<number> are actually <type number>/<chassis number>, that is, they identify individual cars. So they aren't chassis/product codes either. I know that I suggested 100T/1, but, as I think I noted earlier, I saw other chassis numbers for individual cars in that section and presumed that that kind of info went there.

Yes it does. We don't yet have a conflict between Type codes and Chassis #s so can run 2 parallel systems in the same box. But it is probably going to start happening at some stage, and we may need to rethink tactics/protocols. The new version - whenever it comes but not according to reports particularly imminent - may throw up a lot of these potential conflicts as it opens up [codes] across manufacturers. I'd guess carry on current practice in the meantime???

Not really imminent, there is still work
And links between manufacturers, models, etc. would be made manually
i.e. first a database of makes & models, and then roles and pictures linked to these, rather than having just the text entered for each role and the list generated from that, I do not know if it is clear what I say
So there won't be conflicts in that way, we'll be able to link together models or car generations without having to specify a same code in each of them.

To come back a project codes, sometimes they can be used as reference too. For example the model codes for Renault are usually derived from project codes.

The target audience for the site are car enthusiasts. So if they usually refer to cars of a given make by project codes, we can do that too, even if the manufacturer does not

Was this sorted in the end? Elise are still listed as Type M111...