We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A named parameter cannot be used for a house ID, instead throwing a Unrecognised identifier for the parameter name, for example:
Unrecognised identifier
house_id_1=5; item(FEAT_HOUSES, item_house_1, house_id_1) { ... }
Gives Unrecognised identifier for house_id_1. This seems like a bug:
house_id_1
"in theory it's supposed to work (https://github.com/OpenTTD/nml/blob/master/nml/ast/item.py#L55 looks for named params via https://github.com/OpenTTD/nml/blob/master/nml/global_constants.py#L1415), so it looks like a bug (but a hard to fix one I think"
"I guess it's similar to #299 check happens at parsing but the registration of house_id_1 is during preprocess step"
The text was updated successfully, but these errors were encountered:
A possible solution/workaround could be #302
Sorry, something went wrong.
No branches or pull requests
A named parameter cannot be used for a house ID, instead throwing a
Unrecognised identifier
for the parameter name, for example:Gives
Unrecognised identifier
forhouse_id_1
. This seems like a bug:"in theory it's supposed to work (https://github.com/OpenTTD/nml/blob/master/nml/ast/item.py#L55 looks for named params via https://github.com/OpenTTD/nml/blob/master/nml/global_constants.py#L1415), so it looks like a bug (but a hard to fix one I think"
"I guess it's similar to #299 check happens at parsing but the registration of house_id_1 is during preprocess step"
The text was updated successfully, but these errors were encountered: