How can I read the game mode in action 2?

[George]

In action 7 I can read the mode
92 B Game mode, 0 in title screen, 1 in game and 2 in editor
how can I do it in action D or 2?

[belugas]

In action D, it is easy to do.
It would be patch's variable 14, same encoding as for var 92, action 7.
As for action 2...
http://wiki.ttdpatch.net/tiki-index.php ... nalAction2, variable 21?
AS far as i know, there is no other means. But i may be wrong.

[George]

In action D, it is easy to do.
It would be patch's variable 14, same encoding as for var 92, action 7.
As for action 2...
http://wiki.ttdpatch.net/tiki-index.php ... nalAction2, variable 21?
AS far as i know, there is no other means. But i may be wrong.

Ok.

[belugas]

hemmm...
Sorry, but i meant that these would be new features, not currently available ones...

[George]

hemmm...
Sorry, but i meant that these would be new features, not currently available ones...

I understood your post as you've added this task to your todo list. Was I mistaken?

[frosch]

George:
You can access every variable from Action7/9 also in ActionD.
To use them in VarAction2 just copy variable 0x92 to a free 'parameter'-variable (0x00-0x7F) and use it through varaction2 variable 0x7F[...]

So we decided that there is no need to add new things.

Speaking for the OTTD-devs. Regards frosch.

[George]

You can access every variable from Action7/9 also in ActionD.

How?

[frosch]

target, source1, source2
These bytes specify the target parameter and source parameters. They can either be simply the numbers of grf parameters, or they can be the special variables from action 7, see the description of param-num there.

[George]

target, source1, source2
These bytes specify the target parameter and source parameters. They can either be simply the numbers of grf parameters, or they can be the special variables from action 7, see the description of param-num there.

Ok, thank you.

[DaleStan]

You can access every variable from Action7/9 also in ActionD.

You can also access every 7/9/D variable in action 2.

[frosch]

That does not seem to be documented.
So is VarAction2 variable 'i' identical to Action7/9/D variable '0x80 + i' for 'i' in 0x00 to 0x3F ?

[DaleStan]

It's documented only in that there's a suspicious correspondence between the global action 2 variables and the action 7/9/D variables.

And correct.

[George]

It's documented only in that there's a suspicious correspondence between the global action 2 variables and the action 7/9/D variables. And correct.

NFOrenum reports var 12 unknown

[Maedhros]

It's documented only in that there's a suspicious correspondence between the global action 2 variables and the action 7/9/D variables.

Why wasn't it explicitly documented, out of interest?

[DaleStan]

Because there's a nebulous idea that we might someday split the action 2 globals from the 7/9/D globals, and the fewer variables are actually documented as working both places, the more space we can generate from the split.

[George]

Because there's a nebulous idea that we might someday split the action 2 globals from the 7/9/D globals, and the fewer variables are actually documented as working both places, the more space we can generate from the split.

why not to make such change from GRF version 8 (9, 10 ...)? In the current version (7) it works this way - so it should go to documentation.
We already had changes between version 6 and 7, so why not to use this solution in the future?

[DaleStan]

why not to make such change from GRF version 8?

That would work too, I suppose.

In the current version (7) it works this way - so it should go to documentation.

Invalid argument. In earlier versions, the feature byte for 1/2/3 chains didn't actually have to match. Should that have been documented too?

[George]

In the current version (7) it works this way - so it should go to documentation.

Invalid argument. In earlier versions, the feature byte for 1/2/3 chains didn't actually have to match. Should that have been documented too?

I suppose yes.

I mean I'm using var 12 in action 2 in my current versions of the GRF files, it works, so I would like to be sure that this will be not broken in the next version without a warning (changing the appropriate wiki page counts as this warning )

[DaleStan]

Any GRF file that obeys the current documentation will continue to work with all future versions of TTDPatch, unless Patchman decides differently.

[George]

Any GRF file that obeys the current documentation will continue to work with all future versions of TTDPatch, unless Patchman decides differently.

Current documentation does not declare var 12 for action 2 as game mode. NFOrenum counts it as error 86.