Callback: Station slope check - Revision history

Frosch: use new grf templates

2012-04-01T13:33:19Z

use new grf templates

← Older revision		Revision as of 13:33, 1 April 2012
Line 3:		Line 3:
	This callback is called for each tile where the new station part will be built.		This callback is called for each tile where the new station part will be built.

	{{~~grf~~\|7}} For GRF version 7 and below the return values are the same as for [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]], but with bit 10 inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable".		{{grfTill\|7}} For GRF version 7 and below the return values are the same as for [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]], but with bit 10 inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable".
	Note that earlier version of OpenTTD before r22658 and TTDPatch only support 0 for success and 1 for error.		Note that earlier version of OpenTTD before r22658 and TTDPatch only support 0 for success and 1 for error.

	{{~~grf~~\|8}} For GRF version 8 and above the return values are the same as for [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]]. Return value 401 stands for "Land sloped in wrong direction" instead of "Site unsuitable".		{{grfFrom\|8}} For GRF version 8 and above the return values are the same as for [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]]. Return value 401 stands for "Land sloped in wrong direction" instead of "Site unsuitable".

	Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:		Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:

Frosch: grf version 8

2011-11-09T01:08:09Z

grf version 8

← Older revision		Revision as of 01:08, 9 November 2011
Line 1:		Line 1:
	== Station slope check (149) ==		== Station slope check (149) ==

			This callback is called for each tile where the new station part will be built.
⚫	~~This~~ ~~callback~~ is ~~called~~ ~~for~~ ~~each~~ ~~tile where~~ the ~~new~~ ~~station~~ ~~part~~ ~~will~~ be ~~built.~~ ~~For OpenTTD since r22658 allowed return values are like~~ [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]], but with ~~the difference that the meaning of~~ bit 10 is inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable"~~. Earlier version of OpenTTD and TTDPatch only support 0 for success and 1 for error~~.

		⚫	{{grf\|7}} For GRF version 7 and below the return values are the same as for [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]], but with bit 10 inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable".
			Note that earlier version of OpenTTD before r22658 and TTDPatch only support 0 for success and 1 for error.

			{{grf\|8}} For GRF version 8 and above the return values are the same as for [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]]. Return value 401 stands for "Land sloped in wrong direction" instead of "Site unsuitable".

	Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:		Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:

Frosch: remove object specific stuff

2011-08-27T21:24:33Z

remove object specific stuff

← Older revision		Revision as of 21:24, 27 August 2011
Line 1:		Line 1:
	== ~~Land~~ slope check (149~~/157~~) ==		== Station slope check (149) ==

	This callback is called for each tile where the new station part will be built. For OpenTTD since r22658 allowed return values are like [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]], but with the difference that the meaning of bit 10 is inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable". Earlier version of OpenTTD and TTDPatch only support 0 for success and 1 for error.		This callback is called for each tile where the new station part will be built. For OpenTTD since r22658 allowed return values are like [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]], but with the difference that the meaning of bit 10 is inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable". Earlier version of OpenTTD and TTDPatch only support 0 for success and 1 for error.
Line 33:		Line 33:
	The callback is called only after the normal checks TTD does for slopes, so it's not possible to allow a slope that isn't allowed by default; you can only narrow the set of allowed slopes. If the callback fails, the tile will be accepted. It is, however, called for flat tiles, so you can force your station to sloped land. You can't access the station info even if the platform is added to an existing rail station or is overbuilding station tiles. That's because TTD will decide this later in the code, after the slope is already accepted.		The callback is called only after the normal checks TTD does for slopes, so it's not possible to allow a slope that isn't allowed by default; you can only narrow the set of allowed slopes. If the callback fails, the tile will be accepted. It is, however, called for flat tiles, so you can force your station to sloped land. You can't access the station info even if the platform is added to an existing rail station or is overbuilding station tiles. That's because TTD will decide this later in the code, after the slope is already accepted.

	Please note that for Objects only the low byte of variable 18 is valid (Offset from north tile (origin), stored as YX) and that variable 10 does not have the reversed version, and bits 0 - 3 contain the actual raised corners (same order as bits 4 - 7).
	[[Category:Callbacks]]		[[Category:Callbacks]]

Frosch: moved Callback: Land slope check to Callback: Station slope check: objects will get separate page

2011-08-27T21:23:08Z

moved Callback: Land slope check to Callback: Station slope check: objects will get separate page

← Older revision	Revision as of 21:23, 27 August 2011
(No difference)

Michi cc: Specify OpenTTD revision

2011-07-11T16:40:34Z

Specify OpenTTD revision

← Older revision		Revision as of 16:40, 11 July 2011
Line 1:		Line 1:
	== Land slope check (149/157) ==		== Land slope check (149/157) ==

	This callback is called for each tile where the new station part will be built. ~~Allowed~~ return values are like [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]], but with the difference that the meaning of bit 10 is inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable".		This callback is called for each tile where the new station part will be built. For OpenTTD since r22658 allowed return values are like [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]], but with the difference that the meaning of bit 10 is inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable". Earlier version of OpenTTD and TTDPatch only support 0 for success and 1 for error.

	Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:		Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:

Michi cc: link fix

2011-07-11T16:26:16Z

link fix

← Older revision		Revision as of 16:26, 11 July 2011
Line 1:		Line 1:
	== Land slope check (149/157) ==		== Land slope check (149/157) ==

	This callback is called for each tile where the new station part will be built. Allowed return values are like [[#Industry_location_permissibility_.2828.29\|callback 28]], but with the difference that the meaning of bit 10 is inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable".		This callback is called for each tile where the new station part will be built. Allowed return values are like [[Callbacks#Industry_location_permissibility_.2828.29\|callback 28]], but with the difference that the meaning of bit 10 is inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable".

	Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:		Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:

Michi cc: /* Land slope check (149/157) */ Custom error messages.

2011-07-11T16:25:00Z

Land slope check (149/157): Custom error messages.

← Older revision		Revision as of 16:25, 11 July 2011
Line 1:		Line 1:
	== Land slope check (149/157) ==		== Land slope check (149/157) ==

	This callback is called for each tile where the new station part will be built. ~~It can~~ return ~~zero~~ to ~~accept~~ ~~the~~ ~~current~~ ~~tile~~ or ~~one~~ to ~~make~~ the ~~station~~ ~~building~~ ~~fail~~ ~~with~~ ~~the~~ ~~"Land~~ ~~sloped~~ in ~~wrong~~ ~~direction"~~ ~~error~~ ~~message.~~ ~~Other~~ ~~return~~ ~~values~~ ~~are~~ ~~reserved~~ ~~for~~ ~~future~~ ~~use,~~ ~~don't~~ ~~use~~ ~~them~~ for ~~now~~.		This callback is called for each tile where the new station part will be built. Allowed return values are like [[#Industry_location_permissibility_.2828.29\|callback 28]], but with the difference that the meaning of bit 10 is inverted for backwards compatibility. This means that success is 0 instead of 0x400 while custom GRF texts start at 0x400 instead of 0. Return value 1 stands for "Land sloped in wrong direction" instead of "Site unsuitable".

	Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:		Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:
Line 31:		Line 31:
	\|}		\|}

		⚫	The callback is called only after the normal checks TTD does for slopes, so it's not possible to allow a slope that isn't allowed by default; you can only narrow the set of allowed slopes. If the callback fails, the tile will be accepted. It is, however, called for flat tiles, so you can force your station to sloped land. You can't access the station info even if the platform is added to an existing rail station or is overbuilding station tiles. That's because TTD will decide this later in the code, after the slope is already accepted.
	The callback is called only after the normal checks TTD does for slopes, so it's not possible

⚫	to allow a slope that isn't allowed by default; you can only narrow the set of allowed slopes. If the callback fails, the tile will be accepted. It is, however, called for flat tiles, so you can force your station to sloped land. You can't access the station info even if the platform is added to an existing rail station or is overbuilding station tiles. That's because TTD will decide this later in the code, after the slope is already accepted.

	This is called if available just before object construction, it does not require that any flags be set in the action0.

	Please note that for Objects only the low byte of variable 18 is valid (Offset from north tile (origin), stored as YX) and that variable 10 does not have the reversed version, and bits 0 - 3 contain the actual raised corners (same order as bits 4 - 7).		Please note that for Objects only the low byte of variable 18 is valid (Offset from north tile (origin), stored as YX) and that variable 10 does not have the reversed version, and bits 0 - 3 contain the actual raised corners (same order as bits 4 - 7).

Pm-bot: Create a separate page for each callback

2011-06-16T18:58:24Z

Create a separate page for each callback

New page

== Land slope check (149/157) ==

This callback is called for each tile where the new station part will be built. It can return zero to accept the current tile or one to make the station building fail with the "Land sloped in wrong direction" error message. Other return values are reserved for future use, don't use them for now.

Since the station isn't built yet, no 8x variables can be accessed. Only variables 43 and 67 will work from the 4x and 6x variables. You get the following information, though:
* variable 18:
{| |-
!bit numbers!!Meaning
|-
|0..7||offset of current tile on the platform, 0 is the northmost tile
|-
|8..15||bits 8..15: current platform number, 0 is the northmost platform
|-
|16..23||total length of station being built
|-
|24..31||total number of platforms being built
|}
* variable 10:
{| |-
!bit numbers!!Meaning
|-
|4..7||Slope info of the current tile:
* bit 7 - N corner is elevated
* bit 6 - E corner is elevated
* bit 5 - S corner is elevated
* bit 4 - W corner is elevated
|-
|0..3||the same information, but "mirrored" (bit 0 and 2 swapped) if the station is built in the NW-SE orientation. This allows you to check slopes without checking the orientation explicitly.
|-
|other bits||reserved for future use
|}

The callback is called only after the normal checks TTD does for slopes, so it's not possible

to allow a slope that isn't allowed by default; you can only narrow the set of allowed slopes. If the callback fails, the tile will be accepted. It is, however, called for flat tiles, so you can force your station to sloped land. You can't access the station info even if the platform is added to an existing rail station or is overbuilding station tiles. That's because TTD will decide this later in the code, after the slope is already accepted.

This is called if available just before object construction, it does not require that any flags be set in the action0.

Please note that for Objects only the low byte of variable 18 is valid (Offset from north tile (origin), stored as YX) and that variable 10 does not have the reversed version, and bits 0 - 3 contain the actual raised corners (same order as bits 4 - 7).
[[Category:Callbacks]]