Talk:Making a Re-Patch/@comment-86.158.102.196-20140420023345

This is incredible, thanks guys, my issue is solved, I moved the onscripter to my desktop and i played around with the name of my script too. The name of the script was "mine.txt" and in the cmd I typed in "mine.txt", which the cmd would then tell me it cannot be opened for reading. So then I was annoyed and decided to put nscmake [random jibberish] basically random words which wasn't the name of any folder, and it gave me the same error "could not be opened for reading"... So I thought it must be my naming, so I named my script "mine" but inserted "mine.txt" after nscmake... I think the problem is that it was a txt file and the name was "mine.txt" that confused the system maybe? I'm not sure but it works now, thanks a lot :D

A new issue that you guys are now familiar with that could come up maybe lol