actually, as the video shows, the Filetype for the list is set to "Image", but I guess in the previous version would kind of offer to insert the "get random item" node as an option while connecting... in any case I was able to go find some nodes to help me make the connection, but the behavior is definitely different than the previous version
in this screen capture video (no audio) I show how a node connection I had created in a comp built using Vuo 1.x still works when the comp is opened in Vuo 2 but is no longer possible to make as a new connection in Vuo 2 (I show it in the video by disconnecting and then attempting to reconnect) ;
Those numbers are currently auto-generated by Motion, not something that Vuo tries to control. As a result, the ID numbers aren't necessarily preserved as you add/remove/reorder published input ports.... To solve this, perhaps Vuo could generate an ID number for each published input port based on the port's name (similar to how it generates the UUID based on the bundle identifier). kingluma, does that seem like a reasonable solution to you?
I think it's reasonable, and renaming of a parameter could be done to the template in the Motion UI rather than Vuo (while still maintaining the ID number). This (defining/changing final param names in Motion) should allow for a way to rename parameters for improved clarity or localization in another language etc without creating incompatibilities with existing versions of the effect