Skip to content
New issue

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

Feature: Engine name callback #276

Merged
merged 2 commits into from
Feb 1, 2023
Merged

Conversation

michicc
Copy link
Member

@michicc michicc commented Jan 30, 2023

Description

See OpenTTD/OpenTTD#10399.

Add basic support for the engine name callback and the extended callback flag properties.

Limitations

To make full use of the name callback in view of the limited D0xx text are that is available as a callback results, the OpenTTD PR also increases the D8xx text are up to FFFF (using up some TTDpatch specific IDs). Inclusion via the text stack and codes 80/81 can use all IDs and thus also D8xx.
So far, NML can not make use of this though, as all strings that are referred from Action 2s seem to be strictly allocated into the D0xx area. Reworking this is above my pay grade and thus not part of this PR.

nml/actions/action0.py Outdated Show resolved Hide resolved
@andythenorth
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants