Reply to dPlay (explained)
If you don't have an account, just leave the password field blank.
: this is a program open with dink or is it all inside of dink? that would be pretty neat. I think redink1 kind of forgot to explain this in full (I knew about it earlier)
It's an external program but the d-mod can access it because it pretends to be the avi player that came with the CD version of Dink. DinkC includes a rarely (if ever) used command called playavi to access this program and pass it a text string (originally an avi file name).
So basically the idea is to use that single access point to the outside world to cram new things into Dink.
Comunication between the two programs is somewhat limited, but it gets the initial command line from the playavi command and can read variables out of save games and create .c files (which would then be run by the d-mod) as a way to set variables.
But it could do pretty much anything any program could do, at least in theory. Actually programing some thing could be tricky of course. Redink1 is doing this in perl, which I don't know anything about unfortunatly.
It's an external program but the d-mod can access it because it pretends to be the avi player that came with the CD version of Dink. DinkC includes a rarely (if ever) used command called playavi to access this program and pass it a text string (originally an avi file name).
So basically the idea is to use that single access point to the outside world to cram new things into Dink.
Comunication between the two programs is somewhat limited, but it gets the initial command line from the playavi command and can read variables out of save games and create .c files (which would then be run by the d-mod) as a way to set variables.
But it could do pretty much anything any program could do, at least in theory. Actually programing some thing could be tricky of course. Redink1 is doing this in perl, which I don't know anything about unfortunatly.
