Callback: Custom shape check - Revision history

Frosch: use new grf templates

2012-04-01T13:28:10Z

use new grf templates

← Older revision		Revision as of 13:28, 1 April 2012
Line 3:		Line 3:
	This callback is called when TTD checks if a given tile is suitable for the industry tile. The callback should return zero if the tile isn't suitable, or any other value if it is suitable.		This callback is called when TTD checks if a given tile is suitable for the industry tile. The callback should return zero if the tile isn't suitable, or any other value if it is suitable.

	{{~~grf~~\|7}} The meaning of the returned value is different in GRF version 7; it works the same way as [[Callbacks#Industry location permissibility (28) \|callback 28]]. {{ottdp\| \|2.6\|ttdprev=r1755}} Also, since TTDPatch r1755, you can use the text reference stack for your error messages, similarly to [[#Show_additional_text_in_industry_window_.283A.29 \|callback 3A]]. The only difference is that only 4 registers are copied instead of 6.		{{grfFrom\|7}} The meaning of the returned value is different in GRF version 7; it works the same way as [[Callbacks#Industry location permissibility (28) \|callback 28]]. {{ottdp\| \|2.6\|ttdprev=r1755}} Also, since TTDPatch r1755, you can use the text reference stack for your error messages, similarly to [[#Show_additional_text_in_industry_window_.283A.29 \|callback 3A]]. The only difference is that only 4 registers are copied instead of 6.

	Since the tile isn't built yet, you can use variables 41, 42, 43, and 60 only, and you can't access any industry variables, either. Variable 60 is the most useful here, since you can check the slope of the tile, or even the nearby tiles. This callback is the only way to allow your tile to be built on steep slopes.		Since the tile isn't built yet, you can use variables 41, 42, 43, and 60 only, and you can't access any industry variables, either. Variable 60 is the most useful here, since you can check the slope of the tile, or even the nearby tiles. This callback is the only way to allow your tile to be built on steep slopes.

Planetmaker: /* Custom shape check (2F) */ Re-order text so that the important info comes first

2011-08-16T07:18:13Z

Custom shape check (2F): Re-order text so that the important info comes first

@@ Line 1: / Line 1: @@
 == Custom shape check (2F) ==
-This callback is called when TTD checks if a given tile is suitable for the industry tile. Since the tile isn't built yet, you can
+This callback is called when TTD checks if a given tile is suitable for the industry tile. The callback should return zero if the tile isn't suitable, or any other value if it is suitable.
-'''PLEASE NOTE:''' When this callback is called, TTD is just checking, and hasn't placed any industry tiles yet. Therefore, bit 8 (tile
+'''PLEASE NOTE:''' When this callback is called, TTD is just checking, and hasn't placed any industry tiles yet. Therefore, bit 8 (tile belongs to the same industry as current) of variable 60 will always be clear, even for the current tile.
 [[Category:Callbacks]]

Michi cc: formatting

2011-07-25T20:53:34Z

formatting

← Older revision		Revision as of 20:53, 25 July 2011
Line 13:		Line 13:
	are the same as the lowest byte of variable 18 of callback 28.		are the same as the lowest byte of variable 18 of callback 28.

	{{grf\|7}}The meaning of the returned value is different in GRF version 7; it works the same way as [[Callbacks#Industry location permissibility (28) \|callback 28]].		{{grf\|7}} The meaning of the returned value is different in GRF version 7; it works the same way as [[Callbacks#Industry location permissibility (28) \|callback 28]].
	Also, since TTDPatch r1755, you can use the text reference stack for your error messages, similarly to callback 3A. The only difference is that		Also, since TTDPatch r1755, you can use the text reference stack for your error messages, similarly to callback 3A. The only difference is that
	only 4 registers are copied instead of 6.		only 4 registers are copied instead of 6.

Michi cc: /* Custom shape check (2F) */ GRF version tag

2011-07-23T18:36:02Z

Custom shape check (2F): GRF version tag

← Older revision		Revision as of 18:36, 23 July 2011
Line 13:		Line 13:
	are the same as the lowest byte of variable 18 of callback 28.		are the same as the lowest byte of variable 18 of callback 28.

	~~'''Important:'''~~ The meaning of the returned value ~~will~~ ~~change~~ in GRF version 7; it ~~will work~~ the same way as ~~callback~~ 28. ~~Also,~~ ~~since~~		{{grf\|7}}The meaning of the returned value is different in GRF version 7; it works the same way as [[Callbacks#Industry location permissibility (28) \|callback 28]].
	TTDPatch r1755, you can use the text reference stack for your error messages, similarly to callback 3A. The only difference is that		Also, since TTDPatch r1755, you can use the text reference stack for your error messages, similarly to callback 3A. The only difference is that
	only 4 registers are copied instead of 6~~; see [[Callbacks#Industry location permissibility (28) \|callback 28]] for details~~.		only 4 registers are copied instead of 6.

	'''PLEASE NOTE:''' When this callback is called, TTD is just checking, and hasn't placed any industry tiles yet. Therefore, bit 8 (tile		'''PLEASE NOTE:''' When this callback is called, TTD is just checking, and hasn't placed any industry tiles yet. Therefore, bit 8 (tile

Pm-bot: Create a separate page for each callback

2011-06-16T18:58:04Z

Create a separate page for each callback

New page

== Custom shape check (2F) ==

This callback is called when TTD checks if a given tile is suitable for the industry tile. Since the tile isn't built yet, you can
use variables 41, 42, 43, and 60 only, and you can't access any industry variables, either. Since OpenTTD r19744 however, you can
access the random bits of the industry (it would get after construction) via industry variable 5F resp. [[RandomAction2]] type 83.
Var. 60 is the most useful here, since you can check the slope of the tile, or even the nearby tiles. This callback is the only way
to allow your tile to be built on steep slopes. The callback should return zero if the tile isn't suitable, or any other value if it is suitable.

Since TTDPatch 2.6 r1728, the lowest byte of variable 18 contains the layout number selected for the industry. The other bits of
variable 18 remain undefined for now.

Since OpenTTD r20942, the second lowest byte of variable 18 contains the trigger event of the industry construction. The values
are the same as the lowest byte of variable 18 of callback 28.

'''Important:''' The meaning of the returned value will change in GRF version 7; it will work the same way as callback 28. Also, since
TTDPatch r1755, you can use the text reference stack for your error messages, similarly to callback 3A. The only difference is that
only 4 registers are copied instead of 6; see [[Callbacks#Industry location permissibility (28) |callback 28]] for details.

'''PLEASE NOTE:''' When this callback is called, TTD is just checking, and hasn't placed any industry tiles yet. Therefore, bit 8 (tile
belongs to the same industry as current) of variable 60 will always be clear, even for the current tile.
[[Category:Callbacks]]