Opps sorry, I think at the front.. atleast it moves the cursor to that postion. Hope that is what you mean.
But I found something I don't understand..
See I just put that code into a script to try get the error location and it worked perfect with the code; no errors, could hear the voices and cars didn't talk.
?(true):{{[_x] exec "snds.sqs"} forEach (crew vehicle _x)} forEach list trigname
So the only thing that changed was that instead of thislist I put list trigname because I had too.
Now here comes the real confusing bit (for me atleast), when I put that same code into the triggers condition field (using the triggers name again), it gives me the same error as before and points the cursor at the start?
Well regardless, the problem is solved as I can just launch it from the init so thanks again for your help and interest guys, but if anyone knows why this is working in a script but not a trigger it would be really helpful if you could inform as to why this is happening (probably a stupid mistake I overlooked but I did try alot of testing).
Edit: No your on your game Loyal, just i'm not
Turns out if I add the ";" onto the end it works. I have never used one of them in a condition field in the past, so didn't think twice about it.
That also explains why it would work in a sqs script
This topic is solved now, thanks very much I learned alot!