Reply to thread

Message

<blockquote data-quote="viperguy" data-source="post: 1246528" data-attributes="member: 79833">Just after a little help...For the life of me i cannot use the playfile command to actually start a file playing, no matter how many (or how few) escape backslashes I use in my file path I always get a &quot;Bad JSON&nbsp; escape sequence: \x&quot; message in my logs.The x here is whatever character happens to follow the first backslash I'm trying to escape.The command documentation shows a file path with no escaped backslashes but no matter how I format the path i continue to get the error.....I've tried running my path through a JSON formatter/checker and using the results of that but no dice. Even when the path is as simple as c:\xxx it still complains, so I'm officially going mad from trying to escape slashes <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Many thanks in advance</blockquote>

[QUOTE="viperguy, post: 1246528, member: 79833"] Just after a little help... For the life of me i cannot use the playfile command to actually start a file playing, no matter how many (or how few) escape backslashes I use in my file path I always get a "Bad JSON escape sequence: \x" message in my logs. The x here is whatever character happens to follow the first backslash I'm trying to escape. The command documentation shows a file path with no escaped backslashes but no matter how I format the path i continue to get the error.....I've tried running my path through a JSON formatter/checker and using the results of that but no dice. Even when the path is as simple as c:\xxx it still complains, so I'm officially going mad from trying to escape slashes :) Many thanks in advance [/QUOTE]

Verification