GRF Tools » NewGRF Meta Language

Mostly a bug-fix release for the 0.2 branch, but it also adds some minor features mostly in the form of previously unsupported variables/callbacks. The decision to add those features was made because the 0.3 branch which is currently work-in-progress does not and will not support OpenTTD 1.1 and older. Since there are still people wanting to make their NewGRFs available for people with older OpenTTD versions they can keep using the 0.2 branch.

Full changelog for this release:
- Feature: Report NML line information as well as pixel position for pure white pixels. Also, report number of pixels in the sprite, instead of the whole image. (issue #4029)
- Feature: 'signals' callback for railtypes.
- Feature: Allow the 'nfo' unit to be used with non-constant values. (issue #3828)
- Feature: 'build_prod_change' callback for industries to set industry production level on construction.
- Feature: Constant CB_RESULT_REFIT_COST_MASK
- Feature: Vehicle misc_flag VEHTYPE_FLAG_NO_BREAKDOWN_SMOKE.
- Feature: 'current_max_speed' variable for vehicles. (issue #3979)
- Feature: 'vehicle_is_in_depot' variable for aircraft.
- Feature: 'range' property and callback for aircraft.
- Feature: 'production_rate_1/2' variables for industries.
- Feature: 'town_zone' variable for railtypes.
- Feature: 'other_veh_(curv_info|is_hidden|x_offset|y_offset|z_offset)' variables for vehicles.
- Fix: Provide a proper error message when running out of action2 IDs
- Fix: A '{' at the end of a string could cause a crash
- Fix: Backslash-escapes in strings weren't properly validated. Also remove useless \n escape. (issue #3636)
- Fix: Provide a proper error message if a substring is missing, instead of an assertion error. (issue #3932)
- Fix: 'refit_cost' callback may also be called from the purchase menu.
- Fix: Allow using constants > 255 as variable parameter. (issue #4086)
- Fix: Sprite layout register code contained an unsorted iteration over dictionary keys, resulting in possible regression failures.

A bug-fix release from the 0.2 branch. No major new features, just a few new constants to make porting projects to NML 0.3 easier and some bug-fixes.

• Add: CB_RESULT_NO_MORE_ARTICULATED_PARTS, CB_RESULT_REVERSED_VEHICLE and CB_RESULT_NO_TEXT as constants to make porting projects to NML 0.3 easier.
• Fix: Internal error when the ID in a replace-block was not a compile-time constant
• Fix: Crash when referencing a SpriteSetCollection in a graphics-block that was inside an if-block
• Fix: Text files in docs/ were not included in source package
• Doc: Add GPL v2 header to all .py files

1.5 years after starting with NML we can finaly released version 0.2.0. The list of features, changes and fixes since 0.1 is too long to list. If all the features you want are supported by NML 0.2, we urge you to keep using it. NML 0.3 might have a few syntax-breaking changes, although we'll try to prevent that.

The 0.2 branch will be updated for a while with fixes, and this will be the last version to support OpenTTD 1.1.x. Starting with 0.3, NML will put it's focus on OpenTTD 1.2+.