Age | Commit message (Collapse) | Author |
|
|
|
|
|
Allow more direct player-initiated interaction for Game Scripts, by letting the GS put push-buttons on storybook pages. These buttons can either trigger an immediate event, or require the player to first select a tile on the map, or a vehicle.
Additionally this reworks how the storybook pages are layouted and rendered, to allow for slightly more complex layouts, and maybe speeding drawing up a bit.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
scripts and fix documentation.
|
|
|
|
industry, or town when publishing news.
|
|
|
|
|
|
station
|
|
|
|
page elements for a given page
|
|
|
|
rate set previously via GSTown::SetGrowthRate.
|
|
money to companies
|
|
rename towns
|
|
|
|
|
|
|
|
IsSnowTile work, i.e. the ones without infrastructure or buildings
-Feature: introduce GetTerrainType which allows one to get that information for tiles with buildings and infrastructure as well
|
|
|
|
|
|
|
|
deliveries done by companies.
|
|
|
|
|
|
and a town.
|
|
|
|
window's title from a (small) set of options
|
|
|
|
company(ies). It can contain random text, and at most 3 buttons from a collection of 17
|
|
even over network
|
|
|
|
(GameScript only)
|
|
|
|
(GameScript only)
|
|
(GameScript only)
|
|
GameScript
|
|
ScriptGame::GetLandscape (GameScript only)
|
|
|
|
API when they refer to the in-game values in the cases where that is possible and sensible
|
|
|
|
|
|
C++ glue templates to script/api/template
|