Difference between revisions of "Action13"
From GRFSpecs
Jump to navigationJump to searchm (use grfID consistently) |
m (use GRFID consistently) |
||
| Line 9: | Line 9: | ||
The data looks as follows: |
The data looks as follows: |
||
| − | <sprite-number> * <length> 13 <feature> < |
+ | <sprite-number> * <length> 13 <feature> <GRFID> <num-ent> <offset> <text...> |
{| |
{| |
||
| Line 29: | Line 29: | ||
|Action 13 |
|Action 13 |
||
|- |
|- |
||
| − | |< |
+ | |<GRFID> |
|4*B |
|4*B |
||
| − | |The |
+ | |The GRFID of the file whose texts are to be translated |
|- |
|- |
||
|<num-ent> |
|<num-ent> |
||
| Line 49: | Line 49: | ||
For action 13, <num-ent>, <offset> and <text...> work exactly as for [[Action4|action 4]], but the offset may only refer to a text ID in the D000 or DC00 range of IDs. |
For action 13, <num-ent>, <offset> and <text...> work exactly as for [[Action4|action 4]], but the offset may only refer to a text ID in the D000 or DC00 range of IDs. |
||
| − | Action 13 is skipped if the given |
+ | Action 13 is skipped if the given GRFID cannot be found or if the file is inactive; action 13 generates an error message and disables the current file if it appears before the GRF that it is translating. |
Revision as of 16:05, 15 June 2011
Description
Translating regular strings is easy by just overwriting them with an action 4, however this is not possible for translating GRF-specific strings in the D000 or DC00 range of IDs. Instead, these must be translated with this action 13.
Available since 2.6 alpha 1 (r857).
Format
The data looks as follows:
<sprite-number> * <length> 13 <feature> <GRFID> <num-ent> <offset> <text...>
| Element | Size | Description |
|---|---|---|
| <sprite-number> | dec | A sequential sprite number |
| <length> | dec | The total number of bytes in the action |
| 13 | B | Action 13 |
| <GRFID> | 4*B | The GRFID of the file whose texts are to be translated |
| <num-ent> | B | Number of strings |
| <offset> | W | First text ID |
| <text...> | S | Zero-terminated strings |
For action 13, <num-ent>, <offset> and <text...> work exactly as for action 4, but the offset may only refer to a text ID in the D000 or DC00 range of IDs.
Action 13 is skipped if the given GRFID cannot be found or if the file is inactive; action 13 generates an error message and disables the current file if it appears before the GRF that it is translating.
