Bug #7615

Issues with Name property

Added by Supercheese over 4 years ago. Updated over 4 years ago.

Status:NewStart date:2015-04-09
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Attached are two patched versions of OGFX+ Airports, one which adds a new small seaplane port successfully, but avoids setting the name property.

The only difference between the two is the addition of the name property, but this causes OTTD to complain of invalid ID access.

The relevant code difference is:

item(FEAT_AIRPORTS, seaplane_airport) {
property {
override: 0;
layouts: [
small_airport_layout_seaplane_north,
small_airport_layout_seaplane_east,
...

Versus:

item(FEAT_AIRPORTS, seaplane_airport) {
property {
name: string(STR_SEAPLANE_AIRPORT);
override: 0;
layouts: [
small_airport_layout_seaplane_north,
small_airport_layout_seaplane_east,
...

Not sure what's going on here, and I do not know of any other grfs that modify airports...

OGFX+ seaplane airport no name.grf (1.06 MB) Supercheese, 2015-04-09 07:44

OGFX+ seaplane airport with name.grf (1.06 MB) Supercheese, 2015-04-09 07:44

History

#1 Updated by Supercheese over 4 years ago

The issue here was with the name property being set before/above the override property. Moving the override above the name fixes the issue; this task can now be closed.

Also available in: Atom PDF