Difference between revisions of "Callback: Additional text in purchase screen"

From GRFSpecs
Jump to navigationJump to search
(reference stack in cb 23)
(six registers instead of four)
Line 7: Line 7:
 
If cargo FF (buy menu sprite) is handled explicitly for a vehicle, then the varaction 2 handling [[Callbacks#Additional text in purchase screen (23) |callback 23]] must be in the buy menu varaction 2 chain.
 
If cargo FF (buy menu sprite) is handled explicitly for a vehicle, then the varaction 2 handling [[Callbacks#Additional text in purchase screen (23) |callback 23]] must be in the buy menu varaction 2 chain.
   
{{ottdp|1.2|no|ottdrev=r23040}} Since OpenTTD r23040 the contents of registers 100h..103h are copied onto the text reference stack.
+
{{ottdp|1.2|no|ottdrev=r23045}} Since OpenTTD r23045 the contents of registers 100h..105h are copied onto the text reference stack.
   
 
[[Category:Callbacks]]
 
[[Category:Callbacks]]

Revision as of 19:03, 20 October 2011

Additional text in purchase screen (23)

This callback is called when TTDPatch displays the vehicle stats of any vehicle in its purchase screen. The return value is the "xx" of a D0xx text ID to be shown below all other stats. The callback is always used when defined, no bit in the action 0 property needs to be set to activate it. As of r1908, text IDs D100..D3FF may also be returned.

How many lines are available depends on the type of vehicle and its other properties, for instance the presence or absence of a "refittable to" line or powered wagons etc. Lines are wrapped automatically, or may be broken explicitly using the newline character 0D.

If cargo FF (buy menu sprite) is handled explicitly for a vehicle, then the varaction 2 handling callback 23 must be in the buy menu varaction 2 chain.

Supported by OpenTTD 1.2 (r23045)1.2 Not supported by TTDPatch Since OpenTTD r23045 the contents of registers 100h..105h are copied onto the text reference stack.