Reply to Savebot Idea.
If you don't have an account, just leave the password field blank.
: [mumbling rambling mode on]
: The more you add the slowly Dink runs - and if you start playing around with init("load sequence...."); things can get ugly on low end machines.
: I'm currently testing Pilgrim's Quest on my old P200 MMX and it is verrrrry slow when loading screens with new graphics... let alone what I might find at the end of the DMOD when I started to use the init command to load new graphics. I use the save machine script to check which version of graphics need to be in which slots depending on the story... what this means is that when you go to a screen with a save machine... it takes a little while for Dink to actually step into that screen - kinda annoying, not sure what to do about that - I could go back to my first plan which was have the checking scripts fired of on loading weapons/magic... but that seemed to be double handling. Ahhhh.... when will this DMOD ever be finished!!!!
: [/end mumbling rambling]
Here's what I did in Crosslink: When you save the game, it sets a variable (&flag, a general purpose global I use, in this case) to a spesific value. Then it unsets it as soon as the game is saved. Then, when they load, the value is still set, so the savebot knows to do the start-up stuff (only) then.
: The more you add the slowly Dink runs - and if you start playing around with init("load sequence...."); things can get ugly on low end machines.
: I'm currently testing Pilgrim's Quest on my old P200 MMX and it is verrrrry slow when loading screens with new graphics... let alone what I might find at the end of the DMOD when I started to use the init command to load new graphics. I use the save machine script to check which version of graphics need to be in which slots depending on the story... what this means is that when you go to a screen with a save machine... it takes a little while for Dink to actually step into that screen - kinda annoying, not sure what to do about that - I could go back to my first plan which was have the checking scripts fired of on loading weapons/magic... but that seemed to be double handling. Ahhhh.... when will this DMOD ever be finished!!!!
: [/end mumbling rambling]
Here's what I did in Crosslink: When you save the game, it sets a variable (&flag, a general purpose global I use, in this case) to a spesific value. Then it unsets it as soon as the game is saved. Then, when they load, the value is still set, so the savebot knows to do the start-up stuff (only) then.
