It's almost impossible to do anything about bugs that I can't reproduce. Step 1 is to reproduce the problem, so I'm still stuck on step 1.
I'm with you on that, but the usual methods of achieving that step don't seem to be working. Perhaps we need to think outside the box.
I'll try to keep this little story brief. Back in the days of Windows XP, there was a crash bug that afflicted
many users in every game, and for a significant period of time, no developer knew why. EA would just tell you that "you didn't meet the minimum requirements", even though their own utility said the opposite. Then, Valve stepped up and said, "ok, someone send us a computer that can reproduce the crash". Someone did, and then Valve found the cause. Users were running out of paged pool memory, as windows wasn't allocating enough for some arbitrary reason. The problem was worked around with a registry tweak that forced windows to allocate more, and the problem was fixed for good in Windows Vista.
That being said, I don't think the cause of this Construct 2 bug is so obscure as to require shipping a computer to you. So, lets try some other options first.
I am able to reproduce the bug in a virtual machine, so perhaps I can let you remote in to it, and you can do as you will with it?
I could probably reproduce it on a virtual machine provided by you. I have yet to find a computer that I can't reproduce this on.
Perhaps I could send you a virtual machine with a save state?
If you have better suggestions, I'm all ears.