Ok. So, again without any code or samples, its still a bit tricky to debug here. However, I did want to mention a few things. The default behavior of the GrasshopperPlayer was to actually keep the file open (even after it’s run). This was a decision made specifically for definitions that were using things like Human UI. We did recently introduce a new boolean toggle in the Document Properties which allows you to be explicit about whether you want to keep the document open or closed when running the GrasshopperPlayer command. This was only added in the latest Rhino 8 WIP… but you might try your files in Rhino 8 WIP and see if there’s any difference there.
I’m honestly not sure if looping is supported in general when run as a command. I haven’t test this in hops, so if you have a simple looping example you could upload here, that would be helpful.
1 Like