loading variables between games
billchelonis
27 Apr 2004, 17:00What is the size limit on how much script Quest can compile?
Also, in case a game world did ever get too big, could you create another .asl or .cas file and have your first game load up the second, and not just that but import variables from the first? I guess you could use the shell command, right? Problem is in getting the variables from one game to the other though. That could be shell'd through a batch file to write the variables but then how would you go about reading them back again?
Also, in case a game world did ever get too big, could you create another .asl or .cas file and have your first game load up the second, and not just that but import variables from the first? I guess you could use the shell command, right? Problem is in getting the variables from one game to the other though. That could be shell'd through a batch file to write the variables but then how would you go about reading them back again?
Alex
27 Apr 2004, 17:09The size limit is currently 32767 of anything. I don't think anybody's got anywhere near that limit yet, but in future I will up the limit to 2 billion - which should be more than enough!
As for transferring variables etc. between games, there's no "nice" way to do this, but if you delete or rename the original ASL or CAS file before loading up the QSG, you can then select a different ASL or CAS file to "load" the game into - though if the player saved the game in a room which isn't in the new file, strange things will probably happen.
As for transferring variables etc. between games, there's no "nice" way to do this, but if you delete or rename the original ASL or CAS file before loading up the QSG, you can then select a different ASL or CAS file to "load" the game into - though if the player saved the game in a room which isn't in the new file, strange things will probably happen.
billchelonis
27 Apr 2004, 17:46Thanks. I don't think I'll hit that number myself. Was just wondering.
My fear is if I keep adding and adding to the game (a.k.a. like a Mudd or Muck) that at some point I'd run out of space. I seriously doubt I'll get the file up to the current limit though, but I am a bit wasteful in my over use of (hidden) objects in each room to account for the player examining things out of the room description that you can't necessarily take but might want to know more about. So at some point if I get enough really really object packed rooms I don't know if it'll bog down the CPU or crash the game or what. I worry about this stuff because I used to be a Lotus Notes database programmer and learned the hard way what the database did when it got too full.
Just bought the registered versoin of QDK the other day and have to say I really like it. Though I used to write all my script in text editors and for some languages I prefer it, I like having a script editor like this for writing text adventures. Seems to make it easier to see the object oriented programming in a visual format than wading through huge blocks of code. I messed with TADS a little and though it has its advantages, it doesn't seem to have any kind of script editor like this, so that's why I went with QDK. Anyhow back to work I guess.
My fear is if I keep adding and adding to the game (a.k.a. like a Mudd or Muck) that at some point I'd run out of space. I seriously doubt I'll get the file up to the current limit though, but I am a bit wasteful in my over use of (hidden) objects in each room to account for the player examining things out of the room description that you can't necessarily take but might want to know more about. So at some point if I get enough really really object packed rooms I don't know if it'll bog down the CPU or crash the game or what. I worry about this stuff because I used to be a Lotus Notes database programmer and learned the hard way what the database did when it got too full.
Just bought the registered versoin of QDK the other day and have to say I really like it. Though I used to write all my script in text editors and for some languages I prefer it, I like having a script editor like this for writing text adventures. Seems to make it easier to see the object oriented programming in a visual format than wading through huge blocks of code. I messed with TADS a little and though it has its advantages, it doesn't seem to have any kind of script editor like this, so that's why I went with QDK. Anyhow back to work I guess.