Reply to Re: Custom procedures
If you don't have an account, just leave the password field blank.
Yes, you can only return 1 value from a custom procedure. If you're calling a custom procedure you get &arg1 to &arg9, if you're calling via external you only get up to &arg8.
For the single return value thing, a workaround is you can save as many values as you want without extra variable use by using sp_custom values attached to Dink.
sp_custom("return1", 1, ###);
sp_custom("return2", 1, ###);
Etc...
Then retrieve whenever you want. There's no limit to sp_custom values. You can store as many as you want with Dink, and they'll survive screen changes. They just don't save with save game. They are also I think the only value you can set/retrieve in DinkC that is instance specific. Meaning they also survive through loading a save game... If you set a sp_custom value on Dink, load a save game and retrieve it, it'll be the value you set before you loaded. You only lose the "memory" of sp_custom values on Dink when the game is closed.
For the single return value thing, a workaround is you can save as many values as you want without extra variable use by using sp_custom values attached to Dink.
sp_custom("return1", 1, ###);
sp_custom("return2", 1, ###);
Etc...
Then retrieve whenever you want. There's no limit to sp_custom values. You can store as many as you want with Dink, and they'll survive screen changes. They just don't save with save game. They are also I think the only value you can set/retrieve in DinkC that is instance specific. Meaning they also survive through loading a save game... If you set a sp_custom value on Dink, load a save game and retrieve it, it'll be the value you set before you loaded. You only lose the "memory" of sp_custom values on Dink when the game is closed.
