RichardG867, on 31 January 2013 - 03:57 AM, said:
Released 3.0c, yet another UUID algorithm + nuclear control fixes.
I have two questions.
1) Should we count on the UUIDs being temporally unstable - therefore any internal database of item <-> UUID (compiled by actually scanning hundreds of items, not by code-searching) will potentially get broken in a next patch? The workaround is to have a sufficiently large chest next to the sorter with examples of items in a known order, and comparing the item being sorted using its ID with all of the example items. Is this the intended use?
2) With all due respect, is messing with the few people capable of decompiling your code or reverse-engineering the UUIDs in-game more important than the fact that the sorter still eats any and all items during sort() if they are already present in the target inventory? Please don't take me wrong, no offense intended. I like this mod, and I can't wait to be able to use it properly.