QDK 2.X & 3.X - Axe Software Forums

  Axe Software Forums
  Quest Developer Forum
  QDK 2.X & 3.X

Author Topic:   QDK 2.X & 3.X

DarkAng3l posted 28-11-2001 21:22 GMT
How can I transform games made for Quest 2.1.8 to games for Quest 3.02?
Alex posted 28-11-2001 22:50 GMT
I think the best advice is - DON'T!
But if you must, look in the Quest Documentation under "Notes for users of Quest 2.x".
DarkAng3l posted 30-11-2001 20:24 GMT
Why? Anyway, I am going to keep a 2.X copy in my disk. Another copy will be transformed into asl3, or whatever it is called...
Alex posted 01-12-2001 12:52 GMT
I recommend you don't convert ASL2 to games to ASL3 because ASL3 is very different from ASL2, so you might end up taking a while to do it.
But if you are going to do it, your idea of keeping an ASL2 copy as backup is a very good one.
DarkAng3l posted 01-12-2001 22:28 GMT
I know that! How to convert? Can I do it automatically, or should I rewrite the game back from the scratch by hand?
Alex posted 01-12-2001 23:18 GMT
There's no automatic way of converting ASL2 to ASL3, but you could do it by hand I suppose - not a fun task though, which is why it's not something I suggest you try! Basically you just need to go through your code armed with the "notes for users of Quest 2.x" in the documentation and a bit of patience... or just finish your game using ASL2, which is of course still fully supported in Quest 3.x.
Computer Whizz posted 02-12-2001 01:08 GMT
Use the "replace" in wordpad or any useful word processor!
search for things such as "setnum" and replace with "set numeric" ect...
Then there are only a few more things to change (items, collectables).
Computer Whizz
Alex posted 02-12-2001 13:09 GMT
It's the replacing items and collectables that's the "hard" part - you'd have to create a "define variable" block for each collectable, change your take-able objects so they don't hide themselves and give "items" to the player, and change any give/use code. There's a number of ways you might do the above to convert your ASL2 game to ASL3, which is why there's no automatic conversion utility.

Author	Topic: QDK 2.X & 3.X
DarkAng3l	posted 28-11-2001 21:22 GMT How can I transform games made for Quest 2.1.8 to games for Quest 3.02?
Alex	posted 28-11-2001 22:50 GMT I think the best advice is - DON'T! But if you must, look in the Quest Documentation under "Notes for users of Quest 2.x".
DarkAng3l	posted 30-11-2001 20:24 GMT Why? Anyway, I am going to keep a 2.X copy in my disk. Another copy will be transformed into asl3, or whatever it is called...
Alex	posted 01-12-2001 12:52 GMT I recommend you don't convert ASL2 to games to ASL3 because ASL3 is very different from ASL2, so you might end up taking a while to do it. But if you are going to do it, your idea of keeping an ASL2 copy as backup is a very good one.
DarkAng3l	posted 01-12-2001 22:28 GMT I know that! How to convert? Can I do it automatically, or should I rewrite the game back from the scratch by hand?
Alex	posted 01-12-2001 23:18 GMT There's no automatic way of converting ASL2 to ASL3, but you could do it by hand I suppose - not a fun task though, which is why it's not something I suggest you try! Basically you just need to go through your code armed with the "notes for users of Quest 2.x" in the documentation and a bit of patience... or just finish your game using ASL2, which is of course still fully supported in Quest 3.x.
Computer Whizz	posted 02-12-2001 01:08 GMT Use the "replace" in wordpad or any useful word processor! search for things such as "setnum" and replace with "set numeric" ect... Then there are only a few more things to change (items, collectables). Computer Whizz
Alex	posted 02-12-2001 13:09 GMT It's the replacing items and collectables that's the "hard" part - you'd have to create a "define variable" block for each collectable, change your take-able objects so they don't hide themselves and give "items" to the player, and change any give/use code. There's a number of ways you might do the above to convert your ASL2 game to ASL3, which is why there's no automatic conversion utility.