Rather than events and event structures you could probably use a simple waiting while loop or timed loop with shift registers to pass the previous value for all your items from the last iteration and compare them to the current values. If all you care about is that some value has changed and you aren't as concerned as to which, you could combine the items into a single array or cluster so you only have to do one comparison because the comparison will note if any element has changed.
Some of the comparison tools and even math operators and the array search functions could even be used to identify what element specifically changed if you need to do something different depending on what item changed. In any event that is a lot of items to keep track of to have everything be a separate item. If there are at least a few specific groupings that have similar actions then you could use several timed loops that have the nice advantage of being able to run simultaneously yet do there own things that you could at least subdivide the checks somewhat.
If the cluster operators were more versatile like the array, string, and number pallets then I'd use them far more myself; but most are limited and very inflexible when you mix and match data types. Clusters provide visual grouping, individual element "naming", yet gives you just one item to have to deal with until you need to do something to a specific element in which case the pallet has a few useful tools for that.
-Leif
