made this little test and while you can only set one
cartdata address you can use run() to do it again with breadcrumbs
and such. this is both a stupid way to store data and the biggest
brain way possible. does anyone think this is a bug?
It definitely sounds like unintended behavior - I suppose it could be a problem if someone used it to very slowly fill the target's hard drive with persistent cart data files? Or worse, if someone wrote a cart to very slowly corrupt all the other cartridge data on the target's computer.
Not sure the most elegant way to patch it out - maybe put a restriction of 16 cartdata ids per cart during each time the cartridge is launched?
[Please log in to post a comment]