Reply to Re: Removing/changing limits in the source code
If you don't have an account, just leave the password field blank.
I'm not denying that Shevek's preprocessor scripts would be more readable. I'm just saying that the reason I would like a new scripting language is not for convienence or quality of life or anything, but added functionality, and Shevek's preprocessor language is just DinkC in terms of functionality.
'Supervars' allows values over 9. Read my advanced tutorial. The inventory system in MouseDink is very extensive (24 different slots with 35 different possible items for each slot.. so 24^35 different possible inventories) and is stored in 4 variables.
On the topic of supervars and Shevek's preprocessor, prehaps Shevek will like to integrate my 'supervar' read & write functions into his preprocessor. For most, that would effectively remove the var limit. The DMOD author would just have to specify the range of values their pseudovariables can have when they initialise them. And no custom exe would even be required. But of course, this doesn't remove the other limits.
'Supervars' allows values over 9. Read my advanced tutorial. The inventory system in MouseDink is very extensive (24 different slots with 35 different possible items for each slot.. so 24^35 different possible inventories) and is stored in 4 variables.
On the topic of supervars and Shevek's preprocessor, prehaps Shevek will like to integrate my 'supervar' read & write functions into his preprocessor. For most, that would effectively remove the var limit. The DMOD author would just have to specify the range of values their pseudovariables can have when they initialise them. And no custom exe would even be required. But of course, this doesn't remove the other limits.
