type="list"
type="simplestringlist"
jaynabonne wrote:Be sure when you load the old game in 5.5 that you *save the game* in 5.5 before you run it. It's an odd thing, but it's necessary to upgrade the old file completely. I had the same message the other day with an old game, and that worked for me.
Pertex wrote:And you should have a look at http://docs.textadventures.co.uk/quest/ ... notes.html
The Pixie wrote:An issue I had, that I think causes the second of the two sympotoms you describe, is Quest changed how it reads list s from XML. Previously, if a list was tagged as:type="list"
... then it would become a string list. Now it needs to be:type="simplestringlist"
Opening the game in a text editor and searching for the former would be the best way to update the games.
It is just possible this will fix both errors (I have definitely seen them both).
TextStories wrote:"jaynabonne"
Be sure when you load the old game in 5.5 that you *save the game* in 5.5 before you run it. It's an odd thing, but it's necessary to upgrade the old file completely. I had the same message the other day with an old game, and that worked for me.
Hello. So you are saying I should copy the entire "old" game code as it is and simply paste it into this new version of 5.5 and then save it and it should work?
jaynabonne wrote:"TextStories"
[quote="jaynabonne"]Be sure when you load the old game in 5.5 that you *save the game* in 5.5 before you run it. It's an odd thing, but it's necessary to upgrade the old file completely. I had the same message the other day with an old game, and that worked for me.
Hello. So you are saying I should copy the entire "old" game code as it is and simply paste it into this new version of 5.5 and then save it and it should work?
Pertex wrote:Perhaps you could upload your game file here so we could have a look at it?
<asl>
hi my name is HK.
I love playing video games
</asl>
HegemonKhan wrote:when you used ' <asl version="520"> ', for your (preumably current download~install of quest) '550' version of quest.exe, it stopped right there, reporting that problem. When you changed it to "550", it's now able to continue to check your code lines, finding an error on line 55 position 82.
line 55 is literally your 55th line of your (code~text) file, and the position is your character space (starting from the left).
* I recommend you download notepad++ ( http://notepad-plus-plus.org/ ), as it's really useful. Once you got it up, choose for the (programming) language (bar at the top of the screen): XML
so for example (maybe it starts at zero instead of one, meh):
blah.aslx (your game file) 's contents, for pretend:<asl>
hi my name is HK.
I love playing video games
</asl>
line 2 position 1: h
line 3 pos 1: I
line 2 pos 7: n
line 3 pos 14: g
line 3 pos 22: g
-----------------------
invalid xml character errors have three possible common mistakes (but there's many other mistakes too, these are probably just the most common ones), that you can see if these are the cause of your xml char error:
you used a ' < ' or ' > ' in your scripting lines without the ' <![CDATA[ scripts ]]> ' tag block
or, when writing a tag, such as ' <attr name="strength">0</attr> ', you forgot for example: to put in an ' = ' sign or you forgot the ' / ' in the ending tag (I do this all the time, argh!).
or, you used, for example with script lines: ' ( ' instead of ' { ', or you forgot to add the ending ' } ' ... (like I do a lot also, argh!)
---------------
opening up your game file with notepad++ (and then selecting for its programming language at the top bar: XML), makes trouble shooting much easier, as it color codes your code structure making it easier to spot mistakes.
notepad++ will tell you where (line and position) your curser is at in your game file, so it's easy to find the ' line 55 position 82 ' location in your game file's coding
jaynabonne wrote:If you do wish to continue forward with trying to fix it, then what I would do is keep the 5.5 in the header and then tackle each error. The way I would do that is to create a new empty game in Quest and re-create on a small scale each construct (e.g. a string list, a string dictionary, a script dictionary, whatever you use that is causing an error) and see how the new Quest formats it in the file. Then use that to change the format in your old game file to match. I can't tell you off the top of my head how to format a script dictionary, but Quest can.