Well what I meant was that ^K99 has always had this behaviour, unlike ^K16-98, and this behaviour is emulated in some other IRC clients which may treat ^K16-98 differently (ie. as additional colours), so it's important that any IRC client developers implementing the colour scheme realise that if they want to plow ahead and use additional colours for numbers >16 they should still treat ^K99 as a "return to default" instead of trying to make it a specific colour.
