No error when tram_type property is set without a tram typetable

Open
#398 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

No file or test is named in the issue. Start by tracing validation for tram_type, tramtypetable, and ROADVEH_FLAG_TRAM, then reproduce the missing-property cases; done means NML reports an error for the stated scenario and clarifies any related tram consistency checks.

Written by the indexing model from the issue text.

Description

If a tram is created with no tram_type property, OpenTTD will use the default ELRL. But if a tram_type property is set (even to ELRL) without a tramtypetable, OpenTTD does not default to ELRL

NML should throw an error in this scenario.

Possibly also around some similar "You've set tram_type but no ROADVEH_FLAG_TRAM" edge cases (and vice versa), if required, I generally found it a bit confusing to create a tram with no feedback when I was missing properties and multiple are required

Dominant language
Python
Stars
61
Forks
47
Avg merge
8d 14h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenTTD/nml

All issues in OpenTTD/nml

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.