Feature Request #4222
Allow more than 64 user-defined parameters
In order to make a nice basecost NewGRF it needs 70 parameters
This particular problem could either be solved by allowing to put more parameters (also ints) into one actual parameter (like the booleans) or it could be solved by lifting the restriction on the amount of user parameters.
I'm suggesting the latter, as it would also give NML the option to use the non-used part of the 64 user-parameters for varaction2 etc (or does it do that already? I got a bit lost when trying to find the places in the source)
#1 Updated by Hirundo over 7 years ago
Currently NML uses parameters 64-127 for internal calculations, while 0-63 are kept free for the user
We could detect what parameters are used, but that fails for param[param ]-like code
Perhaps an easy 'solution' would be to use the parameters 64-127 in reverse order, so 127 is used first by NML. Then, using 70 parameters, although not officially supported, would most likely work (unless NML needs more than 58 params).