Your game will now be displayed in pretty colours. When you open a Quest game or library for the first time, go to the Language menu, and select XML. Notepad++ can be downloaded for free from here. Use Notepad++įor more advanced use, and for editing libraries, I would recommend using Notepad++. When you correct an error, you should be able to collapse that bit. The error is somewhere in whatever is left and cannot be collapsed.

If not, go through it and collapse all the elements that you can. If you can collapse the asl element at the top (or library element for a library), then your XML is formatted corrected. Errors in XMLĬollapsing elements is also a great way to find XML errors. Now you can copy or delete that line, confident that you have the entire XML element. Click the box, and the entire XML element will be collapsed into one line (and the - becomes +). Look down the left side you will see some lines have a - in a box. To ensure that never happens, collapse an element before manipulating it.

XML is very fussy, and you will get an error if end tags are missing or in the wrong order. Go into code view, press -F, and paste the offending code into the search box (bear in mind that the text could be in multiple places in your code).Īnother reason to use full code view is for a library file, as the Quest editor will not allow you to edit library files. Whilst playing your game, if Quest throws an error, it will often tell you the code that caused the error. So why use code view at all? One good reason is to find errors and typos. in full code view, but it is far easier to let Quest do that for you. It is a good idea to back up your game to another location first, just in case something goes wrong. It is not difficult to make changes in full code view that will cause Quest to be unable to load your game, so use with caution. NOTE: You can only access full code view in the desktop version. Tips and Tricks for Editing in Full Code View

Notepad++ compare plugin missing