Jens,
I understand your problem but as the subroutines are open source you could easily reuse the &decloak subroutine again to decode the ID for other scripts.
There is actually no choice as the coding/decoding is integrated everywhere, however it is only the surface layer (so the visible one).
Internally the whole board still works with good old readable ID's.
But look at boards like SMF, they user cryptic ID's everywhere and a user is refered to as u=123456 or some number.
The decoding of the ID is a simple shifted HEX/ASCII routine of 5 lines so it should not be too hard to re-use and the content of the cookies is exactly the same as it is now so no worries about using cookies, nothing changed there.
Just check the cookie you got from this board and see that there is nothing crypted there other then the password and the session id
To show you the present cookie, taken from my dev board:
Quote:Y2User-61617
admin
www.spikecity.net/ 1536
1638612992
32111473
598524144
29746111
*
Y2Pass-61617
*****************
www.spikecity.net/ 1536
1638612992
32111473
600714144
29746111
*
Y2Sess-61617
********************
www.spikecity.net/ 1536
1638612992
32111473
600874144
29746111
*