| 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.
|
|
|
|
|
|
|
|
bounds are inclusive
|
|
rigs
|
|
|
|
incorrect
|
|
|
|
|
|
|
|
While at it, renamed the project names to reflect how we currently
refer to them.
|
|
* Feature: GS method to allow company to use an engine before its introduction date
* Feature: GS method to retire an engine early for a specific company
|
|
|
|
|
|
|
|
|
|
|
|
window.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This allows GameScripts to shrink towns as well as grow them.
|
|
Multiplayer games has the server add some flags to the cmd value during the handling.
These flags should not be included in the verification, mask them out. Without this
masking out, scripts tend to die when executing their first command in multiplayer.
|
|
|
|
(#7715)
|
|
Can be found at town information > local authority window
Layout for button is same as Graph Keys
Turn on/off for every town individually
|
|
|
|
|
|
Null pointer dereference occurred when either origin_tile or dest_tile
were waypoint tiles.
|
|
< 2**16
|
|
|
|
|
|
|
