Putting that many setprint events would be such a pain.
By idea is to make a playMovie event with one argument for movie selection, and then the movies themselves could be individual add-ons that create a scriptobject, that contains data about how many individual prints are in the movie, in which order they go, and how long between the frames, and then the playMovie event would access this scriptobject and play the movie accordingly.
The biggest problem I see with this is how to get the prints to be appliable to bricks without spamming the print list.